Updating Elastic search index along with DB

Hi

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?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b63b2347-700b-4bc0-a5a8-09a8c3b4681e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi ,
You cna use JDBC river to bridge ES and DB -


Only data inside the DB would flow to ES.

Thanks
Vineeth

On Fri, Dec 19, 2014 at 10:43 PM, teseter iamravi79@gmail.com wrote:

Hi

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?

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b63b2347-700b-4bc0-a5a8-09a8c3b4681e%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/b63b2347-700b-4bc0-a5a8-09a8c3b4681e%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGdPd5%3DgJ5xjKNgaVt3vU6RYfasBE5JMi0OJeWHzBPjdtpuQRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Hi,
Rivers are going to be deprecated as i read somewhere and doesn't seem to
be scalable solution.

Thanks
Ravi

On Mon, Dec 22, 2014 at 9:27 AM, vineeth mohan vm.vineethmohan@gmail.com
wrote:

Hi ,
You cna use JDBC river to bridge ES and DB -
https://github.com/jprante/elasticsearch-river-jdbc
Only data inside the DB would flow to ES.

Thanks
Vineeth

On Fri, Dec 19, 2014 at 10:43 PM, teseter iamravi79@gmail.com wrote:

Hi

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?

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b63b2347-700b-4bc0-a5a8-09a8c3b4681e%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/b63b2347-700b-4bc0-a5a8-09a8c3b4681e%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/i5npeA6lbZg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAGdPd5%3DgJ5xjKNgaVt3vU6RYfasBE5JMi0OJeWHzBPjdtpuQRA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAGdPd5%3DgJ5xjKNgaVt3vU6RYfasBE5JMi0OJeWHzBPjdtpuQRA%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAG%3DF_BKKeyz7wWvBCJFUaZW_Hyzy5ruU7wJd%3DPwmptgYJH2KmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

This is a JDBC plugin, not only a river.

You can use both JDBC river and feeder mode (logstash-like).

Both modes will be supported for a long time by JDBC plugin, even if
official ES river API disappears.

Jörg

On Mon, Dec 22, 2014 at 9:23 AM, Anupindi RaviShankar iamravi79@gmail.com
wrote:

Hi,
Rivers are going to be deprecated as i read somewhere and doesn't seem to
be scalable solution.

Thanks
Ravi

On Mon, Dec 22, 2014 at 9:27 AM, vineeth mohan vm.vineethmohan@gmail.com
wrote:

Hi ,
You cna use JDBC river to bridge ES and DB -
https://github.com/jprante/elasticsearch-river-jdbc
Only data inside the DB would flow to ES.

Thanks
Vineeth

On Fri, Dec 19, 2014 at 10:43 PM, teseter iamravi79@gmail.com wrote:

Hi

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?

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b63b2347-700b-4bc0-a5a8-09a8c3b4681e%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/b63b2347-700b-4bc0-a5a8-09a8c3b4681e%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/i5npeA6lbZg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAGdPd5%3DgJ5xjKNgaVt3vU6RYfasBE5JMi0OJeWHzBPjdtpuQRA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAGdPd5%3DgJ5xjKNgaVt3vU6RYfasBE5JMi0OJeWHzBPjdtpuQRA%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAG%3DF_BKKeyz7wWvBCJFUaZW_Hyzy5ruU7wJd%3DPwmptgYJH2KmQ%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAG%3DF_BKKeyz7wWvBCJFUaZW_Hyzy5ruU7wJd%3DPwmptgYJH2KmQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGFr9vjnQa3vcfaCrrmxD8Ztr1XAUzoVe5GQaTZajqigQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.