I have a query on method setTimeout() of SearchRequestBuilder. We have set a timeout value of 1 milliseconds while creating SearchRequestBuilder to execute the query. When we get the SearchResponse object and extract total time taken by executing the method getTookInMillis() of SearchResponse class, the total time comes as 100 milliseconds. That means query should have timed out as we have set time out value of 1 milliseconds earlier, still we are getting the result. It means that timeout value set in SearchRequestBuilder is not working.
When we check the docs for SearchRequestBuilder, it says that setTimeout() method allow us to set 'an optional timeout to control how long search is allowed to take'.
Can you please suggest if we are interpreting or doing something wrong!
On Wednesday, April 17, 2013 5:27:01 AM UTC-4, Kranti wrote:
Hi,
I have a query on method setTimeout() of SearchRequestBuilder. We have set
a
timeout value of 1 milliseconds while creating SearchRequestBuilder to
execute the query. When we get the SearchResponse object and extract total
time taken by executing the method getTookInMillis() of SearchResponse
class, the total time comes as 100 milliseconds. That means query should
have timed out as we have set time out value of 1 milliseconds earlier,
still we are getting the result. It means that timeout value set in
SearchRequestBuilder is not working.
When we check the docs for SearchRequestBuilder, it says that setTimeout()
method allow us to set 'an optional timeout to control how long search is
allowed to take'.
Can you please suggest if we are interpreting or doing something wrong!
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.