Nested object docs.count anomaly

Hi,

I have a nested object JSON which I am inserting into the Elasticsearch
1.4.0.
The nested object mapping is as follows:-

{
"mappings": {
"observations": {
"properties": {
"attribute": {
"type": "nested",
"properties": {
"name": {"type": "string"},
"value": {"type": "string"},
"type": {"type": "string"}
}
}
}
}
}
}

For testing, I inserted 50,000 of such observations JSON documents(each
with 5 attributes) in Elasticsearch three times. Testing environment is
the same for all the three cases.

The output of the " *GET /_cat/indices?v *" command is given below.

Test Case - 1
health status index pri rep docs.count docs.deleted store.size
pri.store.size
green open nested 1 0 *299960 * 0 16.3mb
16.3mb

Test Case - 2
health status index pri rep docs.count docs.deleted store.size
pri.store.size
green open nested 1 0 299997 0 9.4mb
9.4mb

Test Case - 3
health status index pri rep docs.count docs.deleted store.size
pri.store.size
green open nested 1 0 300000 0 9.4mb
9.4mb

In all the three cases, the docs.count is different. Also, there is a
difference in the storage sizes.
Are data points getting lost??

My target is to store 1,000,000 data points or more. This can cause issues
as the data points grows.

--
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/4947b8f0-4318-4b09-abe9-31f6846e1e36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi,

Can you please first do optimize then do count query.
If this count and size is still inconsistent please let me know.

Thanks,
Sumit