I didn't realize that Lily was that far along, I thought you were
still in R&D for a few more months. This sounds very promising and
we'll take a look at what you have available.
-Daniel
On 6/8/10 3:38 AM, Steven Noels wrote:
On Tue, Jun 8, 2010 at 2:55 AM, Daniel Einspanjer
<[email protected]>wrote:
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.
We'll soon (2-3 weeks) be releasing a HBase table-backed WAL/queue
implementation that binds HBase with SOLR for index updates in Lily, but is
designed not to be Lily-specific or -dependent. I don't know if this is of
any help for you, but it could be a robust way to asynchronously connect to
ES (or any other indexing service) as well.
More info at http://www.slideshare.net/outerthought/learning-lessons-4426942and
http://lilycms.org/lily/prerelease/architecture.html
HTH,
Steven.
