[
https://issues.apache.org/jira/browse/PHOENIX-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241614#comment-14241614
]
James Taylor commented on PHOENIX-1514:
---------------------------------------
I like the idea of being able to define the type system, but one primary
guiding factor for Phoenix is to be compatible with the SQL standards so I'd be
reluctant to specify this in a non standard way. If we can do it through config
options that would be more tenable.
You might need one or more new built-in functions to interpret OpenTSDB row
data.
We have Jenkins setup, but it's post commit. Nothing setup pre commit, but
that'd be a great thing to add.
> Break up PDataType Enum
> -----------------------
>
> Key: PHOENIX-1514
> URL: https://issues.apache.org/jira/browse/PHOENIX-1514
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 5.0.0
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 5.0.0
>
> Attachments: PHOENIX-1514.00.patch
>
>
> A first step in adopting (a portion of) HBase's type encodings is to break up
> the PDataType enum into an interface. This will pave the way for more
> flexibility going forward.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
