phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Levine (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1514) Break up PDataType Enum
Date Thu, 18 Dec 2014 05:04:13 GMT


Eli Levine commented on PHOENIX-1514:

bq. Or by "main and 5.0 branch" you just mean "master" in git? Thanks.
Sorry, [~ndimiduk]. Yes, just the "master" branch.

The reason I started this conversation is that I feel we (developers of Phoenix) could be
clearer about the semantics of what major and minor versions mean in Phoenix. Major features
would only go into into major versions; minor features into minor versions. This Jira falls
somewhere between the two (maybe close to major?): there are a lot of small changes but probably
no significant change in terms of how Phoenix works. It's really hard to have a discussion
about such things because we don't have clarity what kind of features should go into what
kind of version.

I'll kick off a conversation at private@ about this as the first step.

> Break up PDataType Enum
> -----------------------
>                 Key: PHOENIX-1514
>                 URL:
>             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

View raw message