You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/10/27 18:44:01 UTC
[jira] [Commented] (PHOENIX-3283) Track incompatibilities between
Calcite/Phoenix and Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612763#comment-15612763 ]
James Taylor commented on PHOENIX-3283:
---------------------------------------
Please label any JIRA that requires a change in Phoenix behavior (and subsequent unit test changes) with calcite-compat-change. That way we can track required changes for our consumers through this JIRA query: https://issues.apache.org/jira/browse/PHOENIX-3267?jql=project%20%3D%20PHOENIX%20and%20labels%3Dcalcite-compat-change
FYI, [~lomoree], [~rajeshbabu], [~maryannxue], [~gabriel.reid]
> Track incompatibilities between Calcite/Phoenix and Phoenix
> -----------------------------------------------------------
>
> Key: PHOENIX-3283
> URL: https://issues.apache.org/jira/browse/PHOENIX-3283
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
>
> As we get deeper into moving Phoenix to run on top of Calcite, we may find non standard Phoenix-specific syntax which we don't want to support in Phoenix/Calcite. An example might be not supporting != but requiring these to be changed to <>. This epic JIRA can serve as the root for tracking purposes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)