.
Client is thread safe. Any chance you could share on github a small
project which reproduce this error?
David
Le 23 janv. 2015 à 01:18, TimOnGmail timb...@gmail.com javascript: a
écrit :
I changed the code to use a Singleton. Even so, when I made the indexing
and searching happen
22, 2015 at 2:30:07 PM UTC-8, David Pilato wrote:
Answers inlined
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 22 janv. 2015 à 20:19, TimOnGmail timb...@gmail.com javascript: a
écrit :
Thanks for your suggestions!
I'm generally created a fresh client for each
.
You should create first the index and wait for the index to be created,
using actionGet(). It's a quick operation. Then run your code as you wrote.
My 2 cents.
David
Le 22 janv. 2015 à 06:12, TimOnGmail timb...@gmail.com javascript: a
écrit :
I have a situation where, using the Java API
I have a situation where, using the Java API, I initiate a bunch of
indexing operations, but throw away the Future object (I don't need the
return status). This is so I can do a lot of indexing reasonably
asynchronously, so I don't have to hold up the GUI that triggers these
calls.
However,
I have a situation where, using the Java API, I initiate a bunch of
indexing operations, but throw away the Future object (I don't need the
return status). This is so I can do a lot of indexing reasonably
asynchronously, so I don't have to hold up the GUI that triggers these
calls.
However,
Final bit of info, and this seems important; one TransportClient is being
run in one thread, the other in another... so it goes like this:
Thread 1: Fork Thread 1
Thread 2: Create new TransportClient; Index list of items, not waiting for
Future objects (i.e. not calling actionGet())
Thread 1:
I made a mistake in my statement above - I am using different
TransportClients for the indexing and the searching... so, one is doing the
indexing, and while that is going on, I'm doing the searching on a
different one.
- Tim
--
You received this message because you are subscribed to the
I wish I could just go back and edit prior postings. :-)
... I should mention, if I do the above, but don't create 2 threads - that
is, synchronously index each item, close the TransportClient, create
another TransportClient and do the search, it works. So this is ONLY
happening when the two
https://github.com/elasticsearch/elasticsearch/commit/fa16969360ea43667ad11f827bbf86718c18fcc6
Jörg
On Wed, Dec 3, 2014 at 1:17 AM, TimOnGmail timb...@gmail.com
javascript: wrote:
Hey folks...
I'm upgrading to the newest version of Elastic Search, and noticed that
ElasticSearchException
Hey folks...
I'm upgrading to the newest version of Elastic Search, and noticed that
ElasticSearchException was renamed to ElasticsearchException.
Was this done across the board for lots of classes? Just this class? A
mistake? Just curious what drove this.
- Tim
--
You received this
10 matches
Mail list logo
