Jason Tedor 24d10adaab Main response should not have status 503 when okay (#29045) ... The REST status 503 means "I can not handle the request that you sent me." However today we respond to a main request with a 503 when there are certain cluster blocks despite still responding with an actual main response. This is broken, we should respond with a 200 status. This commit removes this silliness.		2018-03-14 06:36:37 -04:00
..
benchmark	Upgrade Gradle Shadow plugin to 2.0.2	2017-12-29 10:57:11 +01:00
client-benchmark-noop-api-plugin	Cross Cluster Search: make remote clusters optional (#27182)	2017-11-21 11:41:47 +01:00
rest	[TEST] replace randomAsciiAlphanumOfLengthBetween with randomAsciiLettersOfLengthBetween	2018-02-21 16:36:04 +01:00
rest-high-level	Main response should not have status 503 when okay (#29045)	2018-03-14 06:36:37 -04:00
sniffer	Introduce elasticsearch-core jar (#28191)	2018-01-15 09:59:01 -07:00
test	Introduce elasticsearch-core jar (#28191)	2018-01-15 09:59:01 -07:00
transport	Add rank-eval module to transport client and HL client dependencies	2017-12-13 18:05:43 +01:00