Databases
StackOverflow2013
Postsdbo
POElasticsearch GET just after POST
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POElasticsearch GET just after POST
    primarykey
    data
    text
    <p>I'm encountering some issues when performing several <code>get_or_create</code> requests to ES. Elasticsearch seems to take some time after responding to the <code>POST</code> to index a document, so much that a <code>GET</code> called <strong>just after</strong> returns no results.</p> <p>This example reproduces the issue:</p> <pre class="lang-bash prettyprint-override"><code>curl -XPOST 'http://localhost:9200/twitter/tweet/' -d '{ "user" : "kimchy", "post_date" : "2009-11-15T14:12:12", "message" : "trying out Elastic Search" }' &amp;&amp; \ curl -XGET 'http://localhost:9200/twitter/tweet/_search' -d '{ "query" : { "term" : { "user" : "kimchy" } } }' &amp;&amp; \ sleep 1 &amp;&amp; \ curl -XGET 'http://localhost:9200/twitter/tweet/_search' -d '{ "query" : { "term" : { "user" : "kimchy" } } }' </code></pre> <p>The <code>POST</code> goes well:</p> <pre class="lang-bash prettyprint-override"><code>{ "ok": true, "_index": "twitter", "_type": "tweet", "_id": "yaLwtgSuQcWg5lzgFpuqHQ", "_version": 1 } </code></pre> <p>The first <code>GET</code> does not match any result:</p> <pre class="lang-bash prettyprint-override"><code>{ "took": 1, "timed_out": false, "_shards": { "total": 5, "successful": 5, "failed": 0 }, "hits": { "total": 0, "max_score": null, "hits": [] } } </code></pre> <p>And after a brief pause, shows the result (second <code>GET</code>):</p> <pre class="lang-bash prettyprint-override"><code>{ "took": 1, "timed_out": false, "_shards": { "total": 5, "successful": 5, "failed": 0 }, "hits": { "total": 1, "max_score": 0.30685282, "hits": [{ "_index": "twitter", "_type": "tweet", "_id": "yaLwtgSuQcWg5lzgFpuqHQ", "_score": 0.30685282, "_source": { "user": "kimchy", "post_date": "2009-11-15T14:12:12", "message": "trying out Elastic Search" } }] } } </code></pre> <p>Is that behaviour normal ?</p> <p>Is there a possibility to get the result immediately, even if the response is slower ?</p> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USLéo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POElasticsearch GET just after POST
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POElasticsearch GET just after POST
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYour index request cause a new index to be created right? You're not creating it upfront using the create index api if I understood correctly.
      singulars
      1. POElasticsearch GET just after POST
      1. USjavanna
    2. COYes, but that example is based on Elasticsearch's ones on the doc. The fact is that happenned in my environment with previously created indices. The two people below have made good answers: using the GET API would be safer for such a case.
      singulars
      1. POElasticsearch GET just after POST
      1. USLéo
    3. COSure, I hadn't noticed that, the capital http GET method confused me :) as the answers say, use get or explicitly call refresh. Cheers!
      singulars
      1. POElasticsearch GET just after POST
      1. USjavanna
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload