Hi JoeMcGuire.

I actually started work on this a little while ago, and I am pretty psyched someone else is interested in this. I am super excited that you started this project, and I think I have some code lying around that I can share if you are interested. Would also love to give some guidance on integrating with Search Lucene API if you get stuck. The API is flexible, but totally undocumented :-).

Thanks,
Chris

Comments

JoeMcGuire’s picture

JoeMcGuire commented

Hi Chris,

Thanks that would be great - if it's suitable for public view can you attach it here. If not then drop it in an email to me.

I'll try to help out with the documentation as I go. Is the Zend Lucene the only backend implementation of Search Lucene API so far?

cpliakas’s picture

cpliakas commented

Joe,

It is suitable for public view, I just have to find it. Zend Lucene is the only backend implemented in Search Lucene API, as other backends are intended to be added as contribs. The good part about the API is that it handles the difficult aspects of indexing as well as the UI. All the elastic search stuff contrib have to do is extend the adapter to do the CRUD operations along with adding any ES specific settings.

~Chris

alfthecat’s picture

alfthecat commented

subscribing

niccolox’s picture

niccolox commented

did you see the Dev Seed article by Adrian on using ElasticSearch with CouchDB?
http://developmentseed.org/blog/2011/may/31/flexible-faceting-and-full-t...

Search API extended by CouchDB and Elastic Search would be very interesting

cpliakas’s picture

cpliakas commented

Just a follow up here, I plan on breaking up Search Lucene API into smaller pieces that all search modules can use. Therefore I would focus on only providing an elastic search backend to Search API. Also, I think the code is lost in some harddrive somewhere that I simply cannot find. Sorry for not being able to share my past work around this.

Thanks,
Chris

JoeMcGuire’s picture

JoeMcGuire commented

Hi Chris,

Thanks for the update. How do you plan to manage this move for Drupal 7 versions? Will the current D7 module be dropped or will you keep it and just use another branch to break up the components?

cpliakas’s picture

cpliakas commented

I am planning on keeping the project page as is and posting a "News" item explaining my intentions referencing http://groups.drupal.org/node/162249 as a reason why. In terms of breaking the pieces up, I startes a sandbox project called Search Tools where I plan on adding the backend-agnostic stuff.

The overall reason is that we hava a fragmented search community. Adding yet another search centric API would only add to the problem. I think you are taking the right approach in adding a Zend Lucene backend for Search API, and it would be great for you to pull some of the knowledge from Search Lucene API into that module. Reducing the amount of targeted backend code people have to write will only make Drupal search better.

cpliakas’s picture

cpliakas commented
Status: Active » Closed (won't fix)

Marking as closed since I unfortunately have no code to share :-(