hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3247) Changes API: API for pulling edits from HBase
Date Tue, 23 Nov 2010 21:34:14 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935055#action_12935055

stack commented on HBASE-3247:

@Steven Yes, we should start with RowLog (http://www.lilyproject.org/maven-site/0.1/apidocs/org/lilycms/rowlog/api/RowLog.html).

bq. I'm wondering, as I'm seeing a proliferation of alternative yet overlapping approaches
to a certain number of issues (secondary indexes, change listening) which in the end could
confuse new users.

-1 to proliferation of alternate yet overlapping... things

What you fellas suggest for bootstrapping system -- doing a fat bulk load into the search
index -- and then cutting over to rowlog for incremental updates?  Doesn't there have to exact
transition so followers do not miss edits?  You fellas have ideas for how to do that?

> Changes API: API for pulling edits from HBase
> ---------------------------------------------
>                 Key: HBASE-3247
>                 URL: https://issues.apache.org/jira/browse/HBASE-3247
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
> Talking to Shay from Elastic Search, he was asking where the Changes API is in HBase.
 Talking more -- there was a bit of beer involved so apologize up front -- he wants to be
able to bootstrap an index and thereafter ask HBase for changes since time t.  We thought
he could tie into the replication stream, but rather he wants to be able to pull rather than
have it pushed to him (in case he crashes, etc. so on recovery he can start pulling again
from last good edit received).  He could do the bootstrap with a Scan.  Thereafter, requests
to pull from hbase would pass a marker of some  sort.  HBase would then give out edits that
came in after this marker, in batches, along with an updated marker.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message