We are specifically looking for the ability to create callbacks on
put, increment, and delete for specific tables so we can implement the
indexing solution. This is actually advance preparation for Socorro 2.0
which won't be released until August or maybe September, so we have some
dev time.
My concern is that if we don't take advantage of your coprocessor work,
we will end up needing to write our own callback code from scratch
anyway, and that doesn't seem to be a better choice than helping you
flesh out a solid use case for co-processors and implement it.
Thoughts?
-Daniel
On 6/7/10 7:28 PM, Andrew Purtell wrote:
Hi Anurag,
Part of the big patch for HBASE-2001 up on JIRA, the RegionObserver interface,
is available in a tracked branch of HBase trunk up on Github:
http://github.com/apurtell/hbase-coprocessor
I see three problems with your use of it at this time: 1) You will have to run
HBase trunk (0.21-dev). 2) The patch must be considered highly experimental.
The particulars of the interfaces will be changing soon. For example, those
relating to splits and flushes must change when HBASE-2375 (and related) goes
in. 3) This is being developed in a feature branch up in GitHub until it is
ready end to end including a demo use case.
So I expect you will prefer to wait.
However if you are interested in taking up coprocessors in some form I'm always
happy to collaborate on its further development, including:
- Commit access to the GitHub repository
- Help troubleshooting
- Timely bug fixes
- Collaborative development
Best regards,
- Andy
From: Anurag Phadke
Subject: HBASE-2001 and ElasticSearch
To: [email protected]
Date: Monday, June 7, 2010, 3:39 PM
Hello,
We are planning to use Elastic Search (http://www.elasticsearch.com/) for
indexing crash reports built-off Socorro, the crash-reporting software. The
index file/s for ElasticSearch will be built off Hadoop/HBase.
We are particularly interested in applying HBASE-2001, the co-processor patch
(https://issues.apache.org/jira/browse/HBASE-2001) to the standard HBase
install. Is it possible for anyone to share some thoughts on the patch,
specifically, whether it's in a state where we can apply it and run production
instance of HBase or its preferred to wait....
Thanks for your time,
-Anurag
