hbase-issues mailing list archives

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

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

Jonathan Gray commented on HBASE-3247:
--------------------------------------

Scanning requires you to look at all the data (or at least, more than just the data you need).
 I think that would prove far to inefficient for something like keeping a search index up
to date which you expect to be as "realtime" as possible.

This is about only needing to see the deltas.

> 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.


Mime
View raw message