[
https://issues.apache.org/jira/browse/CALCITE-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252426#comment-17252426
]
Vitalii Diravka commented on CALCITE-4423:
------------------------------------------
[~julianhyde]
I think there are no any reason don't make Calcite be usable by other tools.
The only requirement is the change should be good for all other tools too,
right?
bq. How can we make it more generally applicable?
Should incoming trait be available to be passed in all Rules, not only
JdbcRules?
> 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)
