Re: Issue with unit testing TransportClient

[Alexander Reelsen]

Hey,

you might want to read:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/testing-framework.html


should help you to create tests which have a whole elasticsearch cluster
running in the background.


--Alex


On Thu, Feb 13, 2014 at 7:37 PM, joergpra...@gmail.com 
joergpra...@gmail.com wrote:

 I admit the code is confusing and too short, sorry.

 What you want is just exactly what I do.

 I start a test elasticsearch test cluster by doing this


 @BeforeMethod
 public void create() throws Exception {
 startNode(1);
 NodesInfoRequest nodesInfoRequest = new
 NodesInfoRequest().transport(true);
 NodesInfoResponse response =
 client(1).admin().cluster().nodesInfo(nodesInfoRequest).actionGet();
 InetSocketTransportAddress address =
 (InetSocketTransportAddress)response.iterator().next()
 .getTransport().getAddress().publishAddress();
 PORT = address.address().getPort();
 addresses.put(1, address);

 }

...

 protected URI getAddress() {
 return URI.create(es://localhost: + PORT + ?es.cluster.name=
 + CLUSTER);
 }


  and now I can tell a TransportClient to use the server. For this I keep a
 map of adresses of the server nodes in form of an URI.

 Look at this code, which is trivially extending the abstract test code

 @Test
 public void testBulkClient() {
 final BulkClient es = new BulkClient()
 .newClient(getAddress());
 es.shutdown();
 if (es.hasErrors()) {
 logger.error(error, es.getThrowable());
 }
 assertFalse(es.hasErrors());
 }

 I use getAddress() for the address of the elasticseach test cluster that
 is currently running, and the BulkClient (which is my custom client
 wrapping a TransportClient together with a BulkProcessor) is connecting to
 the embedded test cluster with newClient(...). In this method I build a
 Settings object that contains all the required info for the TransportClient
 to connect.

 The Setting object is something like

 settingsBuilder()
 .put(cluster.name, findClusterName(uri))
 .put(network.server, false)
 .put(node.client, true)
 .put(client.transport.sniff, false)
 .put(client.transport.ignore_cluster_name, false)
 .put(client.transport.ping_timeout, 30s)
 .put(client.transport.nodes_sampler_interval, 30s)
 .build();

 where findClusterName() is a routine to get the cluster name from the
 parameters of the test.

 The @AfterMethod shuts everything down, the BulkClient and the test
 cluster.

 If i want more nodes, I add startNode(2), startNode(3), to the
 @BeforeMethod

 Does this help?

 Jörg


  --
 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/CAKdsXoEL2w5kJby8PddkvHRdZNtAima3E1vAaEYOW%3D3mQN2_og%40mail.gmail.com
 .

 For more options, visit https://groups.google.com/groups/opt_out.


-- 
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/CAGCwEM9J7g23LTiDwci6xu5wcTKyTMxpsCancLLdjdKteur6tw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Issue with unit testing TransportClient

[SD]

Jörg,

Thanks for your response. I see that in your example you create the Node 
and get the client in the buildNode() method used by the tests..But my 
requirement is different.

I want to be able to start a test elastic search server and make my code in 
the app (not the test) use this server to give me the client..

For Example:

Lets say this is how my code is organised

-src package
   -  class ElasticSearchExtension { Client getClient() {  return new 
TransportClient().addTransportAddress(new 
InetSocketTransportAddress(config.get(host), config.get(port))); } }
-tests package
   -  class ElasticSearchExtensionTest {  testGetClient() { } }

Now in my ElasticSearchExtensionTest, I want to be able to start up a test 
elastic server and tell the getClient() in ElasticSearchExtension  to use 
the test server and give me the client...I don't want to get the client 
directly in ElasticSearchExtensionTest.

Also, thanks for your note. But we instantiate the client only once per 
module using Akka's Extensions and Bootable implementations.

Thanks,
SD

On Thursday, February 13, 2014 10:48:20 AM UTC-6, Jörg Prante wrote:

 The NodeBuilder can start an embedded Elasticsearch cluster, this is 
 exactly what you want for unit tests with a TransportClient.

 To see how this works, you can also consult my elasticsearch-support tests 
 which I stole from the original Elasticearch test code:


 https://github.com/jprante/elasticsearch-support/blob/master/src/test/java/org/xbib/elasticsearch/support/AbstractNodeTest.java

 Note, is is rather bad practice to issue a new TransportClient() each 
 time you want a client instance. Create just a singleton TransportClient 
 and pass this instance around. At instantiation, the TransportClient starts 
 the full discovery and cluster rendevzous, which takes a lng time.

 Jörg



-- 
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/9305fe60-9ef7-48e0-a6bd-82d7a788bb6d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.