[
https://issues.apache.org/jira/browse/PHOENIX-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251254#comment-14251254
]
James Taylor commented on PHOENIX-1514:
---------------------------------------
[~elilevine] - I documented the current backward compat contract on our website
here: http://phoenix.apache.org/upgrading.html, and I think going forward (post
4.2) there's general consensus that we want to support a "mixed" set of clients
against a new version of Phoenix on the server-side: PHOENIX-1483. Other than
that, I think the burden is on us to provide adequate testing to meet this
contract. Small versus big in terms of lines of code changed isn't a good
metric IMHO. If everything continues working according to our backward compat
contract and our API contract (which is JDBC and SQL), then I think we're free
to innovate. If you want to start a conversation on private@ that's fine too.
> 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, PHOENIX-1514.05.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)
