[
https://issues.apache.org/jira/browse/PHOENIX-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250725#comment-14250725
]
Nick Dimiduk commented on PHOENIX-1514:
---------------------------------------
Okay, so the back port to 4 is pretty simple. I'm running through the verify
suite again on my linux machine to ensure nothing broke. I guess assessing the
level of risk in this patch is up to the RM for the stable branch. I agree it
is risky in that it touches many things. For this reason, I wouldn't take it a
patch release. I think it's also risky in that it's refactored the class
hierarchy of arrays. That latter point is where I've hit stumbling blocks in
the verify suite. I think this is where it becomes a question for the 4.3 RM.
Since the back port is relatively painless, maybe it's best to land this in
master and then evaluate it in the compatibility suite as [~jamestaylor]
suggest. If thinks look good, we can open a back port JIRA to take it into 4.3.
> 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)
