You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/03/02 02:37:00 UTC

[jira] [Updated] (HBASE-18881) [Coprocessor] Example on how best to keep up a secondary index

     [ https://issues.apache.org/jira/browse/HBASE-18881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-18881:
--------------------------
    Fix Version/s:     (was: 2.0.0)

> [Coprocessor] Example on how best to keep up a secondary index
> --------------------------------------------------------------
>
>                 Key: HBASE-18881
>                 URL: https://issues.apache.org/jira/browse/HBASE-18881
>             Project: HBase
>          Issue Type: Task
>          Components: Coprocessors
>            Reporter: stack
>            Priority: Major
>
> Do some study and make a recommendation, codified as an example of how to keep up a secondary index in another table out of a Coprocessor. This is a common usage. Discussion over in https://issues.apache.org/jira/browse/HBASE-18298?focusedCommentId=16180183&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16180183 cites a user making use of CP APIs do 'do the right thing' regards keeping up the secondary table only it is super-clunky in implementation. Study here would come up w/ recommendation on best way to do this (e.g. create 'shared' connection in the RS context used by all CPs participating in the index upkeep).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)