[
https://issues.apache.org/jira/browse/PHOENIX-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid resolved PHOENIX-381.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by
first re-opening all closed imported issues and then resolving them in bulk.
> Long literal should be supported
> --------------------------------
>
> Key: PHOENIX-381
> URL: https://issues.apache.org/jira/browse/PHOENIX-381
> Project: Phoenix
> Issue Type: Task
> Reporter: Raymond Liu
>
> I can see that in phoenix.g there are TOKEN for LONG type to describe long
> number as 1L etc., while it does not been included in literal rules, instead
> the literal value's type is determined by the value range. Thus there are no
> way to represent a value which fall in INT range as a Long type. usually this
> is ok, since int could be convert to long when they been assigned or compare
> to a column. However, this not working for "SPLIT ON" which have no clue of
> the column type.
> either support LONG literal or fix SPLIT ON by access column type info. And I
> think to support LONG literal is more nature and easy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
