[
https://issues.apache.org/jira/browse/PHOENIX-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250475#comment-14250475
]
James Taylor edited comment on PHOENIX-1514 at 12/17/14 8:28 PM:
-----------------------------------------------------------------
If it meets our backward compatibility contract, why wouldn't we want this to
go into 4.0 for our 4.3 release? The reason to put it into 4.0 is because
otherwise our merges from master to 4.0 branch will become almost impossible.
was (Author: jamestaylor):
If it meets our backward compatibility contract, why wouldn't we want this to
go into 4.0 for our 4.3 release?
> 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, PHOENIX-1514.01.patch,
> PHOENIX-1514.02.patch, PHOENIX-1514.04.patch, hung-phoenix-verify.txt,
> stack.txt
>
>
> 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)
