You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@datafusion.apache.org by "danielhumanmod (via GitHub)" <gi...@apache.org> on 2026/05/01 01:08:23 UTC
Re: [I] feat: make it user configurable to display plans as tree renderer [datafusion-ballista]
danielhumanmod commented on issue #1627:
URL: https://github.com/apache/datafusion-ballista/issues/1627#issuecomment-4357217853
> Cc [@danielhumanmod](https://github.com/danielhumanmod) now we have explain and analyse maybe we could support tree renderer there as well?
Yeah, that sounds like a good improvement.
One thing I am thinking is how users should request the tree format for `EXPLAIN` / `EXPLAIN ANALYZE`.
One option is to extend the SQL syntax, for example:
```sql
EXPLAIN (FORMAT TREE) SELECT ...
EXPLAIN ANALYZE (FORMAT TREE) SELECT ...
```
Another option is to use a session config:
```
let config = SessionConfig::new_with_ballista()
.set_str("ballista.explain.plan_format", "tree")...
or from SQL:
SET ballista.explain.plan_format = 'tree';
```
The first option seems nicer from a user-facing SQL perspective, while the second one may be smaller to introduce on the Ballista side. I’d be curious what the community prefers here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org