[
https://issues.apache.org/jira/browse/PHOENIX-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726593#comment-15726593
]
ASF GitHub Bot commented on PHOENIX-3477:
-----------------------------------------
Github user maryannxue commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/224#discussion_r91163250
--- Diff:
phoenix-core/src/it/java/org/apache/phoenix/calcite/CalciteIT.java ---
@@ -1343,6 +1343,28 @@ public void initTable() throws Exception {
{7L, "0000000005", "T5", "0000000005", "S5"},
{8L, "0000000006", "T6", "0000000006", "S6"}})
.close();
+
--- End diff --
Thank you for the info, @lomoree! Very helpful! I was wondering if there
had been any check of that kind during conversion. Anyway, would you mind
removing that NO_SEQUENCE predicate and trying the changes I suggested below?
> Support sequence arithmetic in Calcite-Phoenix
> ----------------------------------------------
>
> Key: PHOENIX-3477
> URL: https://issues.apache.org/jira/browse/PHOENIX-3477
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Eric Lomore
> Assignee: Eric Lomore
>
> When a sequence is wrapped inside an arithmetic operator it is routed through
> PhoenixServerProject which does not currently have sequence support
> {{SELECT NEXT VALUE FOR foo.bar+1 FROM SYSTEM.SEQUENCE.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
