[
https://issues.apache.org/jira/browse/HBASE-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180996#comment-13180996
]
Lars Hofhansl commented on HBASE-2038:
--------------------------------------
Maybe there's a way to collaborate on this (although I cannot promise much of
my time on this either).
>From gleaming HBASE-2037 this would not requite ITHBase and the indexes would
>be always consistent, correct? I have not looked at the 2.5mb(!) patch in
>HBASE-2037, yet...
I was wondering if there's a summary somewhere about how it works. Specifically
how does a client know where to look for an indexed value?
> Coprocessors: Region level indexing
> -----------------------------------
>
> Key: HBASE-2038
> URL: https://issues.apache.org/jira/browse/HBASE-2038
> Project: HBase
> Issue Type: New Feature
> Components: coprocessors
> Reporter: Andrew Purtell
> Priority: Minor
>
> HBASE-2037 is a good candidate to be done as coprocessor. It also serve as a
> good goalpost for coprocessor environment design -- there should be enough of
> it so region level indexing can be reimplemented as a coprocessor without any
> loss of functionality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
