457 lines
26 KiB
Java
Raw Normal View History

package org.elasticsearch.document;
import org.elasticsearch.action.bulk.BulkRequestBuilder;
import org.elasticsearch.action.bulk.BulkResponse;
import org.elasticsearch.action.get.GetResponse;
import org.elasticsearch.action.index.IndexResponse;
import org.elasticsearch.action.search.SearchResponse;
import org.elasticsearch.action.update.UpdateRequestBuilder;
import org.elasticsearch.action.update.UpdateResponse;
import org.elasticsearch.common.Priority;
import org.elasticsearch.common.bytes.BytesArray;
import org.elasticsearch.common.settings.ImmutableSettings;
import org.elasticsearch.index.VersionType;
import org.elasticsearch.index.query.QueryBuilders;
import org.elasticsearch.AbstractSharedClusterTest;
import org.junit.Test;
import java.util.concurrent.CyclicBarrier;
import static org.elasticsearch.common.xcontent.XContentFactory.jsonBuilder;
import static org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertNoFailures;
import static org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertSearchHits;
import static org.hamcrest.Matchers.*;
/**
*/
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
public class BulkTests extends AbstractSharedClusterTest {
@Test
public void testBulkUpdate_simple() throws Exception {
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().admin().indices().prepareCreate("test")
.setSettings(
ImmutableSettings.settingsBuilder()
.put("index.number_of_shards", 2)
.put("index.number_of_replicas", 0)
).execute().actionGet();
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().admin().cluster().prepareHealth().setWaitForEvents(Priority.LANGUID).setWaitForGreenStatus().execute().actionGet();
BulkResponse bulkResponse = client().prepareBulk()
.add(client().prepareIndex().setIndex("test").setType("type1").setId("1").setSource("field", 1))
.add(client().prepareIndex().setIndex("test").setType("type1").setId("2").setSource("field", 2).setCreate(true))
.add(client().prepareIndex().setIndex("test").setType("type1").setId("3").setSource("field", 3))
.add(client().prepareIndex().setIndex("test").setType("type1").setId("4").setSource("field", 4))
.add(client().prepareIndex().setIndex("test").setType("type1").setId("5").setSource("field", 5))
.execute().actionGet();
assertThat(bulkResponse.hasFailures(), equalTo(false));
assertThat(bulkResponse.getItems().length, equalTo(5));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
bulkResponse = client().prepareBulk()
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("1").setScript("ctx._source.field += 1"))
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("2").setScript("ctx._source.field += 1").setRetryOnConflict(3))
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("3").setDoc(jsonBuilder().startObject().field("field1", "test").endObject()))
.execute().actionGet();
assertThat(bulkResponse.hasFailures(), equalTo(false));
assertThat(bulkResponse.getItems().length, equalTo(3));
assertThat(((UpdateResponse) bulkResponse.getItems()[0].getResponse()).getId(), equalTo("1"));
assertThat(((UpdateResponse) bulkResponse.getItems()[0].getResponse()).getVersion(), equalTo(2l));
assertThat(((UpdateResponse) bulkResponse.getItems()[1].getResponse()).getId(), equalTo("2"));
assertThat(((UpdateResponse) bulkResponse.getItems()[1].getResponse()).getVersion(), equalTo(2l));
assertThat(((UpdateResponse) bulkResponse.getItems()[2].getResponse()).getId(), equalTo("3"));
assertThat(((UpdateResponse) bulkResponse.getItems()[2].getResponse()).getVersion(), equalTo(2l));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
GetResponse getResponse = client().prepareGet().setIndex("test").setType("type1").setId("1").setFields("field").execute().actionGet();
assertThat(getResponse.isExists(), equalTo(true));
assertThat(getResponse.getVersion(), equalTo(2l));
assertThat(((Long) getResponse.getField("field").getValue()), equalTo(2l));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
getResponse = client().prepareGet().setIndex("test").setType("type1").setId("2").setFields("field").execute().actionGet();
assertThat(getResponse.isExists(), equalTo(true));
assertThat(getResponse.getVersion(), equalTo(2l));
assertThat(((Long) getResponse.getField("field").getValue()), equalTo(3l));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
getResponse = client().prepareGet().setIndex("test").setType("type1").setId("3").setFields("field1").execute().actionGet();
assertThat(getResponse.isExists(), equalTo(true));
assertThat(getResponse.getVersion(), equalTo(2l));
assertThat(getResponse.getField("field1").getValue().toString(), equalTo("test"));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
bulkResponse = client().prepareBulk()
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("6").setScript("ctx._source.field += 1")
.setUpsert(jsonBuilder().startObject().field("field", 0).endObject()))
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("7").setScript("ctx._source.field += 1"))
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("2").setScript("ctx._source.field += 1"))
.execute().actionGet();
assertThat(bulkResponse.hasFailures(), equalTo(true));
assertThat(bulkResponse.getItems().length, equalTo(3));
assertThat(((UpdateResponse) bulkResponse.getItems()[0].getResponse()).getId(), equalTo("6"));
assertThat(((UpdateResponse) bulkResponse.getItems()[0].getResponse()).getVersion(), equalTo(1l));
assertThat(bulkResponse.getItems()[1].getResponse(), nullValue());
assertThat(bulkResponse.getItems()[1].getFailure().getId(), equalTo("7"));
assertThat(bulkResponse.getItems()[1].getFailure().getMessage(), containsString("DocumentMissingException"));
assertThat(((UpdateResponse) bulkResponse.getItems()[2].getResponse()).getId(), equalTo("2"));
assertThat(((UpdateResponse) bulkResponse.getItems()[2].getResponse()).getVersion(), equalTo(3l));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
getResponse = client().prepareGet().setIndex("test").setType("type1").setId("6").setFields("field").execute().actionGet();
assertThat(getResponse.isExists(), equalTo(true));
assertThat(getResponse.getVersion(), equalTo(1l));
assertThat(((Long) getResponse.getField("field").getValue()), equalTo(0l));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
getResponse = client().prepareGet().setIndex("test").setType("type1").setId("7").setFields("field").execute().actionGet();
assertThat(getResponse.isExists(), equalTo(false));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
getResponse = client().prepareGet().setIndex("test").setType("type1").setId("2").setFields("field").execute().actionGet();
assertThat(getResponse.isExists(), equalTo(true));
assertThat(getResponse.getVersion(), equalTo(3l));
assertThat(((Long) getResponse.getField("field").getValue()), equalTo(4l));
}
@Test
public void testBulkVersioning() throws Exception {
createIndex("test");
ensureGreen();
BulkResponse bulkResponse = run(client().prepareBulk()
.add(client().prepareIndex("test", "type", "1").setCreate(true).setSource("field", "1"))
.add(client().prepareIndex("test", "type", "2").setCreate(true).setSource("field", "1"))
.add(client().prepareIndex("test", "type", "1").setSource("field", "2")));
assertTrue(((IndexResponse) bulkResponse.getItems()[0].getResponse()).isCreated());
assertThat(((IndexResponse) bulkResponse.getItems()[0].getResponse()).getVersion(), equalTo(1l));
assertTrue(((IndexResponse) bulkResponse.getItems()[1].getResponse()).isCreated());
assertThat(((IndexResponse) bulkResponse.getItems()[1].getResponse()).getVersion(), equalTo(1l));
assertFalse(((IndexResponse) bulkResponse.getItems()[2].getResponse()).isCreated());
assertThat(((IndexResponse) bulkResponse.getItems()[2].getResponse()).getVersion(), equalTo(2l));
bulkResponse = run(client().prepareBulk()
.add(client().prepareUpdate("test", "type", "1").setVersion(4l).setDoc("field", "2"))
.add(client().prepareUpdate("test", "type", "2").setDoc("field", "2"))
.add(client().prepareUpdate("test", "type", "1").setVersion(2l).setDoc("field", "3")));
assertThat(bulkResponse.getItems()[0].getFailureMessage(), containsString("Version"));
assertThat(((UpdateResponse) bulkResponse.getItems()[1].getResponse()).getVersion(), equalTo(2l));
assertThat(((UpdateResponse) bulkResponse.getItems()[2].getResponse()).getVersion(), equalTo(3l));
bulkResponse = run(client().prepareBulk()
.add(client().prepareIndex("test", "type", "e1").setCreate(true).setSource("field", "1").setVersion(10).setVersionType(VersionType.EXTERNAL))
.add(client().prepareIndex("test", "type", "e2").setCreate(true).setSource("field", "1").setVersion(10).setVersionType(VersionType.EXTERNAL))
.add(client().prepareIndex("test", "type", "e1").setSource("field", "2").setVersion(12).setVersionType(VersionType.EXTERNAL)));
assertTrue(((IndexResponse) bulkResponse.getItems()[0].getResponse()).isCreated());
assertThat(((IndexResponse) bulkResponse.getItems()[0].getResponse()).getVersion(), equalTo(10l));
assertTrue(((IndexResponse) bulkResponse.getItems()[1].getResponse()).isCreated());
assertThat(((IndexResponse) bulkResponse.getItems()[1].getResponse()).getVersion(), equalTo(10l));
assertFalse(((IndexResponse) bulkResponse.getItems()[2].getResponse()).isCreated());
assertThat(((IndexResponse) bulkResponse.getItems()[2].getResponse()).getVersion(), equalTo(12l));
bulkResponse = run(client().prepareBulk()
.add(client().prepareUpdate("test", "type", "e1").setVersion(4l).setDoc("field", "2").setVersion(10).setVersionType(VersionType.EXTERNAL))
.add(client().prepareUpdate("test", "type", "e2").setDoc("field", "2").setVersion(15).setVersionType(VersionType.EXTERNAL))
.add(client().prepareUpdate("test", "type", "e1").setVersion(2l).setDoc("field", "3").setVersion(15).setVersionType(VersionType.EXTERNAL)));
assertThat(bulkResponse.getItems()[0].getFailureMessage(), containsString("Version"));
assertThat(((UpdateResponse) bulkResponse.getItems()[1].getResponse()).getVersion(), equalTo(15l));
assertThat(((UpdateResponse) bulkResponse.getItems()[2].getResponse()).getVersion(), equalTo(15l));
}
@Test
public void testBulkUpdate_malformedScripts() throws Exception {
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().admin().indices().prepareDelete().execute().actionGet();
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().admin().indices().prepareCreate("test")
.setSettings(
ImmutableSettings.settingsBuilder()
.put("index.number_of_shards", 2)
.put("index.number_of_replicas", 0)
).execute().actionGet();
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().admin().cluster().prepareHealth().setWaitForEvents(Priority.LANGUID).setWaitForGreenStatus().execute().actionGet();
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
BulkResponse bulkResponse = client().prepareBulk()
.add(client().prepareIndex().setIndex("test").setType("type1").setId("1").setSource("field", 1))
.add(client().prepareIndex().setIndex("test").setType("type1").setId("2").setSource("field", 1))
.add(client().prepareIndex().setIndex("test").setType("type1").setId("3").setSource("field", 1))
.execute().actionGet();
assertThat(bulkResponse.hasFailures(), equalTo(false));
assertThat(bulkResponse.getItems().length, equalTo(3));
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
bulkResponse = client().prepareBulk()
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("1").setScript("ctx._source.field += a").setFields("field"))
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("2").setScript("ctx._source.field += 1").setFields("field"))
.add(client().prepareUpdate().setIndex("test").setType("type1").setId("3").setScript("ctx._source.field += a").setFields("field"))
.execute().actionGet();
assertThat(bulkResponse.hasFailures(), equalTo(true));
assertThat(bulkResponse.getItems().length, equalTo(3));
assertThat(bulkResponse.getItems()[0].getFailure().getId(), equalTo("1"));
assertThat(bulkResponse.getItems()[0].getFailure().getMessage(), containsString("failed to execute script"));
assertThat(bulkResponse.getItems()[0].getResponse(), nullValue());
assertThat(((UpdateResponse) bulkResponse.getItems()[1].getResponse()).getId(), equalTo("2"));
assertThat(((UpdateResponse) bulkResponse.getItems()[1].getResponse()).getVersion(), equalTo(2l));
assertThat(((Integer) ((UpdateResponse) bulkResponse.getItems()[1].getResponse()).getGetResult().field("field").getValue()), equalTo(2));
assertThat(bulkResponse.getItems()[1].getFailure(), nullValue());
assertThat(bulkResponse.getItems()[2].getFailure().getId(), equalTo("3"));
assertThat(bulkResponse.getItems()[2].getFailure().getMessage(), containsString("failed to execute script"));
assertThat(bulkResponse.getItems()[2].getResponse(), nullValue());
}
@Test
public void testBulkUpdate_largerVolume() throws Exception {
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().admin().indices().prepareCreate("test")
.setSettings(
ImmutableSettings.settingsBuilder()
.put("index.number_of_shards", 2)
.put("index.number_of_replicas", 1)
).execute().actionGet();
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().admin().cluster().prepareHealth().setWaitForEvents(Priority.LANGUID).setWaitForGreenStatus().execute().actionGet();
int numDocs = 2000;
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
BulkRequestBuilder builder = client().prepareBulk();
for (int i = 0; i < numDocs; i++) {
builder.add(
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().prepareUpdate()
.setIndex("test").setType("type1").setId(Integer.toString(i))
.setScript("ctx._source.counter += 1").setFields("counter")
.setUpsert(jsonBuilder().startObject().field("counter", 1).endObject())
);
}
BulkResponse response = builder.execute().actionGet();
assertThat(response.hasFailures(), equalTo(false));
assertThat(response.getItems().length, equalTo(numDocs));
for (int i = 0; i < numDocs; i++) {
assertThat(response.getItems()[i].getId(), equalTo(Integer.toString(i)));
assertThat(response.getItems()[i].getVersion(), equalTo(1l));
assertThat(response.getItems()[i].getIndex(), equalTo("test"));
assertThat(response.getItems()[i].getType(), equalTo("type1"));
assertThat(response.getItems()[i].getOpType(), equalTo("update"));
assertThat(((UpdateResponse) response.getItems()[i].getResponse()).getId(), equalTo(Integer.toString(i)));
assertThat(((UpdateResponse) response.getItems()[i].getResponse()).getVersion(), equalTo(1l));
assertThat(((Integer) ((UpdateResponse) response.getItems()[i].getResponse()).getGetResult().field("counter").getValue()), equalTo(1));
for (int j = 0; j < 5; j++) {
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
GetResponse getResponse = client().prepareGet("test", "type1", Integer.toString(i)).setFields("counter").execute().actionGet();
assertThat(getResponse.isExists(), equalTo(true));
assertThat(getResponse.getVersion(), equalTo(1l));
assertThat((Long) getResponse.getField("counter").getValue(), equalTo(1l));
}
}
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
builder = client().prepareBulk();
for (int i = 0; i < numDocs; i++) {
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
UpdateRequestBuilder updateBuilder = client().prepareUpdate()
.setIndex("test").setType("type1").setId(Integer.toString(i)).setFields("counter");
if (i % 2 == 0) {
updateBuilder.setScript("ctx._source.counter += 1");
} else {
updateBuilder.setDoc(jsonBuilder().startObject().field("counter", 2).endObject());
}
if (i % 3 == 0) {
updateBuilder.setRetryOnConflict(3);
}
builder.add(updateBuilder);
}
response = builder.execute().actionGet();
assertThat(response.hasFailures(), equalTo(false));
assertThat(response.getItems().length, equalTo(numDocs));
for (int i = 0; i < numDocs; i++) {
assertThat(response.getItems()[i].getId(), equalTo(Integer.toString(i)));
assertThat(response.getItems()[i].getVersion(), equalTo(2l));
assertThat(response.getItems()[i].getIndex(), equalTo("test"));
assertThat(response.getItems()[i].getType(), equalTo("type1"));
assertThat(response.getItems()[i].getOpType(), equalTo("update"));
assertThat(((UpdateResponse) response.getItems()[i].getResponse()).getId(), equalTo(Integer.toString(i)));
assertThat(((UpdateResponse) response.getItems()[i].getResponse()).getVersion(), equalTo(2l));
assertThat(((Integer) ((UpdateResponse) response.getItems()[i].getResponse()).getGetResult().field("counter").getValue()), equalTo(2));
}
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
builder = client().prepareBulk();
int maxDocs = numDocs / 2 + numDocs;
for (int i = (numDocs / 2); i < maxDocs; i++) {
builder.add(
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().prepareUpdate()
.setIndex("test").setType("type1").setId(Integer.toString(i)).setScript("ctx._source.counter += 1")
);
}
response = builder.execute().actionGet();
assertThat(response.hasFailures(), equalTo(true));
assertThat(response.getItems().length, equalTo(numDocs));
for (int i = 0; i < numDocs; i++) {
int id = i + (numDocs / 2);
if (i >= (numDocs / 2)) {
assertThat(response.getItems()[i].getFailure().getId(), equalTo(Integer.toString(id)));
assertThat(response.getItems()[i].getFailure().getMessage(), containsString("DocumentMissingException"));
} else {
assertThat(response.getItems()[i].getId(), equalTo(Integer.toString(id)));
assertThat(response.getItems()[i].getVersion(), equalTo(3l));
assertThat(response.getItems()[i].getIndex(), equalTo("test"));
assertThat(response.getItems()[i].getType(), equalTo("type1"));
assertThat(response.getItems()[i].getOpType(), equalTo("update"));
}
}
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
builder = client().prepareBulk();
for (int i = 0; i < numDocs; i++) {
builder.add(
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().prepareUpdate()
.setIndex("test").setType("type1").setId(Integer.toString(i)).setScript("ctx.op = \"none\"")
);
}
response = builder.execute().actionGet();
assertThat(response.hasFailures(), equalTo(false));
assertThat(response.getItems().length, equalTo(numDocs));
for (int i = 0; i < numDocs; i++) {
assertThat(response.getItems()[i].getItemId(), equalTo(i));
assertThat(response.getItems()[i].getId(), equalTo(Integer.toString(i)));
assertThat(response.getItems()[i].getIndex(), equalTo("test"));
assertThat(response.getItems()[i].getType(), equalTo("type1"));
assertThat(response.getItems()[i].getOpType(), equalTo("update"));
}
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
builder = client().prepareBulk();
for (int i = 0; i < numDocs; i++) {
builder.add(
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
client().prepareUpdate()
.setIndex("test").setType("type1").setId(Integer.toString(i)).setScript("ctx.op = \"delete\"")
);
}
response = builder.execute().actionGet();
assertThat(response.hasFailures(), equalTo(false));
assertThat(response.getItems().length, equalTo(numDocs));
for (int i = 0; i < numDocs; i++) {
assertThat(response.getItems()[i].getItemId(), equalTo(i));
assertThat(response.getItems()[i].getId(), equalTo(Integer.toString(i)));
assertThat(response.getItems()[i].getIndex(), equalTo("test"));
assertThat(response.getItems()[i].getType(), equalTo("type1"));
assertThat(response.getItems()[i].getOpType(), equalTo("update"));
for (int j = 0; j < 5; j++) {
Improve integration testing by reusing an abstracted cluster across tests The new AbstractSharedClusterTest abstracts integration testing further to reduce the overhead of writing tests that don't rely on explict control over the cluster. For instance tests that run query, facets or that test highlighting don't need to explictly start and stop nodes. Testing features like the ones just mentioned are based on the assumption that the underlying cluster can be arbitray. Based on this assumption this base class allows to: * randomize cluster and index settings if not explictly specified * transparently test transport & node clients * test features like search or highlighting on different cluster sizes * allow reuse of node insteance across tests * provide utility methods that act as upper or lower bounds that a test must pass with ie. if a test requries at least 3 nodes then it should also pass with 4 nodes * given a cluster has unmodified cluster settings (persistent and transient) the cluster should not differ to a fresh started cluster when reused across nodes. * within a test the client implementation and the clients associated node can be changed at any time and should return a valid result. This patch also prepares some redundant tests like 'RelocationTests.java' for randomized testing. Test like this are very long-running on some machines and run the same test with different parameters like 'number of writers' or 'number of relocations' which can easily be chosen with a random number and run only ones during development but multiple times during CI builds. All the improvements in this change reduce the test time by ~30%
2013-04-05 08:59:04 +02:00
GetResponse getResponse = client().prepareGet("test", "type1", Integer.toString(i)).setFields("counter").execute().actionGet();
assertThat(getResponse.isExists(), equalTo(false));
}
}
}
/*
Test for https://github.com/elasticsearch/elasticsearch/issues/3444
*/
@Test
public void testBulkUpdateDocAsUpsertWithParent() throws Exception {
client().admin().indices().prepareCreate("test")
.addMapping("parent", "{\"parent\":{}}")
.addMapping("child", "{\"child\": {\"_parent\": {\"type\": \"parent\"}}}")
.execute().actionGet();
client().admin().cluster().prepareHealth().setWaitForEvents(Priority.LANGUID).setWaitForGreenStatus().execute().actionGet();
BulkRequestBuilder builder = client().prepareBulk();
byte[] addParent = new BytesArray("{\"index\" : { \"_index\" : \"test\", \"_type\" : \"parent\", \"_id\" : \"parent1\"}}\n" +
"{\"field1\" : \"value1\"}\n").array();
byte[] addChild = new BytesArray("{ \"update\" : { \"_index\" : \"test\", \"_type\" : \"child\", \"_id\" : \"child1\", \"parent\" : \"parent1\"}}\n" +
"{\"doc\" : { \"field1\" : \"value1\"}, \"doc_as_upsert\" : \"true\"}\n").array();
builder.add(addParent, 0, addParent.length, false);
builder.add(addChild, 0, addChild.length, false);
BulkResponse bulkResponse = builder.get();
assertThat(bulkResponse.getItems().length, equalTo(2));
assertThat(bulkResponse.getItems()[0].isFailed(), equalTo(false));
assertThat(bulkResponse.getItems()[1].isFailed(), equalTo(false));
client().admin().indices().prepareRefresh("test").get();
//we check that the _parent field was set on the child document by using the has parent query
SearchResponse searchResponse = client().prepareSearch("test")
.setQuery(QueryBuilders.hasParentQuery("parent", QueryBuilders.matchAllQuery()))
.get();
assertNoFailures(searchResponse);
assertSearchHits(searchResponse, "child1");
}
/*
Test for https://github.com/elasticsearch/elasticsearch/issues/3444
*/
@Test
public void testBulkUpdateUpsertWithParent() throws Exception {
client().admin().indices().prepareCreate("test")
.addMapping("parent", "{\"parent\":{}}")
.addMapping("child", "{\"child\": {\"_parent\": {\"type\": \"parent\"}}}")
.execute().actionGet();
client().admin().cluster().prepareHealth().setWaitForEvents(Priority.LANGUID).setWaitForGreenStatus().execute().actionGet();
BulkRequestBuilder builder = client().prepareBulk();
byte[] addParent = new BytesArray("{\"index\" : { \"_index\" : \"test\", \"_type\" : \"parent\", \"_id\" : \"parent1\"}}\n" +
"{\"field1\" : \"value1\"}\n").array();
byte[] addChild = new BytesArray("{\"update\" : { \"_id\" : \"child1\", \"_type\" : \"child\", \"_index\" : \"test\", \"parent\" : \"parent1\"} }\n" +
"{ \"script\" : \"ctx._source.field2 = 'value2'\", \"upsert\" : {\"field1\" : \"value1\"}}\n").array();
builder.add(addParent, 0, addParent.length, false);
builder.add(addChild, 0, addChild.length, false);
BulkResponse bulkResponse = builder.get();
assertThat(bulkResponse.getItems().length, equalTo(2));
assertThat(bulkResponse.getItems()[0].isFailed(), equalTo(false));
assertThat(bulkResponse.getItems()[1].isFailed(), equalTo(false));
client().admin().indices().prepareRefresh("test").get();
SearchResponse searchResponse = client().prepareSearch("test")
.setQuery(QueryBuilders.hasParentQuery("parent", QueryBuilders.matchAllQuery()))
.get();
assertNoFailures(searchResponse);
assertSearchHits(searchResponse, "child1");
}
@Test
public void testFailingVersionedUpdatedOnBulk() throws Exception {
createIndex("test");
index("test","type","1","field","1");
final BulkResponse[] responses = new BulkResponse[30];
final CyclicBarrier cyclicBarrier = new CyclicBarrier(responses.length);
Thread[] threads = new Thread[responses.length];
for (int i=0;i<responses.length;i++) {
final int threadID = i;
threads[threadID] = new Thread(new Runnable() {
@Override
public void run() {
try {
cyclicBarrier.await();
} catch (Exception e) {
return;
}
BulkRequestBuilder requestBuilder = client().prepareBulk();
requestBuilder.add(client().prepareUpdate("test", "type", "1").setVersion(1).setDoc("field", threadID));
responses[threadID]=requestBuilder.get();
}
});
threads[threadID].start();
}
for (int i=0;i < threads.length; i++) {
threads[i].join();
}
int successes = 0;
for (BulkResponse response : responses) {
if (!response.hasFailures()) successes ++;
}
assertThat(successes, equalTo(1));
}
}