ElasticSearch Java-API: Client-Erstellung

Question

Müssen wir für jede Operation ein Client-Objekt erstellen oder das einzige Objekt für alle Operationen während des Lebenszyklus der Anwendung verwenden?

Answer 1

Sie können eine TransportClient instanziiert wie im documentation erklärt:

TransportClient client = new PreBuiltTransportClient(Settings.EMPTY) 
     .addTransportAddress(new InetSocketTransportAddress(InetAddress.getByName("host1"), 9300)) 
     .addTransportAddress(new InetSocketTransportAddress(InetAddress.getByName("host2"), 9300)); 

Instanz Dieser Client erben alle Methoden aus der AbstractClient:

admin, bulk, bulk, clearScroll, clearScroll, count, count, delete, 
delete, deleteIndexedScript, deleteIndexedScript, execute, execute, exists, 
exists, explain, explain, fieldStats, fieldStats, get, get, 
getIndexedScript, getIndexedScript, headers, index, index, multiGet, multiGet, multiPercolate, multiPercolate, multiSearch, multiSearch, 
multiTermVectors, multiTermVectors, percolate, percolate, prepareBulk, 
prepareClearScroll, prepareCount, prepareDelete, prepareDelete, 
prepareDeleteIndexedScript, prepareDeleteIndexedScript, prepareExecute, 
prepareExists, prepareExplain, prepareFieldStats, prepareGet, 
prepareGet, prepareGetIndexedScript, prepareGetIndexedScript, 
prepareIndex, prepareIndex, prepareIndex, prepareMultiGet, 
prepareMultiPercolate, prepareMultiSearch, prepareMultiTermVectors, 
preparePercolate, preparePutIndexedScript, preparePutIndexedScript, 
prepareSearch, prepareSearchScroll, prepareSuggest, prepareTermVector, 
prepareTermVector, prepareTermVectors, prepareTermVectors, 
prepareUpdate, prepareUpdate, putIndexedScript, putIndexedScript, 
search, search, searchScroll, searchScroll, settings, suggest, suggest, 
termVector, termVector, termVectors, termVectors, threadPool, update, 
update 

So Ihre Frage zu beantworten; Sie können dasselbe Clientobjekt mehrmals verwenden.