Live data from Hacker News

Dgsh – Directed graph shell

dmst.aueb.gr

51–53 of 53 posts

Re: Dgsh – Directed graph shell

#51
post #49

Earlier quoted context omitted.

Is it possible to show what XSLT is and why it's useful in like 5 minutes? I've always wanted a transformation language of some sort, but I've never managed to figure out XSLT (probably because I've never needed it) so I don't know what problems it solves or doesn't solve.

I've always wanted a transformation language of some sort, but I've never managed to figure out XSLT (probably because I've never needed it) so I don't know what problems it solves or doesn't solve. You'd be familiar with SQL. SQL is a declarative language for interacting with a relational structure. You say what you want and from where. It outputs to a table. Or, with significant effort, to more complex forms. XPath…

Thank you for taking the time to write this!!

Re: Dgsh – Directed graph shell

#52
post #28
post #27

Earlier quoted context omitted.

Have you checked out airflow? Any opinions?

I have looked a bit at code examples of Airflow, but was worried that it seems to have a similar problem as a lot of other pipeline tools: That in the main workflow specification, dependencies are specified between tasks only, not between the individual inputs and outputs of each task (between tasks rather than data). This means that this info needs to be implemented "manually" in some less declarative manner somewhe…

We wrote a package to go with our Airflow installation to borrow some of the data flow (as opposed to Airflow's exclusive task deps flow you mention) concepts we liked from Make/Drake/Luigi. You may be interested: github.com/industrydive/fileflow

Re: Dgsh – Directed graph shell

#53
post #52
post #28

Earlier quoted context omitted.

I have looked a bit at code examples of Airflow, but was worried that it seems to have a similar problem as a lot of other pipeline tools: That in the main workflow specification, dependencies are specified between tasks only, not between the individual inputs and outputs of each task (between tasks rather than data). This means that this info needs to be implemented "manually" in some less declarative manner somewhe…

We wrote a package to go with our Airflow installation to borrow some of the data flow (as opposed to Airflow's exclusive task deps flow you mention) concepts we liked from Make/Drake/Luigi. You may be interested: github.com/industrydive/fileflow

That's nice! Didn't know Airflow did in-memory passing (as I now understand it does?), so I can see that this must be needed for larger data items, right?

Does it also help with making it easier to route individual multiple outputs to separate downstream components etc?

Post reply on HN