[
https://issues.apache.org/jira/browse/HBASE-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934192#action_12934192
]
Steven Noels commented on HBASE-3247:
-------------------------------------
If this is really about robust (and distributed) pulling, wouldn't the RowLog
mechanism as implemented in Lily would be a more solid approach - to the point
that RowLog would leave in-row-process-status data in a non-user-visible column?
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.
> 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.
