Inconsistent document existence between search and get?

kakaner · November 17, 2013, 7:58am

I have a document that shows up when using the search api but not get.

The document is in index A, with type B, and id N.

The following endpoints yield:
host:9200/_search => finds document
host:9200/A/_search => finds document
host:9200/A/B/_search => finds document
host:9200/A/B/N => document doesn't exist (returns false)

However, documents with other ID's do exist when I use the get route. I've
been able to replicate this behavior only with several documents in my set.
I have only performed indexing commands, no deletes or updates. The
document is not wellformed when returned in search.

Are any of you aware of a case that could cause this type of behavior? Just
for clarity I've pasted some relevant JSON outputs into the following gist:

gist.github.com

https://gist.github.com/kakaner/7510332

907_video_get.json

HOST:9200/messages_2010_04/video/907

{
  _index: "messages_2010_04",
  _type: "video",
  _id: "907",
  exists: false
}

search_all.json

HOST:9200/_search

{
  took: 11,
  timed_out: false,
  _shards: {
    total: 64,
    successful: 64,
    failed: 0
  },

This file has been truncated. show original

video_subtype_search.json

HOST:9200/messages_2010_04/video/_search

{
  took: 50,
  timed_out: false,
  _shards: {
    total: 64,
    successful: 64,
    failed: 0
  },

This file has been truncated. show original

Thanks in advance!!

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

dadoonet · November 17, 2013, 9:06am

Did you use route or parent/child when indexing?

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

Le 17 nov. 2013 à 08:58, kakaner kakaner@gmail.com a écrit :

I have a document that shows up when using the search api but not get.

The document is in index A, with type B, and id N.

The following endpoints yield:
host:9200/_search => finds document
host:9200/A/_search => finds document
host:9200/A/B/_search => finds document
host:9200/A/B/N => document doesn't exist (returns false)

However, documents with other ID's do exist when I use the get route. I've been able to replicate this behavior only with several documents in my set. I have only performed indexing commands, no deletes or updates. The document is not wellformed when returned in search.

Are any of you aware of a case that could cause this type of behavior? Just for clarity I've pasted some relevant JSON outputs into the following gist:
Elasticsearch document existence inconsistencies example · GitHub

Thanks in advance!!

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.

kakaner · November 18, 2013, 1:50am

Ah! I used routing. Dumb problem solved-- thanks!

On Sunday, November 17, 2013 4:06:30 AM UTC-5, David Pilato wrote:

Did you use route or parent/child when indexing?

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

Le 17 nov. 2013 à 08:58, kakaner <kak...@gmail.com <javascript:>> a
écrit :

I have a document that shows up when using the search api but not get.

The document is in index A, with type B, and id N.

The following endpoints yield:
host:9200/_search => finds document
host:9200/A/_search => finds document
host:9200/A/B/_search => finds document
host:9200/A/B/N => document doesn't exist (returns false)

However, documents with other ID's do exist when I use the get route. I've
been able to replicate this behavior only with several documents in my set.
I have only performed indexing commands, no deletes or updates. The
document is not wellformed when returned in search.

Are any of you aware of a case that could cause this type of behavior?
Just for clarity I've pasted some relevant JSON outputs into the following
gist:
Elasticsearch document existence inconsistencies example · GitHub

Thanks in advance!!

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