uri-request.asciidoc 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899
  1. [[search-uri-request]]
  2. == URI Search
  3. A search request can be executed purely using a URI by providing request
  4. parameters. Not all search options are exposed when executing a search
  5. using this mode, but it can be handy for quick "curl tests". Here is an
  6. example:
  7. [source,js]
  8. --------------------------------------------------
  9. $ curl -XGET 'http://localhost:9200/twitter/tweet/_search?q=user:kimchy'
  10. --------------------------------------------------
  11. And here is a sample response:
  12. [source,js]
  13. --------------------------------------------------
  14. {
  15. "_shards":{
  16. "total" : 5,
  17. "successful" : 5,
  18. "failed" : 0
  19. },
  20. "hits":{
  21. "total" : 1,
  22. "hits" : [
  23. {
  24. "_index" : "twitter",
  25. "_type" : "tweet",
  26. "_id" : "1",
  27. "_source" : {
  28. "user" : "kimchy",
  29. "postDate" : "2009-11-15T14:12:12",
  30. "message" : "trying out Elastic Search"
  31. }
  32. }
  33. ]
  34. }
  35. }
  36. --------------------------------------------------
  37. [float]
  38. === Parameters
  39. The parameters allowed in the URI are:
  40. [cols="<,<",options="header",]
  41. |=======================================================================
  42. |Name |Description
  43. |`q` |The query string (maps to the `query_string` query, see
  44. <<query-dsl-query-string-query,_Query String
  45. Query_>> for more details).
  46. |`df` |The default field to use when no field prefix is defined within the
  47. query.
  48. |`analyzer` |The analyzer name to be used when analyzing the query string.
  49. |`default_operator` |The default operator to be used, can be `AND` or
  50. `OR`. Defaults to `OR`.
  51. |`explain` |For each hit, contain an explanation of how scoring of the
  52. hits was computed.
  53. |`fields` |The selective fields of the document to return for each hit
  54. (either retrieved from the index if stored, or from the `_source` if
  55. not), comma delimited. Defaults to the internal `_source` field. Not
  56. specifying any value will cause no fields to return.
  57. |`sort` |Sorting to perform. Can either be in the form of `fieldName`, or
  58. `fieldName:asc`/`fieldName:desc`. The fieldName can either be an actual
  59. field within the document, or the special `_score` name to indicate
  60. sorting based on scores. There can be several `sort` parameters (order
  61. is important).
  62. |`track_scores` |When sorting, set to `true` in order to still track
  63. scores and return them as part of each hit.
  64. |`timeout` |A search timeout, bounding the search request to be executed
  65. within the specified time value and bail with the hits accumulated up to
  66. that point when expired. Defaults to no timeout.
  67. |`from` |The starting from index of the hits to return. Defaults to `0`.
  68. |`size` |The number of hits to return. Defaults to `10`.
  69. |`search_type` |The type of the search operation to perform. Can be
  70. `dfs_query_then_fetch`, `dfs_query_and_fetch`, `query_then_fetch`,
  71. `query_and_fetch`, `count`, `scan`. Defaults to `query_then_fetch`. See
  72. <<search-request-search-type,_Search Type_>> for
  73. more details on the different types of search that can be performed.
  74. |`lowercase_expanded_terms` |Should terms be automatically lowercased or
  75. not. Defaults to `true`.
  76. |`analyze_wildcard` |Should wildcard and prefix queries be analyzed or
  77. not. Defaults to `false`.
  78. |=======================================================================