[
https://issues.apache.org/jira/browse/PHOENIX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879121#comment-13879121
]
Jeffrey Zhong commented on PHOENIX-8:
-------------------------------------
{quote}
Is there any way to separate this out in a separate module so that both can be
easily generated from the same code base?
{quote}
This is ideal way if we can add a shim layer to load different jars based on
existing deployment. I looked at this before and estimate the effort will be
quite significant because Phoenix is a quite advanced HBase application/client.
Phoenix relies on HBase internals: coprocessor, WAL, keyval & filter. All these
areas have changed significantly with backward compatibility break changes. You
can get a sense on the differences on Phoenix on
0.96(https://github.com/forcedotcom/phoenix/pull/688). With the shim layer,
we'll also create more work for us when we introduce new data type from 0.96 or
develop new features relies on hbase0.96+ new feature such as tags etc.
In addition, all new major features are developed on hbase0.96+. I think people
will start to adopt hbase0.96/0.98 within half a year or so therefore the
effort for shim layer is likely short-lived.
> Apache Phoenix 3.0
> ------------------
>
> Key: PHOENIX-8
> URL: https://issues.apache.org/jira/browse/PHOENIX-8
> Project: Phoenix
> Issue Type: Task
> Reporter: Andrew Purtell
>
> Given the GitHub hosted Phoenix project is already up to the release series
> 2.0.x, I propose the first version of Phoenix released under the Apache roof
> should be 3.0.0.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
