+1 I have no idea whether you use Calcite for formatting plans or use Drill code. If the former, I’d be happy to accept a patch to Calcite that allows this as a formatting option for Calcite plan.
Anyone have a good descriptive name for this format? Steven, were you inspired by some other system that uses this format? Julian On Apr 13, 2015, at 9:44 AM, Jason Altekruse <[email protected]> wrote: > +1 > > On Fri, Apr 10, 2015 at 11:23 PM, Aditya <[email protected]> wrote: > >> This looks much neater and makes it easy to keep track of. >> >> On Fri, Apr 10, 2015 at 4:23 PM, Steven Phillips <[email protected]> >> wrote: >> >>> I find the current format for physical plans, where we indent for every >>> operator, but keep both sides of the join at the same indentation the >> same, >>> is very difficult to read, especially when we have several joins. >>> >>> I think it would be easier to read if we kept sequential operators at the >>> same indentation, but increased indentation only when there is a join, >> and >>> include some marks to show the connection between the sides of the join >> and >>> the join operator. >>> >>> I created a gist with an example: >>> >>> https://gist.github.com/StevenMPhillips/74a6bf655175aabd14c0 >>> >>> >>> >>> -- >>> Steven Phillips >>> Software Engineer >>> >>> mapr.com >>> >>
