You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/12/02 20:39:00 UTC
[jira] [Updated] (CALCITE-4423) Provide the ability to specify
incoming trait in JdbcRules
[ https://issues.apache.org/jira/browse/CALCITE-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated CALCITE-4423:
------------------------------------
Labels: pull-request-available (was: )
> 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: 10m
> 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)