javanna d7e585ca4f REST: Unify query_string parameters parsing ... There currently are small differences between search api and count, exists, validate query, explain api when it comes to reading query_string parameters. `analyze_wildcard`, `lowercase_expanded_terms` and `lenient` are only read by the search api and ignored by all other mentioned apis. Unified code to fix this and make sure it doesn't happen again. Also shared some code when it comes to printing out the query as part of SearchSourceBuilder conversion to ToXContent. Extended REST spec to include all the supported params (some that were already supported weren't listed), and added REST tests (also some basic tests for count and search_exists which weren't tested at all). Closes #11057		2015-05-11 11:32:59 +02:00
..
10_source_filtering.yaml	[TEST] remove old tests from yaml test suite	2014-01-07 16:19:06 +01:00
20_default_values.yaml	[TEST] Replaced RestTestSuiteRunner with parametrized test that uses RandomizedRunner directly	2014-04-07 17:08:05 +02:00
30_template_query_execution.yaml	Add simple escape method for special characters to template query	2014-03-20 18:48:14 +01:00
40_search_request_template.yaml	[API] renaming search-template to search_template.	2014-03-20 21:58:08 +01:00
50_search_count.yaml	Search: Remove the `count` search type.	2015-03-31 11:31:49 +02:00
60_query_string.yaml	REST: Unify query_string parameters parsing	2015-05-11 11:32:59 +02:00
issue4895.yaml	Throw exception if an additional field was placed inside the "query" body	2014-04-25 08:57:06 +02:00
issue9606.yaml	Remove (dfs_)query_and_fetch from the REST API	2015-04-28 15:27:59 -07:00
test_sig_terms.yaml	significant terms: fix json response	2014-06-18 18:51:34 +02:00