-
Notifications
You must be signed in to change notification settings - Fork 60
Elasticsearch module #50
Comments
Hi. You know about [https://github.com/DigitalPebble/behemoth-elasticsearch]? It is probably in need of an update but should be a good starting point. |
Nope I didn't even see this Julien. I've nearly finished this patch as well :( |
I've added a link to [https://github.com/DigitalPebble/behemoth/wiki/Behemoth-Modules].
I decided not to have an ever-expanding list of modules in Behemoth per-se and be as decoupled and modular as possible. This also serves as an example of how to build a new resource for Behemoth with the Maven pom etc... BTW would be interesting to hear about your project and how Behemoth fits in. There's a page for use case which you're welcome to contribute a short blurb to if you feel like it [https://github.com/DigitalPebble/behemoth/wiki/Users]. |
Great.
I just went through around 4 hours of debugging network issues and making upgrades to various dependencies in order to get that ElasticSearch component to work with the master Behemoth codebase. I am however able to persist data into most recent release of ES now and want to push this into the codebase so I will send you a PR.
Yes I'll send you something right now. Please reply here with any thoughts on the above. Thanks Julien. |
great
it was kept separate also because it was less mature than the other components. It should be in sync with core - otherwise it would not compile at all. I take your point about having it released alongside the other modules though.
the many users of Behemoth have been very quiet in the last couple of years ;-) I'll look at your PR before moving the code. BTW do you leverage [https://github.com/elastic/elasticsearch-hadoop] at all? |
Hi @jnioche I'm working on an ES search module as part of using Behemoth in an ongoing project. I'll send you a PR ASAP.
The text was updated successfully, but these errors were encountered: