hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3247) Changes API: API for pulling edits from HBase
Date Sat, 19 Jul 2014 00:30:40 GMT

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

Andrew Purtell resolved HBASE-3247.
-----------------------------------

    Resolution: Not a Problem

Steven and crew ended up using replication to achieve this aim. Could also be done by implementing
a RegionObserver coprocessor that writes to Kafka etc.

> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message