Hi, it's something I started to discuss a bit here: http://neo4j.com/developer/elastic-search/#_elasticsearch_index_provider <http://neo4j.com/developer/elastic-search/#_elasticsearch_index_provider>
The tricky thing is the contract of the index provider and the async / delay until data is in ES and available. Also the index provider would be used for all, exact lookups and constraints too. It's not hard to implement actually, here is a recent example (for chronicle maps) to implement an https://github.com/maxdemarzi/neo_chronicle_index <https://github.com/maxdemarzi/neo_chronicle_index> Michael > Am 27.05.2015 um 23:27 schrieb [email protected]: > > Hi, > > I'm looking into using Elastic Search as the Neo4j schema index provider. > > Has anyone already used/implemented this and would people have any > recommendations? > > Any help is appreciated. > > Take care, > Jennifer > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
