You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/04/18 19:03:15 UTC
[jira] [Updated] (PHOENIX-480) Port Phoenix to 0.98 HBase
[ https://issues.apache.org/jira/browse/PHOENIX-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-480:
---------------------------------
Summary: Port Phoenix to 0.98 HBase (was: Port Phoenix to 0.96 HBase)
> Port Phoenix to 0.98 HBase
> --------------------------
>
> Key: PHOENIX-480
> URL: https://issues.apache.org/jira/browse/PHOENIX-480
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 3.0-Release
> Reporter: James Taylor
> Assignee: jzhong
> Fix For: 4.0.0, 5.0.0
>
>
> Here's what I can think of that'll be required:
> 1. Protobuf MetaDataProtocol endpoint coprocessor
> 2. Protobuf HashCacheProtocol endpoint coprocessor
> 3. Deal with any namespace issues. Phoenix uses HBase table names of the form "<schema_name>.<table_name>", so I'm not sure if this leads to issues with the new namespace scheme.
> They'll likely be other issues too of which I'm not aware. One enhancement I'd like to take advantage of is the new way of modifying HBase tables without requiring to disable and enable them.
> Once things are working, it'd be interesting to try to swap in the new type system to measure the performance impact. This would likely be a bigger task.
--
This message was sent by Atlassian JIRA
(v6.2#6252)