To fasten the search operations we are planning to use Elastic search for
transactional data. Data has to be fed into Elastic search from DB. The
main problem which we are foreseeing is to keep the data in synch between
ES and DB as the transactional data can be updated. We are looking for ways
to update the ES index after the transaction data is updated successfully
to avoid showing the stale data from ES.
We are looking for different solution options to achieve the same. if
anybody has worked on similar requirement please do let us know.
We are using Oracle DB? Should we use Oracle AQ on the database side or
some Java JMS Q to update Elastic search index.
Also we want to know when we update ES index will all the shards
automatically get updated?
To fasten the search operations we are planning to use Elastic search for
transactional data. Data has to be fed into Elastic search from DB. The
main problem which we are foreseeing is to keep the data in synch between
ES and DB as the transactional data can be updated. We are looking for ways
to update the ES index after the transaction data is updated successfully
to avoid showing the stale data from ES.
We are looking for different solution options to achieve the same. if
anybody has worked on similar requirement please do let us know.
We are using Oracle DB? Should we use Oracle AQ on the database side or
some Java JMS Q to update Elastic search index.
Also we want to know when we update ES index will all the shards
automatically get updated?
To fasten the search operations we are planning to use Elastic search
for transactional data. Data has to be fed into Elastic search from DB. The
main problem which we are foreseeing is to keep the data in synch between
ES and DB as the transactional data can be updated. We are looking for ways
to update the ES index after the transaction data is updated successfully
to avoid showing the stale data from ES.
We are looking for different solution options to achieve the same. if
anybody has worked on similar requirement please do let us know.
We are using Oracle DB? Should we use Oracle AQ on the database side or
some Java JMS Q to update Elastic search index.
Also we want to know when we update ES index will all the shards
automatically get updated?
To fasten the search operations we are planning to use Elastic search
for transactional data. Data has to be fed into Elastic search from DB. The
main problem which we are foreseeing is to keep the data in synch between
ES and DB as the transactional data can be updated. We are looking for ways
to update the ES index after the transaction data is updated successfully
to avoid showing the stale data from ES.
We are looking for different solution options to achieve the same. if
anybody has worked on similar requirement please do let us know.
We are using Oracle DB? Should we use Oracle AQ on the database side or
some Java JMS Q to update Elastic search index.
Also we want to know when we update ES index will all the shards
automatically get updated?
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.