How Elasticsearch handles conflicts between alias name and index name

Hi,

Let's say I have 2 indices: *one whose name is index_name and an other
index with alias *index_name (called second_index).

In this way there is a conflict.

How ElasticSearch handles such situation?

Does it give priority to the alias (this means when you are using
index_name it will refer to second_index)?
Or does it do the opposite (this means when you are using index_name it
will refer to the first index called index_name).

--
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/2bea2bee-0d43-4b81-a05c-f07f0f8496fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Basically there will be no conflict, because Elasticsearch does not allow
you to set an alias that is the same of an index name.

Solved!
Thanks :slight_smile:

On Thursday, July 24, 2014 2:27:12 PM UTC+2, Giovanni Gaglione wrote:

Hi,

Let's say I have 2 indices: *one whose name is index_name and an other
index with alias *index_name (called second_index).

In this way there is a conflict.

How Elasticsearch handles such situation?

Does it give priority to the alias (this means when you are using
index_name it will refer to second_index)?
Or does it do the opposite (this means when you are using index_name it
will refer to the first index called index_name).

--
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/78ac7f7b-a2a9-4bbd-886a-c80d5b1560f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.