20 Commits

Author	SHA1	Message	Date
Simon Willnauer	15d58d91f1	[REST] Render REST errors in a structural way ... This commit adds support for structural errors / failures / exceptions on the elasticsearch REST layer. Exceptions are rendering with at least a `type` and a `reason` corresponding to the exception name and the message. Some expcetions like the ones associated with an index or a shard will have additional information about the index the exception was triggered on or the shard respectivly. Each rendered response will also contain a list of root causes which is a list of distinct shard level errors returned for the request. Root causes are the lowest level elasticsearch exception found per shard response and are intended to be displayed to the user to indicate the soruce of the exception. Shard level response are by-default grouped by their type and reason to reduce the amount of duplicates retunred. Yet, the same exception retunred from different indices will not be grouped. Closes #3303	2015-04-24 09:36:10 +02:00
Clinton Gormley	1ee42e93d0	Fix REST test delete/42_missing_parent to catch a RoutingMissingException ... Related to #10136	2015-03-25 06:48:05 +02:00
Clinton Gormley	25369f0727	Remove async replication from the docs and REST spec ... Relates to #10114	2015-03-19 15:34:12 +01:00
Martijn van Groningen	ca4f27f40e	Core: Added _shards header to all write responses. ... The header indicates to how many shard copies (primary and replicas shards) a write was supposed to go to, to how many shard copies to write succeeded and potentially captures shard failures if writing into a replica shard fails. For async writes it also includes the number of shards a write is still pending. Closes #7994	2015-01-08 18:10:08 +01:00
Adrien Grand	9ea25df649	Switch to murmurhash3 to route documents to shards. ... We currently use the djb2 hash function in order to compute the shard a document should go to. Unfortunately this hash function is not very sophisticated and you can sometimes hit adversarial cases, such as numeric ids on 33 shards. Murmur3 generates hashes with a better distribution, which should avoid the adversarial cases. Here are some examples of how 100000 incremental ids are distributed to shards using either djb2 or murmur3. 5 shards: Murmur3: [19933, 19964, 19940, 20030, 20133] DJB: [20000, 20000, 20000, 20000, 20000] 3 shards: Murmur3: [33185, 33347, 33468] DJB: [30100, 30000, 39900] 33 shards: Murmur3: [2999, 3096, 2930, 2986, 3070, 3093, 3023, 3052, 3112, 2940, 3036, 2985, 3031, 3048, 3127, 2961, 2901, 3105, 3041, 3130, 3013, 3035, 3031, 3019, 3008, 3022, 3111, 3086, 3016, 2996, 3075, 2945, 2977] DJB: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 900, 900, 900, 900, 1000, 1000, 10000, 10000, 10000, 10000, 9100, 9100, 9100, 9100, 9000, 9000, 0, 0, 0, 0, 0, 0] Even if djb2 looks ideal in some cases (5 shards), the fact that the distribution of its hashes has some patterns can raise issues with some shard counts (eg. 3, or even worse 33). Some tests have been modified because they relied on implementation details of the routing hash function. Close #7954	2014-11-04 16:32:42 +01:00
javanna	f283a9f3a5	[TEST] specified number_of_shards 5 to make sure the two docs end up in different shards that can be refreshed separately	2014-04-07 19:01:19 +02:00
javanna	1ec4f8f04b	[TEST] Replaced RestTestSuiteRunner with parametrized test that uses RandomizedRunner directly ... ElasticsearchRestTests extends now ElasticsearchIntegrationTest and makes use of our ordinary test infrastructure, in particular all randomized aspects now come for free instead of having to maintain a separate (custom) tests runner We previously parsed only the tests that needed to be run given the version of the cluster the tests are running against. This doesn't happen anymore as it didn't buy much and it would be harder to support as the tests get now parsed before the test cluster gets started. Thus all the tests are now parsed regardless of their skip sections, afterwards the ones that don't need to be run will be skipped through assume directives. Fixed REST tests that rely on a specific number of shards as this change introduces also random number of shards and replicas (through randomIndexTemplate) Closes #5654	2014-04-07 17:08:05 +02:00
Boaz Leskes	b7a95d11a7	Introduced VersionType.FORCE & VersionType.EXTERNAL_GTE ... Also added "external_gt" as an alias name for VersionType.EXTERNAL , accessible for the rest layer. Closes #4213 , Closes #2946	2014-03-10 21:07:17 +01:00
Luca Cavanna	63eccce8f9	[TEST] moved routing REST tests to 0 replicas ... REST tests get run against either 1 node or multiple nodes. Wait for yellow with replicas>0 is not enough when running against multiple nodes as replicas shard might get initialized during testing, which can cause timing issues.	2014-02-10 12:32:34 +01:00
Luca Cavanna	e02635e9c2	[TEST] Fixed delete/50_refresh REST test to work against multiple nodes ... delete/50_refresh tests per shard refresh using refresh:true in delete api. We might run into troubles though if we have a replica that gets initialized after a doc was indexed and deleted, without a refresh, as that doc won't be found when searching against that specific replica shard (as a refresh happens automatically before a replica gets exposed as started).	2014-02-10 10:58:13 +01:00
Lee Hinman	d23f640cd1	Remove hard-coded "ok": true from REST responses	2014-01-07 09:27:07 -07:00
Honza Král	623e4a0fc8	[TEST] remove old tests from yaml test suite	2014-01-07 16:19:06 +01:00
Karel Minarik	397235e2f2	Changed the ignore_missing client parameter to ignore: 404 ... This should make easier any potential expansion such as: client.update('index', 'type', 41, {...}, ignore: 409 Also restructured and renamed the test suite a bit as part of the commit. --- This reverts commit 0b142cc8812d8d090e48ea0ad89c007767870b91, "Removed client-specific `ignore_missing` parameter".	2013-09-09 23:36:45 +02:00
Karel Minarik	081b3e3982	Removed client-specific ignore_missing parameter ... This parameter can introduce confusion, since people might think this is something working on Elasticsearch level, eg. passing it to `curl`	2013-09-09 23:36:43 +02:00
Honza Kral	82de8c35e7	Delete ignores parent param	2013-07-23 20:10:48 +02:00
Clinton Gormley	915a6986b9	Added a test with wrong parent to delete	2013-07-01 16:00:42 +02:00
Clinton Gormley	df94f08dab	Renamed "ok" and "not_ok" to "is_true" and "is_false" ... and tidied up the layout to make it easier to read	2013-07-01 15:58:23 +02:00
Clinton Gormley	8cb6c6ea00	Wait-for-yellow IS required for routing, otherwise can get ... shard-not-available instead of missing	2013-06-30 20:02:32 +02:00
Clinton Gormley	17cdccb50f	wait-for-yellow is not required for the routing tests	2013-06-28 19:42:37 +02:00
Clinton Gormley	262b047224	Added tests for delete	2013-06-28 17:22:32 +02:00