[ https://issues.apache.org/jira/browse/HBASE-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935552#action_12935552 ]
Steven Noels commented on HBASE-3247: ------------------------------------- Well, we're doing mapreduce for initial SOLR population, which might be a bit too involved compared with soemthing like a Changes API. I reckon our Indexer could be made configurable to connect to ES as well. i'll have Evert look into this issue, and comment to it, he just did a writeup on the Rowlog on our blog today: http://outerthought.org/blog/449-ot.html The thing I would object to if I were a non-Lily person, would be that we need tracking/status data in user-visible columns. > 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.