Modify index after creation


(Giovanni Colapinto) #1

Hello.

A simple question, only to be secure of what I found on the web: is it
possible to modify an index after creation? If true, what kind of
modification is supported?

Thank you

Giovanni

--
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/315c2c6f-985a-4226-940c-95a5e7f4fd1b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Brian Yoder) #2

Giovanni,

This list isn't exhaustive, but... the most useful index-level settings
that can be modified for an existing index are refresh interval and number
of replicas.

You may add character filters, tokenizers, and analyzers to an existing
index.

You may add new fields but in general cannot change an existing field's
mappings. However, I suspect you may be able to add new mappings to an
existing field within its "fields":{} object. I have never actually tried
this; I may soon since I'm now using 1.0.0.

You may add new types with new fields.

What I've actually done is to create a set of incompatible but useful
mappings for different indices that I use in testing my understanding of
Elasticsearch and to explore its nooks and crannies without affecting a
production index. I then have a command-line tool that lets me create an
index with a specified set of mappings, and then to update an existing
index with a (superset, usually) of mappings. And for the update, I let
Elsticsearch verify that the mappings are compatible; it will complain if
it thinks something isn't right. For example, it won't let you change the
"foo" field from a "long" to a "string". And this doesn't require a lot of
data (or indeed, any data at all), so it's really easy to run this test on
some locally created index in a test installation and verify the effects on
production.

Brian

--
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/0074b2da-3975-4c12-a2cd-b0eac6cd6c05%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Giovanni Colapinto) #3

Thank you Brian :slight_smile:

On Thu, Feb 27, 2014 at 9:32 PM, InquiringMind brian.from.fl@gmail.comwrote:

Giovanni,

This list isn't exhaustive, but... the most useful index-level settings
that can be modified for an existing index are refresh interval and number
of replicas.

You may add character filters, tokenizers, and analyzers to an existing
index.

You may add new fields but in general cannot change an existing field's
mappings. However, I suspect you may be able to add new mappings to an
existing field within its "fields":{} object. I have never actually tried
this; I may soon since I'm now using 1.0.0.

You may add new types with new fields.

What I've actually done is to create a set of incompatible but useful
mappings for different indices that I use in testing my understanding of
Elasticsearch and to explore its nooks and crannies without affecting a
production index. I then have a command-line tool that lets me create an
index with a specified set of mappings, and then to update an existing
index with a (superset, usually) of mappings. And for the update, I let
Elsticsearch verify that the mappings are compatible; it will complain if
it thinks something isn't right. For example, it won't let you change the
"foo" field from a "long" to a "string". And this doesn't require a lot of
data (or indeed, any data at all), so it's really easy to run this test on
some locally created index in a test installation and verify the effects on
production.

Brian

--
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/h-ooLwLlHes/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/0074b2da-3975-4c12-a2cd-b0eac6cd6c05%40googlegroups.com
.

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

--
www.syshell.net

--
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/CAK%3D2fj%2BBtehS105e20H-_MkMRhWDnmFngowuxsJOMdObb%2BHmUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #4