hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-18881) [Coprocessor] Example on how best to keep up a secondary index
Date Tue, 26 Sep 2017 17:53:00 GMT
stack created HBASE-18881:
-----------------------------

             Summary: [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
             Fix For: 2.0.0


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
(v6.4.14#64029)

Mime
View raw message