You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2019/05/11 20:59:00 UTC
[jira] [Commented] (CALCITE-3016) Reorganize the operator tables
[ https://issues.apache.org/jira/browse/CALCITE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837931#comment-16837931 ]
Julian Hyde commented on CALCITE-3016:
--------------------------------------
[~danny0405], I have reviewed your PR and added some commits to do further refactoring (and renaming). I also extended the test (added in CALCITE-3053) that every operator is documented and that the documentation states which library it belongs to, if it is not in the core library.
Can you take a look at my branch https://github.com/julianhyde/calcite/tree/3016-function-set ? Once we are agreed we can squash and commit.
> Reorganize the operator tables
> ------------------------------
>
> Key: CALCITE-3016
> URL: https://issues.apache.org/jira/browse/CALCITE-3016
> Project: Calcite
> Issue Type: Improvement
> Affects Versions: 1.19.0, 1.20.0
> Reporter: Danny Chan
> Assignee: Danny Chan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Reorganize the operator tables
> # Make a CommonOperatorTable for operators that belong to multiple dialect
> # create a dialect to operator table mapping cache for used dialect
> # annotation the function with specific annotation for operators in CommonOperatorTable
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)