[jira] [Comment Edited] (CALCITE-7247) Add connection config to enable RuleMatchVisualizer

["TJ Banghart (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032958#comment-18032958 ] 

TJ Banghart edited comment on CALCITE-7247 at 10/25/25 11:19 PM:
-----------------------------------------------------------------

[~thomas.rebele] what would you think about a param like this? This could very well be something that already exists but I couldn't find it while briefly debugging with the visualizer. 

https://github.com/apache/calcite/pull/4602


was (Author: tjbanghart):
[~thomas.rebele] what would you think about a param like this? This could very well be something that already exists but I couldn't find it while briefly debugging with the visualizer. 

> Add connection config to enable RuleMatchVisualizer
> ---------------------------------------------------
>
>                 Key: CALCITE-7247
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7247
>             Project: Calcite
>          Issue Type: New Feature
>          Components: core
>            Reporter: TJ Banghart
>            Assignee: TJ Banghart
>            Priority: Minor
>
> The RuleMatchVisualizer is a very useful debugging tool; however, I’ve found it somewhat difficult to use for ad-hoc queries or when working with plans outside of Calcite’s unit tests.
> I would like to add a Calcite connection configuration option that automatically attaches a RuleMatchVisualizer to any planner associated with that connection. This would make it easier to debug queries directly from sqlline or other tools over jdbc.
> For example:
> {code}
> sqlline> !connect jdbc:calcite:ruleVisualizerDir=/tmp/viz
> sqlline> SELECT * FROM emp;
> RuleMatchVisualizer enabled: Output will be written to /tmp/viz/<query_id>
> -- Results --
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)