phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1642) Make Phoenix Master Branch pointing to HBase1.0.0
Date Tue, 03 Mar 2015 02:26:05 GMT


James Taylor commented on PHOENIX-1642:

Since it seems that going from 0.98 -> 1.0 does not require any downtime plus 0.98 clients
will work with 1.0 clients, Phoenix support for 1.0 will not require a major Phoenix release.
Should we commit this patch in a different branch? What will our naming scheme be between
Phoenix releases for HBase 1.0 versus HBase 0.98? Should we have a 4.4 release for HBase 0.98
and a 5.4 release for HBase 1.0? Or should we call in 4.4-HBase-0.98 and 4.4-HBase-1.0 (or
some other, better names)? Or should we have a shim layer, as these changes look pretty minimal?

Also, what would the timing of a Phoenix on top of HBase 1.0 release be? Are users waiting
for this - I've seen one request so far on the mailing list? How long will development continue
on the 0.98 branch? In what branch would we put Phoenix features that *will* require a major
upgrade? If we put these in the master branch, and the master branch is solely for HBase 1.0,
what happens if we want to release a Phoenix major release on the 0.98 branch?

> Make Phoenix Master Branch pointing to HBase1.0.0
> -------------------------------------------------
>                 Key: PHOENIX-1642
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>         Attachments: PHOENIX-1642.patch
> As HBase1.0.0 will soon be released, the JIRA is to point Phoenix master branch to HBase1.0.0
release. Once we reach consensus,  we could also port the changes into Phoenix 4.0 branch
as well which can be done in a separate JIRA.

This message was sent by Atlassian JIRA

View raw message