I will try to explain the situation first, if that is not enough I will try
to prepare full curl example.
I created an index alias named 1 pointing to index named 'users' with
routing (routing=1) and filter (filtering by term: user=1). Then I indexed
new data using created alias (1). Data is inserted in correct shard, so the
routing value was used properly. I can get the document by _id using
created alias (1) but I can not _search via this alias.
What is the most important, I removed alias '1' and added it again.
Now curl -XPOST localhost:9200/1/_search works fine and finds all the
created documents.
Is this description enough to investigate the problem or should I try to
recreate it step by step using curl queries ?
Could you help me with this ? Unfortunately this behavior makes index
aliases useless for me and this is necessary to make "User" data flow
working fine
I will try to explain the situation first, if that is not enough I will
try to prepare full curl example.
I created an index alias named 1 pointing to index named 'users' with
routing (routing=1) and filter (filtering by term: user=1). Then I indexed
new data using created alias (1). Data is inserted in correct shard, so the
routing value was used properly. I can get the document by _id using
created alias (1) but I can not _search via this alias.
What is the most important, I removed alias '1' and added it again.
Now curl -XPOST localhost:9200/1/_search works fine and finds all the
created documents.
Is this description enough to investigate the problem or should I try to
recreate it step by step using curl queries ?
Could you help me with this ? Unfortunately this behavior makes index
aliases useless for me and this is necessary to make "User" data flow
working fine
I will try to explain the situation first, if that is not enough I will
try to prepare full curl example.
I created an index alias named 1 pointing to index named 'users' with
routing (routing=1) and filter (filtering by term: user=1). Then I indexed
new data using created alias (1). Data is inserted in correct shard, so the
routing value was used properly. I can get the document by _id using
created alias (1) but I can not _search via this alias.
What is the most important, I removed alias '1' and added it again.
Now curl -XPOST localhost:9200/1/_search works fine and finds all the
created documents.
Is this description enough to investigate the problem or should I try to
recreate it step by step using curl queries ?
I've just noticed that if I add any document to index 'test' before
creating the alias it works fine. This case does not work for aliases
created when index is empty only. Eg. if I put
right after creating index 'test', the rest curl queries works fine
(creating alias '1' for "user":1, adding documents using alias '1' with
"user":1 and searching documents using alias '1').
Please let me know if this always behaves properly if any document exists
in the index first. I need to know if I can make such an assumption in my
project.
Could you help me with this ? Unfortunately this behavior makes index
aliases useless for me and this is necessary to make "User" data flow
working fine
I will try to explain the situation first, if that is not enough I will
try to prepare full curl example.
I created an index alias named 1 pointing to index named 'users' with
routing (routing=1) and filter (filtering by term: user=1). Then I indexed
new data using created alias (1). Data is inserted in correct shard, so the
routing value was used properly. I can get the document by _id using
created alias (1) but I can not _search via this alias.
What is the most important, I removed alias '1' and added it again.
Now curl -XPOST localhost:9200/1/_search works fine and finds all the
created documents.
Is this description enough to investigate the problem or should I try to
recreate it step by step using curl queries ?
I've just noticed that if I add any document to index 'test' before
creating the alias it works fine. This case does not work for aliases
created when index is empty only. Eg. if I put
right after creating index 'test', the rest curl queries works fine
(creating alias '1' for "user":1, adding documents using alias '1' with
"user":1 and searching documents using alias '1').
Please let me know if this always behaves properly if any document exists
in the index first. I need to know if I can make such an assumption in my
project.
Could you help me with this ? Unfortunately this behavior makes index
aliases useless for me and this is necessary to make "User" data flow
working fine
I will try to explain the situation first, if that is not enough I will
try to prepare full curl example.
I created an index alias named 1 pointing to index named 'users' with
routing (routing=1) and filter (filtering by term: user=1). Then I indexed
new data using created alias (1). Data is inserted in correct shard, so the
routing value was used properly. I can get the document by _id using
created alias (1) but I can not _search via this alias.
What is the most important, I removed alias '1' and added it again.
Now curl -XPOST localhost:9200/1/_search works fine and finds all the
created documents.
Is this description enough to investigate the problem or should I try
to recreate it step by step using curl queries ?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
