[
https://issues.apache.org/jira/browse/PHOENIX-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553537#comment-15553537
]
ASF GitHub Bot commented on PHOENIX-3265:
-----------------------------------------
GitHub user lomoree opened a pull request:
https://github.com/apache/phoenix/pull/216
PHOENIX-3265 Surround columns named date with double quotes
-- Only a few additional unit tests passed
-- Major impact on IT tests. Cherry-picked commit onto master to ensure no
glaring errors, but difficult to test on calcite branch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bloomberg/phoenix reservedkeywords
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/phoenix/pull/216.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #216
----
commit 3f1c926c7604df4abd3a24c95e1870f4c26f8bc0
Author: Eric <elom...@bloomberg.net>
Date: 2016-10-05T18:55:59Z
PHOENIX-3265 Surround columns named date with double quotes
----
> Surround columns named date with double quotes
> ----------------------------------------------
>
> Key: PHOENIX-3265
> URL: https://issues.apache.org/jira/browse/PHOENIX-3265
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Eric Lomore
>
> In Phoenix {{date}} is not a reserved word, but perhaps in Calcite it is? If
> that's the case, we should surround occurrences of columns named {{date}} in
> double quotes to prevent the parser error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
