For streams (changing data over time with timestamps), the simplest method in ES is really to manage timeframe-based indexes, like in the logstash model. So, you can decide to drop indexes when they become too old. There are tools that can help in this job, the curator.
By using index aliases, there is no disadvantage in comparison to a single index. And, ES index drops are very fast, and they do not require resources like document deletes which allocate space in segments. This should be carefully considered. With JDBC river, there is no requirement to delete and create the indexes, just use the same _id to address your docs, by a crontab definition. It is very easy to run this every 30 minutes. The docs will get overwritten and receive a new version number. Aside form the river, by checking the version of the docs in ES, you can find out old documents. The JDBC river does no longer take the job of deleting old documents, this has to be done from outside. Jörg On Mon, Feb 10, 2014 at 2:41 PM, Vallabh Bothre <[email protected]>wrote: > Thank you Kevin for your reply, > > But i was searching for the command which will directly update the data > without deleting and creating the indexes. > > Is there any command like curl -X UPDATE in elasticsearch ? > which will not add already existing data in elastic. > > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHGMWY78d_qgt-P8VQCV9inDMKZUgpBir3_APh%3DHERpHw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
