[
https://issues.apache.org/jira/browse/PHOENIX-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533016#comment-15533016
]
ASF GitHub Bot commented on PHOENIX-3264:
-----------------------------------------
GitHub user lomoree opened a pull request:
https://github.com/apache/phoenix/pull/212
PHOENIX-3264 Allow TRUE and FALSE to be used as literal constants
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bloomberg/phoenix calcite
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/phoenix/pull/212.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 #212
----
commit fb59ed04b151fd8e7533cf5c99c70118a697de77
Author: Eric <[email protected]>
Date: 2016-09-28T17:56:29Z
PHOENIX-3264 Allow TRUE and FALSE to be used as literal constants
----
> Allow TRUE and FALSE to be used as literal constants
> ----------------------------------------------------
>
> Key: PHOENIX-3264
> URL: https://issues.apache.org/jira/browse/PHOENIX-3264
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Eric Lomore
> Attachments: Sql2RelImplementation.png, SqlLiteral.png,
> SqlNodeToRexConverterImpl.png, SqlOptionNode.png, objectdependencies.png,
> objectdependencies2.png, stacktrace.png
>
>
> Phoenix supports TRUE and FALSE as boolean literals, but perhaps Calcite
> doesn't? Looks like this is leading to a fair number of failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
