I also had timing problems in my automated tests, the solution was to
invoke index refresh and wait for it, then execute any search requests.
This way you can make sure that all test data is ready for searching.
03 август 2014, неделя, 18:22:50 UTC+3, John D. Ament написа:
Hi
So after
Hmm. So how do I invoke a reindex via the java API?
On Tue, Aug 5, 2014 at 3:40 AM, Tihomir Lichev shot...@gmail.com wrote:
I also had timing problems in my automated tests, the solution was to
invoke index refresh and wait for it, then execute any search requests.
This way you can make
Sort of:
TransportClient transportClient = *new* TransportClient(settings); // just
an example of transport client instantiation, you can use your own
transportClient.getClient().admin().indices().refresh(*Requests*
.refreshRequest(indexName)).actionGet(); // actionGet() as you may know it
to
Are you refreshing the index after inserting the test documents? I could be
simply a matter of timing.
--
Ivan
On Sun, Aug 3, 2014 at 8:22 AM, John D. Ament john.d.am...@gmail.com
wrote:
Hi
So after running a few rounds of local automated tests, I've noticed that
sometimes I get the wrong
I would think timing as an issue if I got a shorter list of results. I'm
getting too many results in this case.
On Monday, August 4, 2014 12:03:35 PM UTC-4, Ivan Brusic wrote:
Are you refreshing the index after inserting the test documents? I could
be simply a matter of timing.
--
Ivan
Is it possible to provide a minimal test case with docs to reproduce this?
Jörg
On Mon, Aug 4, 2014 at 8:05 PM, John D. Ament john.d.am...@gmail.com
wrote:
I would think timing as an issue if I got a shorter list of results. I'm
getting too many results in this case.
On Monday, August 4,
Hi
So after running a few rounds of local automated tests, I've noticed that
sometimes I get the wrong results in my index. This seems to only be an
issue with my automated tests and not when running the application manually
(at least I haven't seen the wrong results after several
