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/01/24 04:50:39 UTC
[jira] [Resolved] (PHOENIX-1061) PhoenixSQLParser can't handle
Long.MIN_VALUE (-9223372036854775808) as a literal.
[ https://issues.apache.org/jira/browse/PHOENIX-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor resolved PHOENIX-1061.
-----------------------------------
Resolution: Fixed
Assignee: James Taylor
Fix Version/s: 4.6.0
Fixed a while back.
> PhoenixSQLParser can't handle Long.MIN_VALUE (-9223372036854775808) as a literal.
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-1061
> URL: https://issues.apache.org/jira/browse/PHOENIX-1061
> Project: Phoenix
> Issue Type: Bug
> Reporter: Kyle Buzsaki
> Assignee: James Taylor
> Priority: Minor
> Fix For: 4.6.0
>
>
> The PhoenixSQLParser throws a syntax error when the value -9223372036854775808 is used as an integer literal in a select expression. This is Long.MIN_VALUE, so my assumption is that the parser is attempting to parse the sign and magnitude separately and then throwing an error that the magnitude is too large.
> An easy workaround is to replace all uses of -9223372036854775808 with some expression that evaluates to the same value but doesn't use the literal directly. For example, (-9223372036854775807 + -1).
> This issue does not appear to affect upsert expressions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)