If I understand your question, when you get the answer at Step 2, your document is on all nodes which requires it. But not available for search immediatly though get will work. 1 second later max, it will be available for search (on all nodes that is).
You can for demo purpose force the refresh using refresh API so your doc will be searchable after the refresh operation. Note that it could be a parameter to your index operation. Hope this helps -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 7 mars 2014 à 07:55, prashy <prashant.agra...@paladion.net> a écrit : There are two scenario. 1) I am submitting the documents to ES for indexing. 2) I am executing a search query using cluster plugin. Just to elaborate through example. *Step 1: *curl -xPOST 'http://192.168.0.179:9200/prashant' -d { "mappings": { "emp": { "properties": { "empid": {"type":"long", "store":"no", "precision_step":"0" }, "empname": {"type":"string", "store":"yes", "index":"analyzed" }, "empage": {"type":"integer", "store":"yes", "precision_step":"0" }, "empstatus": {"type":"string", "store":"yes", "index":"analyzed" } } } } } *Step 2: *Now adding the documnets by : curl -xPOST 'http://192.168.0.179:9200/prashant/emp' -d { "empid": 1, "empname": "ABC", "empage": 25, "empstatus":"permanent" } *Step 3: *Now if I _search_with_clusters for the documents like { "search_request": { "query": { "match": { "_all": "ABC" } }, "size": 1000, "from":0 }, "query_hint": "", "field_mapping": { "content": [ "_source.empname" ] }, "algorithm": "lingo3g" } It will return 1000 of record in hierarchical structure with the cluster label and all. *So my question is whether the clustering of documents will happen at step2 or step3?* -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Real-time-vs-On-demand-cluster-tp4051151p4051258.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1394175348897-4051258.post%40n3.nabble.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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/83B3F3E3-3504-4061-8E97-A3FB1696E0D2%40pilato.fr. For more options, visit https://groups.google.com/d/optout.
