[9.0-beta1] "Missing" counts in facets are always Zero?

I tried my application with 0.9-beta and noticed that terms and terms_stats
facets missing counts are zerow whwre with 0.2.x it calculated missing
counts. Is it needs to be turned on somehow now?

--
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.

Could you create a curl recreation and open an issue?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2013 à 01:43, AlexR roytmana@gmail.com a écrit :

I tried my application with 0.9-beta and noticed that terms and terms_stats facets missing counts are zerow whwre with 0.2.x it calculated missing counts. Is it needs to be turned on somehow now?

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 David,

I will be on customer site most of Monday and Tuesday. Will try to do it
Wednesday.
It seems to be happening consistently on every facet I have (boolean,
numeric, string terms). If you just do a simple terms facet against any of
your 0.9 index do you see "missing" > 0?

On Sun, Mar 3, 2013 at 11:12 PM, David Pilato david@pilato.fr wrote:

Could you create a curl recreation and open an issue?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2013 à 01:43, AlexR roytmana@gmail.com a écrit :

I tried my application with 0.9-beta and noticed that terms and
terms_stats facets missing counts are zerow whwre with 0.2.x it calculated
missing counts. Is it needs to be turned on somehow now?

--
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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/xQcKcNjNtME/unsubscribe?hl=en-US
.
To unsubscribe from this group and all its topics, 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.

David,

I tried reproducing it with an independent sample but was unable to.
Out of 30 facets in my app about 6 (all seem to be on numeric fields such
as fiscal year or IDs in my reference tables) return 0 "missing" no matter
what the rest are fine
In my test samples I tried some similar mappings and the same faceting but
it works as expected. Of course I only had handful of sample record (and
they are not the same structure as my real data which is deeply nested and
have over hundred fields)

Is there anything else (my real mapping, samples that did not show the
issue) I can provide?

in the example below, you see that total hits does not tally up with facets
total and "missing" is 0 while it should not been. Nothing seems to be out
of the ordinary for these failing fields and they all work fine in 0.2.5

{
"query": {
"match_all": {}
},
"from": 0,
"size": 0,
"fields": [],
"facets": {
"fy": {
"terms": {
"field": "fy",
"size": 3
}
}
}
}

{
"took": 3,
"timed_out": false,
"_shards": {
"total": 1,
"successful": 1,
"failed": 0
},
"hits": {
"total": 71159,
"max_score": 1.0,
"hits": []
},
"facets": {
"fy": {
"_type": "terms",
"missing": 0,
"total": 69355,
"other": 30687,
"terms": [
{
"term": 2006,
"count": 16003
},
{
"term": 2005,
"count": 12326
},
{
"term": 2007,
"count": 10339
}
]
}
}
}

On Sunday, March 3, 2013 11:12:09 PM UTC-5, David Pilato wrote:

Could you create a curl recreation and open an issue?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mars 2013 à 01:43, AlexR <royt...@gmail.com <javascript:>> a écrit :

I tried my application with 0.9-beta and noticed that terms and
terms_stats facets missing counts are zerow whwre with 0.2.x it calculated
missing counts. Is it needs to be turned on somehow now?

--
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.