Are you sure you are not using any routing value when indexing? If so, could you recreate a curl/Sense recreation which reproduce the problem?
-- David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 26 mai 2014 à 15:30:43, Pir Abdul Rasool Qureshi ([email protected]) a écrit: { "OurIndex": { "mappings": { "OurType": { "properties": { "added": { "type": "date", "format": "dateOptionalTime" }, "adult_content": { "type": "boolean" }, "bucket_id": { "type": "short" }, "company_id": { "type": "long" }, "created": { "type": "date", "format": "dateOptionalTime" }, "da_keywords_1": { "type": "string" }, "da_keywords_2": { "type": "string" }, "da_keywords_3": { "type": "string" }, "da_keywords_4": { "type": "string" }, "da_keywords_5": { "type": "string" }, "da_text_keywords_1": { "type": "string", "analyzer": "danish" }, "da_text_keywords_2": { "type": "string", "analyzer": "danish" }, "da_text_keywords_3": { "type": "string", "analyzer": "danish" }, "da_text_keywords_4": { "type": "string", "analyzer": "danish" }, "da_text_keywords_5": { "type": "string", "analyzer": "danish" }, "da_text_title": { "type": "string", "analyzer": "danish" }, "da_title": { "type": "string" }, "de_keywords_1": { "type": "string" }, "de_keywords_2": { "type": "string" }, "de_keywords_3": { "type": "string" }, "de_keywords_4": { "type": "string" }, "de_keywords_5": { "type": "string" }, "de_text_keywords_1": { "type": "string", "analyzer": "german" }, "de_text_keywords_2": { "type": "string", "analyzer": "german" }, "de_text_keywords_3": { "type": "string", "analyzer": "german" }, "de_text_keywords_4": { "type": "string", "analyzer": "german" }, "de_text_keywords_5": { "type": "string", "analyzer": "german" }, "de_text_title": { "type": "string", "analyzer": "german" }, "de_title": { "type": "string" }, "dimension": { "type": "string" }, "duration": { "type": "integer" }, "editorial": { "type": "string" }, "en_keywords_1": { "type": "string" }, "en_keywords_2": { "type": "string" }, "en_keywords_3": { "type": "string" }, "en_keywords_4": { "type": "string" }, "en_keywords_5": { "type": "string" }, "en_text_keywords_1": { "type": "string", "analyzer": "english" }, "en_text_keywords_2": { "type": "string", "analyzer": "english" }, "en_text_keywords_3": { "type": "string", "analyzer": "english" }, "en_text_keywords_4": { "type": "string", "analyzer": "english" }, "en_text_keywords_5": { "type": "string", "analyzer": "english" }, "en_text_title": { "type": "string", "analyzer": "english" }, "en_title": { "type": "string" }, "folder_ids": { "type": "long" }, "height": { "type": "integer" }, "id": { "type": "string" }, "f_id": { "type": "long" }, "media_type": { "type": "string" }, "orientation": { "type": "string" }, "published": { "type": "date", "format": "dateOptionalTime" }, "resolution": { "type": "string" }, "status": { "type": "string" }, "supplier_id": { "type": "long" }, "db_id": { "type": "long" }, "width": { "type": "integer" } } } } } } On Monday, May 26, 2014 3:09:18 PM UTC+2, David Pilato wrote: What is your mapping? -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 26 mai 2014 à 14:59, Pir Abdul Rasool Qureshi <[email protected]> a écrit : No, We are not using Parent/Child. On Monday, May 26, 2014 1:54:11 PM UTC+2, David Pilato wrote: Are you using parent child ? -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 26 mai 2014 à 13:50, Pir Abdul Rasool Qureshi <[email protected]> a écrit : It gives me the (expected) value i.e. 3624608. Details: Query 1: ====== If I do curl -XGET "http://somehost:9200/colourbox/OurIndex/OurType/_search?q=_id:3624608";, it retrieves a single document with _id = 3624608 Query 2: ====== If I do curl -XGET "http://somehost:9200/colourbox/OurIndex/OurType/3624608"; it results in { "_index": "OurIndex", "_type": "OurType", "_id": "3624608", "found": false } Query 3: ======= If I do curl -XGET "http://somehost:9200/OurIndex/OurType/3624608?routing=1"; it retrieves a single document with _id = 3624608 Thanks On Monday, May 26, 2014 12:14:26 PM UTC+2, Itamar Syn-Hershko wrote: When you search, what does the _id field of the result indicate? -- Itamar Syn-Hershko http://code972.com | @synhershko Freelance Developer & Consultant Author of RavenDB in Action On Mon, May 26, 2014 at 11:32 AM, Pir Abdul Rasool Qureshi <[email protected]> wrote: Yes we are specifying index name and type in urls. The curl request looks like the following, curl -XGET "http://somehost:9200/OurIndex/OurType/3624608"; where 3624608 is id of the document Thanks On Monday, May 26, 2014 9:49:33 AM UTC+2, Itamar Syn-Hershko wrote: What is the exact URLs you're approaching? Are you specifying the index name and type name as well in your GET ? -- Itamar Syn-Hershko http://code972.com | @synhershko Freelance Developer & Consultant Author of RavenDB in Action On Mon, May 26, 2014 at 10:47 AM, Pir Abdul Rasool Qureshi <[email protected]> wrote: Hi We have a single machine elastic search server (8 shards but all hosted at the same machine). Index contains 7 million documents. We do not specify any custom routing when indexing the documents. We are using Elastic search version 1.2. The problem is that we are unable to retrieve many of our documents using GET <the id>, . However using search?_id:<the id> we are able to retrieve all of those documents. We are also successful in retrieving a document by specifying routing parameter (with different values (1,2,3,...) ) with GET. With previous version, i.e. Elastic Search 1.0.3, we did not have that problem. Any suggestions for resolution? 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d27e9ca7-4f7e-41c0-a1e9-538ef1565aba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/696d57ae-2c89-4de0-8269-4abed03ba15f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/414ce221-e287-47b9-ab4b-d791a6e3983b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/40eec5a2-55b2-4841-8618-dd54711d1062%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7166fa5a-6182-49ae-9666-28fb2fa43da2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.53834268.419ac241.1e56%40MacBook-Air-de-David.local. For more options, visit https://groups.google.com/d/optout.
