Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a second text format for pipelines/plans #107

Open
jacques-n opened this issue Jul 29, 2024 · 0 comments
Open

Introduce a second text format for pipelines/plans #107

jacques-n opened this issue Jul 29, 2024 · 0 comments

Comments

@jacques-n
Copy link
Contributor

jacques-n commented Jul 29, 2024

Right now pipelines are kind of hard to read if there are nodes that have multiple inputs. Let's add a second supported pipeline pattern that is more similar to other query plans. It can use root to leaf ordering. In the design, it will list out a straight pipeline one line after another. If an operator has more than one input, it's children are indented (and subsequent as well) but are prefixed with a dash. For example, a plan that was a two tables read followed each followed by a filter joined together and then aggregated would like this in the old format and the new format:

Old:

pipelines {
  read -> filter -> join
  read2 -> filter2 -> join
  join -> aggregate -> root
}

New Format:

plan {
  aggregate
  join
  -filter
   read
  -filter2
   read2
}

I propose that both formats are supported but only one can be used at a time. When printing, we can request which we want.

@jacques-n jacques-n changed the title Introduce a second text format for pipelines Introduce a second text format for pipelines/plans Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant