Someone in twitter suggested embedding Elastic Search in OrientDB as it
was done with Lucene https://github.com/orientechnologies/orientdb-lucene.
Could that have scalability problems for either OrientDB or Elastic Search.
I guess this cannot take the full advantage of Elastic Search and it is
using that for querying only..
Please guide me if I need to implement myself something or I could use
existing tools and what are the tradeoffs of the previous or other
approaches. I could have the support from Orient Technologies if I need it.
I could just use this one since OrientDB is providing a JDBC driver.
Could there be compatibility problems?
A person suggested Single point of failure problems with river plugins and
I read that river plugins could be deprecated (?) in the future ( sql server - Preferred method of indexing bulk data into ElasticSearch? - Stack Overflow).
I don't know if SPOF is actually a reality as I see river plugins used for
many types of resources that seem very decoupled.
Someone in twitter suggested embedding Elastic Search in OrientDB as it
was done with Lucene GitHub - orientechnologies/orientdb-lucene: Lucene indexes for OrientDB.
Could that have scalability problems for either OrientDB or Elastic Search.
I guess this cannot take the full advantage of Elastic Search and it is
using that for querying only..
Please guide me if I need to implement myself something or I could use
existing tools and what are the tradeoffs of the previous or other
approaches. I could have the support from Orient Technologies if I need it.
I have that in mind. What do you mean with official clients? I don't think
it is a good idea to hit both orientdb and elasticsearch when I am
inserting something for example..
Τη Τρίτη, 24 Φεβρουαρίου 2015 - 3:16:20 μ.μ. UTC-5, ο χρήστης Mark Walkom
έγραψε:
You can also DIY and leverage the official clients.
Be aware that in the long run that rivers are being deprecated.
On 25 February 2015 at 06:25, Michalis Michaelidis <mmich...@gmail.com
<javascript:>> wrote:
Hello,
I would like some guidelines about how to approach Elasticsearch
synchronization with OrientDB:
A person suggested Single point of failure problems with river plugins
and I read that river plugins could be deprecated (?) in the future ( sql server - Preferred method of indexing bulk data into ElasticSearch? - Stack Overflow).
I don't know if SPOF is actually a reality as I see river plugins used for
many types of resources that seem very decoupled.
Someone in twitter suggested embedding Elastic Search in OrientDB as
it was done with Lucene GitHub - orientechnologies/orientdb-lucene: Lucene indexes for OrientDB. Could that have
scalability problems for either OrientDB or Elastic Search. I guess this
cannot take the full advantage of Elastic Search and it is using that for
querying only..
Please guide me if I need to implement myself something or I could use
existing tools and what are the tradeoffs of the previous or other
approaches. I could have the support from Orient Technologies if I need it.
I have that in mind. What do you mean with official clients? I don't
think it is a good idea to hit both orientdb and elasticsearch when I am
inserting something for example..
Τη Τρίτη, 24 Φεβρουαρίου 2015 - 3:16:20 μ.μ. UTC-5, ο χρήστης Mark Walkom
έγραψε:
You can also DIY and leverage the official clients.
Be aware that in the long run that rivers are being deprecated.
On 25 February 2015 at 06:25, Michalis Michaelidis mmich...@gmail.com
wrote:
Hello,
I would like some guidelines about how to approach Elasticsearch
synchronization with OrientDB:
In this google group discussion (https://groups.google.com/d/
msg/orient-database/YAesdS2qAYc/yCp7v9pF6tcJ) someone said that it
could be done using hooks api of OrientDB that is more efficient than just
pooling. Any thoughts on that?
JDBC River plugin ( jprante (Jörg Prante) · GitHub
elasticsearch-river-jdbc) - I could just use this one since OrientDB is
providing a JDBC driver. Could there be compatibility problems?
A person suggested Single point of failure problems with river plugins
and I read that river plugins could be deprecated (?) in the future ( sql server - Preferred method of indexing bulk data into ElasticSearch? - Stack Overflow
method-of-indexing-bulk-data-into-elasticsearch). I don't know if SPOF
is actually a reality as I see river plugins used for many types of
resources that seem very decoupled.
Someone in twitter suggested embedding Elastic Search in OrientDB as
it was done with Lucene https://github.com/orientechnologies/orientdb-
lucene. Could that have scalability problems for either OrientDB or
Elastic Search. I guess this cannot take the full advantage of Elastic
Search and it is using that for querying only..
Please guide me if I need to implement myself something or I could use
existing tools and what are the tradeoffs of the previous or other
approaches. I could have the support from Orient Technologies if I need it.
No I didn't find anything.. Actually I moved away from OrientDB due to so many bugs that exist in their code base and SQL graph queries that are cumbersome compared to Gremlin. I migrated to TitanDB which is automatically sync'd with ElasticSearch and since it was acquired from Datastax I migrated to Datastax DSE Graph which is sync'd with Apache Solr.. if you need something custom you may approach it with a queue like Apache Kafka or RabbitMQ that each store (e.g your database and elastic search and caches) synchronizes against it. Hope this helps!
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.