[
https://issues.apache.org/jira/browse/CALCITE-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248669#comment-17248669
]
Charles Givre commented on CALCITE-4423:
----------------------------------------
[~julianhyde],
This PR benefits the Drill project as we are working to improve the storage
plugins and how they perform various optimizations. Since Drill has multiple
planning phases, we ran into this roadblock as [~volodymyr]. We would
appreciate it if you could commit this PR as I'm sure other projects that may
have multiple planning phases will also benefit from it.
Thanks!
> Provide the ability to specify incoming trait in JdbcRules
> ----------------------------------------------------------
>
> Key: CALCITE-4423
> URL: https://issues.apache.org/jira/browse/CALCITE-4423
> Project: Calcite
> Issue Type: Improvement
> Affects Versions: 1.26.0
> Reporter: Vova Vysotskyi
> Assignee: Vova Vysotskyi
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> For the case of multiple planning phases, it becomes not enough to use JDBC
> rules that accept rel nodes with {{Convention.NONE}} {{RelTrait}}.
> It would be handly to provide the possibility to specify desired
> {{RelTrait}}, for example, update constructors of {{JdbcConverterRule}}
> successors and provide additional method:
> {{JdbcRules.rules(RelTrait in, JdbcConvention out, RelBuilderFactory
> relBuilderFactory)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
