Is there a problem with elasticsearch query_string?
Hi
i am running a search with accent chín* i am using query string but i
don't get any hits
if i use prefix then i get the correct number of results
is there any problem with query string and it is unable to handle search
with accent?
here are both search json
{
query: {
query_string: {
query: chín*,
fields: [],
use_dis_max: false,
default_operator: and,
allow_leading_wildcard: false
}
}
}
{
query: {
multi_match: {
query: ch?n*,
fields: [],
type: phrase_prefix,
max_expansions: 100,
tie_breaker: 0,
zero_terms_query: NONE
}
}
}
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/fe9cc25d-7df9-4b65-b9bf-ae43ba5ce054%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
restart leave unassigned shards
Hi we have 5 data nodes and 3 master in cluster and we are on ES 1.0 2 week ago when we restarted the it leave 1 shard unassigned for some indices. We check the Lucien index and they are fine. We create a test index and copy the Lucien index to that and it came back. But the we don’t know what is the problem why restart leave unassigned shard. There is nothing help full in logs The segments.gen file are missing for those shards. And we have 2 data directories. Andy hell will be appreciated Thanks -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/286ad5fd-7ac1-4ad5-baaf-3aa686cf68c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
restart leave unassigned shards
Hi I have to restart elasticsearch cluster nodes because of some timeout exceptions I did restart the nodes one by one there are 5 data nodes in cluster But when I did that it leave some shards unassigned and I have no replicas There is nothing help full in logs. Can I get some help to know why these shards remain unassigned and any solution Thanks -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9b9fcede-16a6-4ca0-84d0-2d7cb58e523e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
