You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:20:22 UTC
[jira] [Resolved] (PHOENIX-394) Adding hbase-index contrib/ project
- support #4
[ https://issues.apache.org/jira/browse/PHOENIX-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabriel Reid resolved PHOENIX-394.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.
> Adding hbase-index contrib/ project - support #4
> ------------------------------------------------
>
> Key: PHOENIX-394
> URL: https://issues.apache.org/jira/browse/PHOENIX-394
> Project: Phoenix
> Issue Type: Task
> Reporter: Jason Yates
>
> For the moment, pushing this out as an independent, contrib project. Its independently build-able from Phoenix core until we can figure out where it should go and if it actually works all the way.
> To be fair, this is actually the product of extensive discussions at Salesforce.com. A full description of the underlying architecture is available here: http://jyates.github.io/2013/06/11/hbase-consistent-secondary-indexing.html, but a small outline and usage can be found in the README.
> This should provide the framework for building an index maintenance tool - specificaly a PhoenixIndexBuilder - that can support all the phoenix semantics in a consistent manner.
--
This message was sent by Atlassian JIRA
(v6.2#6252)