Hi,
Issue #896 https://github.com/elasticsearch/elasticsearch/issues/896(Sort: Support "missing" specific handling, include _last, _first, and
custom value for string values) is closed.
clintongormley https://github.com/clintongormley commented that this is
supported for numbers, dates, strings, and geo-locations as of 0.90.0.RC2.
I downloaded the 0.90.0 version but hits sorted on missing string fields
still end up first.
Suppose I have the following mapping:
"user":{
"type":"string",
"index" : "not_analyzed"
}
Then hits with missing the user field still ends up first if I were to run
the following query:
{
"query" : {
...
},
"sort" : [
{ "user" : {"order" : "asc", "missing" : "_last"} }
]
}
According to the ElasticSearch quidehttp://www.elasticsearch.org/guide/reference/api/search/sort/the missing feature only applies to numeric fields.
So I am a bit confused.
Does 0.90.0 support sorting on string fields with missing set to _last?
If not, is this an enhancement that will be implemented any time soon?
Thx,
Luk
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Luk
Hmmm, I'm not sure why I thought it had been added in 0.90.0.RC2. I've
looked through the issues list and can't find it.
I'll ask.
clint
On Wednesday, 22 May 2013 12:08:56 UTC+2, Luk Morbee wrote:
Hi,
Issue #896 https://github.com/elasticsearch/elasticsearch/issues/896(Sort: Support "missing" specific handling, include _last, _first, and
custom value for string values) is closed.
clintongormley https://github.com/clintongormley commented that this is
supported for numbers, dates, strings, and geo-locations as of
0.90.0.RC2.
I downloaded the 0.90.0 version but hits sorted on missing string fields
still end up first.
Suppose I have the following mapping:
"user":{
"type":"string",
"index" : "not_analyzed"
}
Then hits with missing the user field still ends up first if I were to run
the following query:
{
"query" : {
...
},
"sort" : [
{ "user" : {"order" : "asc", "missing" : "_last"} }
]
}
According to the Elasticsearch quidehttp://www.elasticsearch.org/guide/reference/api/search/sort/the missing feature only applies to numeric fields.
So I am a bit confused.
Does 0.90.0 support sorting on string fields with missing set to _last?
If not, is this an enhancement that will be implemented any time soon?
Thx,
Luk
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Apparently it can be supported but isn't yet. I've reopened the issue
clint
On 23 May 2013 12:27, Clinton Gormley clint@traveljury.com wrote:
Hi Luk
Hmmm, I'm not sure why I thought it had been added in 0.90.0.RC2. I've
looked through the issues list and can't find it.
I'll ask.
clint
On Wednesday, 22 May 2013 12:08:56 UTC+2, Luk Morbee wrote:
Hi,
Issue #896 https://github.com/elasticsearch/elasticsearch/issues/896(Sort: Support "missing" specific handling, include _last, _first, and
custom value for string values) is closed.
clintongormley https://github.com/clintongormley commented that this
is supported for numbers, dates, strings, and geo-locations as of
0.90.0.RC2.
I downloaded the 0.90.0 version but hits sorted on missing string fields
still end up first.
Suppose I have the following mapping:
"user":{
"type":"string",
"index" : "not_analyzed"
}
Then hits with missing the user field still ends up first if I were to
run the following query:
{
"query" : {
...
},
"sort" : [
{ "user" : {"order" : "asc", "missing" : "_last"} }
]
}
According to the Elasticsearch quidehttp://www.elasticsearch.org/guide/reference/api/search/sort/the missing feature only applies to numeric fields.
So I am a bit confused.
Does 0.90.0 support sorting on string fields with missing set to _last?
If not, is this an enhancement that will be implemented any time soon?
Thx,
Luk
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Clint,
Thanks for the feedback,
Luk
On Thursday, May 23, 2013 12:53:43 PM UTC+2, Clinton Gormley wrote:
Apparently it can be supported but isn't yet. I've reopened the issue
clint
On 23 May 2013 12:27, Clinton Gormley <cl...@traveljury.com <javascript:>>wrote:
Hi Luk
Hmmm, I'm not sure why I thought it had been added in 0.90.0.RC2. I've
looked through the issues list and can't find it.
I'll ask.
clint
On Wednesday, 22 May 2013 12:08:56 UTC+2, Luk Morbee wrote:
Hi,
Issue #896 https://github.com/elasticsearch/elasticsearch/issues/896(Sort: Support "missing" specific handling, include _last, _first, and
custom value for string values) is closed.
clintongormley https://github.com/clintongormley commented that this
is supported for numbers, dates, strings, and geo-locations as of
0.90.0.RC2.
I downloaded the 0.90.0 version but hits sorted on missing string fields
still end up first.
Suppose I have the following mapping:
"user":{
"type":"string",
"index" : "not_analyzed"
}
Then hits with missing the user field still ends up first if I were to
run the following query:
{
"query" : {
...
},
"sort" : [
{ "user" : {"order" : "asc", "missing" : "_last"} }
]
}
According to the Elasticsearch quidehttp://www.elasticsearch.org/guide/reference/api/search/sort/the missing feature only applies to numeric fields.
So I am a bit confused.
Does 0.90.0 support sorting on string fields with missing set to _last?
If not, is this an enhancement that will be implemented any time soon?
Thx,
Luk
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.