# When a specific index is not specified, what do the additional entries in the response signify? **URL:** \ **Category:** Elasticsearch\ **Created:** [March 6, 2012, 6:00am UTC](https://discuss.elastic.co/t/when-a-specific-index-is-not-specified-what-do-the-additional-entries-in-the-response-signify/6902 "2012-03-06T06:00:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pulkitsinghal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pulkitsinghal/32/802_2.png) [@pulkitsinghal](https://discuss.elastic.co/u/pulkitsinghal)\ **Post date:** [March 6, 2012, 6:00am UTC](https://discuss.elastic.co/t/when-a-specific-index-is-not-specified-what-do-the-additional-entries-in-the-response-signify/6902/1 "2012-03-06T06:00:24Z")
If a search is performed with an index specified: curl -XPOST [http://localhost:9200/my\_specific\_index/\_search/](http://localhost:9200/my_specific_index/_search/) -d '{ "fields": [ "upc" ], "query": { "match\_all": {} } }' Then I receive the correct # of total hits and 10 upc fields are returned in the hits array as results. BUT if the index is not specified then 3 out of the 10 entries that are returned in the hits array ... seem to have some kind of control information specified in them and I'm not sure what the significance/ motivation behind that is: hits: [ { \_index: \_river \_type: my\_specific\_index\_river \_id: \_meta \_score: 1 } { \_index: \_river \_type: my\_specific\_index\_river \_id: \_seq \_score: 1 } { \_index: \_river \_type: my\_specific\_index\_river \_id: \_status \_score: 1 } ... Can someone please point me to a reference page on ES for this? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 6, 2012, 6:33am UTC](https://discuss.elastic.co/t/when-a-specific-index-is-not-specified-what-do-the-additional-entries-in-the-response-signify/6902/2 "2012-03-06T06:33:40Z")
These are river internals values. It depends on your river plugin. HTH David 😉 @dadoonet Le 6 mars 2012 à 07:00, pulkitsinghal [pulkitsinghal@gmail.com](mailto:pulkitsinghal@gmail.com) a écrit : > If a search is performed with an index specified: > curl -XPOST [http://localhost:9200/my\_specific\_index/\_search/](http://localhost:9200/my_specific_index/_search/) -d '{ > "fields": [ > "upc" > ], > "query": { > "match\_all": {} > } > }' > Then I receive the correct # of total hits and 10 upc fields are > returned in the hits array as results. > > BUT if the index is not specified then 3 out of the 10 entries that > are returned in the hits array ... seem to have some kind of control > information specified in them and I'm not sure what the significance/ > motivation behind that is: > > hits: [ > { > \_index: \_river > \_type: my\_specific\_index\_river > \_id: \_meta > \_score: 1 > } > { > \_index: \_river > \_type: my\_specific\_index\_river > \_id: \_seq > \_score: 1 > } > { > \_index: \_river > \_type: my\_specific\_index\_river > \_id: \_status > \_score: 1 > } > ... > > Can someone please point me to a reference page on ES for this? ---
**Author:** ![pulkitsinghal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pulkitsinghal/32/802_2.png) [@pulkitsinghal](https://discuss.elastic.co/u/pulkitsinghal)\ **Post date:** [March 6, 2012, 5:24pm UTC](https://discuss.elastic.co/t/when-a-specific-index-is-not-specified-what-do-the-additional-entries-in-the-response-signify/6902/3 "2012-03-06T17:24:23Z")
That is very ambiguous, can you elaborate? What does having a river plugin, have to do with getting entries in a search result that don't have any of the matching search fields? Also this is a run of the mill CouchDB river plugin. Sent from my iPhone On Mar 6, 2012, at 12:33 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > These are river internals values. > It depends on your river plugin. > > HTH > David 😉 > @dadoonet > > Le 6 mars 2012 à 07:00, pulkitsinghal [pulkitsinghal@gmail.com](mailto:pulkitsinghal@gmail.com) a écrit : > > > If a search is performed with an index specified: > > curl -XPOST [http://localhost:9200/my\_specific\_index/\_search/](http://localhost:9200/my_specific_index/_search/) -d '{ > > "fields": [ > > "upc" > > ], > > "query": { > > "match\_all": {} > > } > > }' > > Then I receive the correct # of total hits and 10 upc fields are > > returned in the hits array as results. > > > > BUT if the index is not specified then 3 out of the 10 entries that > > are returned in the hits array ... seem to have some kind of control > > information specified in them and I'm not sure what the significance/ > > motivation behind that is: > > > > hits: [ > > { > > \_index: \_river > > \_type: my\_specific\_index\_river > > \_id: \_meta > > \_score: 1 > > } > > { > > \_index: \_river > > \_type: my\_specific\_index\_river > > \_id: \_seq > > \_score: 1 > > } > > { > > \_index: \_river > > \_type: my\_specific\_index\_river > > \_id: \_status > > \_score: 1 > > } > > ... > > > > Can someone please point me to a reference page on ES for this? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 6, 2012, 6:26pm UTC](https://discuss.elastic.co/t/when-a-specific-index-is-not-specified-what-do-the-additional-entries-in-the-response-signify/6902/4 "2012-03-06T18:26:14Z")
A river needs to store some internals values. For couchDb, it's the last sequence number provided by the \_change API. More, a river need to store its settings : couchDb URL, port, ... Es store this as Json documents in \_river _special_ index. This way, river settings are "duplicated" in the cluster. If a node failed, a second one will continue the job. Hope it's a bit more clear 🙂 David 😉 @dadoonet Le 6 mars 2012 à 18:24, [pulkitsinghal@gmail.com](mailto:pulkitsinghal@gmail.com) a écrit : > That is very ambiguous, can you elaborate? > > What does having a river plugin, have to do with getting entries in a search result that don't have any of the matching search fields? > > Also this is a run of the mill CouchDB river plugin. > > Sent from my iPhone > > On Mar 6, 2012, at 12:33 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > > > These are river internals values. > > It depends on your river plugin. > > > > HTH > > David 😉 > > @dadoonet > > > > Le 6 mars 2012 à 07:00, pulkitsinghal [pulkitsinghal@gmail.com](mailto:pulkitsinghal@gmail.com) a écrit : > > > > > If a search is performed with an index specified: > > > curl -XPOST [http://localhost:9200/my\_specific\_index/\_search/](http://localhost:9200/my_specific_index/_search/) -d '{ > > > "fields": [ > > > "upc" > > > ], > > > "query": { > > > "match\_all": {} > > > } > > > }' > > > Then I receive the correct # of total hits and 10 upc fields are > > > returned in the hits array as results. > > > > > > BUT if the index is not specified then 3 out of the 10 entries that > > > are returned in the hits array ... seem to have some kind of control > > > information specified in them and I'm not sure what the significance/ > > > motivation behind that is: > > > > > > hits: [ > > > { > > > \_index: \_river > > > \_type: my\_specific\_index\_river > > > \_id: \_meta > > > \_score: 1 > > > } > > > { > > > \_index: \_river > > > \_type: my\_specific\_index\_river > > > \_id: \_seq > > > \_score: 1 > > > } > > > { > > > \_index: \_river > > > \_type: my\_specific\_index\_river > > > \_id: \_status > > > \_score: 1 > > > } > > > ... > > > > > > Can someone please point me to a reference page on ES for this? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 6, 2012, 6:29pm UTC](https://discuss.elastic.co/t/when-a-specific-index-is-not-specified-what-do-the-additional-entries-in-the-response-signify/6902/5 "2012-03-06T18:29:19Z")
I will add that it's strange that you get this result. You asked to search in a specific index but you get documents from the \_river index. David 😉 @dadoonet Le 6 mars 2012 à 19:26, David Pilato [david@pilato.fr](mailto:david@pilato.fr) a écrit : > A river needs to store some internals values. For couchDb, it's the last sequence number provided by the \_change API. > More, a river need to store its settings : couchDb URL, port, ... > > Es store this as Json documents in \_river _special_ index. > This way, river settings are "duplicated" in the cluster. If a node failed, a second one will continue the job. > > Hope it's a bit more clear 🙂 > > David 😉 > @dadoonet > > Le 6 mars 2012 à 18:24, [pulkitsinghal@gmail.com](mailto:pulkitsinghal@gmail.com) a écrit : > > > That is very ambiguous, can you elaborate? > > > > What does having a river plugin, have to do with getting entries in a search result that don't have any of the matching search fields? > > > > Also this is a run of the mill CouchDB river plugin. > > > > Sent from my iPhone > > > > On Mar 6, 2012, at 12:33 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > > > > > These are river internals values. > > > It depends on your river plugin. > > > > > > HTH > > > David 😉 > > > @dadoonet > > > > > > Le 6 mars 2012 à 07:00, pulkitsinghal [pulkitsinghal@gmail.com](mailto:pulkitsinghal@gmail.com) a écrit : > > > > > > > If a search is performed with an index specified: > > > > curl -XPOST [http://localhost:9200/my\_specific\_index/\_search/](http://localhost:9200/my_specific_index/_search/) -d '{ > > > > "fields": [ > > > > "upc" > > > > ], > > > > "query": { > > > > "match\_all": {} > > > > } > > > > }' > > > > Then I receive the correct # of total hits and 10 upc fields are > > > > returned in the hits array as results. > > > > > > > > BUT if the index is not specified then 3 out of the 10 entries that > > > > are returned in the hits array ... seem to have some kind of control > > > > information specified in them and I'm not sure what the significance/ > > > > motivation behind that is: > > > > > > > > hits: [ > > > > { > > > > \_index: \_river > > > > \_type: my\_specific\_index\_river > > > > \_id: \_meta > > > > \_score: 1 > > > > } > > > > { > > > > \_index: \_river > > > > \_type: my\_specific\_index\_river > > > > \_id: \_seq > > > > \_score: 1 > > > > } > > > > { > > > > \_index: \_river > > > > \_type: my\_specific\_index\_river > > > > \_id: \_status > > > > \_score: 1 > > > > } > > > > ... > > > > > > > > Can someone please point me to a reference page on ES for this? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:37am UTC](https://discuss.elastic.co/t/when-a-specific-index-is-not-specified-what-do-the-additional-entries-in-the-response-signify/6902/6 "2017-07-06T03:37:09Z")
Closed on July 6, 2017, 3:37am UTC