Hi,
I have a few questions with respect to the situation of needing to
re-create an index.
Is there is any process to re-create an index apart from deleting the
current one and creating it again with the documents ?
During the situations of re-create, can we use the data already stored
in the ES cluster ?
Are there any easy ways of the doing the same without have any down-time
to the running ES cluster ?
Appreciate any response on the same.
Thanks,
Karthik
--
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/e141b51d-99aa-4a78-b20a-2d9dcfe2e79b%40googlegroups.com .
For more options, visit https://groups.google.com/d/optout .
dadoonet
(David Pilato)
June 9, 2014, 7:55am
2
Use aliases.
So you have an alias which goes to oldindex.
Reindex in newindex.
When done, switch the alias.
You can read old index using scan and scroll feature and reindex in the new index as soon as you kept the _source field.
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 9 juin 2014 à 06:34, karthik jayanthi karthikjayanthi.iitm@gmail.com a écrit :
Hi,
I have a few questions with respect to the situation of needing to re-create an index.
Is there is any process to re-create an index apart from deleting the current one and creating it again with the documents ?
During the situations of re-create, can we use the data already stored in the ES cluster ?
Are there any easy ways of the doing the same without have any down-time to the running ES cluster ?
Appreciate any response on the same.
Thanks,
Karthik
--
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/e141b51d-99aa-4a78-b20a-2d9dcfe2e79b%40googlegroups.com .
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/DEFEB56B-5DDF-409B-829B-BAE787480C07%40pilato.fr .
For more options, visit https://groups.google.com/d/optout .
Awesome. Thanks for the prompt reply.
Thanks,
Karthik
On Mon, Jun 9, 2014 at 1:25 PM, David Pilato david@pilato.fr wrote:
Use aliases.
So you have an alias which goes to oldindex.
Reindex in newindex.
When done, switch the alias.
You can read old index using scan and scroll feature and reindex in the
new index as soon as you kept the _source field.
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 9 juin 2014 à 06:34, karthik jayanthi karthikjayanthi.iitm@gmail.com
a écrit :
Hi,
I have a few questions with respect to the situation of needing to
re-create an index.
Is there is any process to re-create an index apart from deleting the
current one and creating it again with the documents ?
During the situations of re-create, can we use the data already stored
in the ES cluster ?
Are there any easy ways of the doing the same without have any
down-time to the running ES cluster ?
Appreciate any response on the same.
Thanks,
Karthik
--
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/e141b51d-99aa-4a78-b20a-2d9dcfe2e79b%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/e141b51d-99aa-4a78-b20a-2d9dcfe2e79b%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/1kgp2yjGUD0/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/DEFEB56B-5DDF-409B-829B-BAE787480C07%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/DEFEB56B-5DDF-409B-829B-BAE787480C07%40pilato.fr?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout .
--
Sarve Jana Sukhino Bhavanthu
Karthik Jayanthi
--
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/CAD7PaHzF6h1y49wWSvWNe%2BFpYAehQuJu6Zb-34HYkGLqssy2-Q%40mail.gmail.com .
For more options, visit https://groups.google.com/d/optout .