anchor.diff:  // CONSOLE
   // TEST[continued]
   
  -The `from` parameter (0-based) specifies which document index to start from and the `size` parameter specifies how many documents to return starting at the from parameter. This feature is useful when implementing paging of search results. Note that if `from` is not specified, it defaults to 0.
  -
  -This example does a `match_all` and sorts the results by account balance in descending order and returns the top 10 (default size) documents.
  -
  -[source,js]
  ---------------------------------------------------
  -GET /bank/_search
  -{
  -  "query": { "match_all": {} },
  -  "sort": { "balance": { "order": "desc" } }
  -}
  ---------------------------------------------------
  -// CONSOLE
  -// TEST[continued]
  -
  -Now that we have seen a few of the basic search parameters, let's dig in some more into the Query DSL. Let's first take a look at the returned document fields. By default, the full JSON document is returned as part of all searches. This is referred to as the source (`_source` field in the search hits). If we don't want the entire source document returned, we have the ability to request only a few fields from within source to be returned.
  -
  -This example shows how to return two fields, `account_number` and `balance` (inside of `_source`), from the search:
  -
  -[source,js]
  ---------------------------------------------------
  -GET /bank/_search
  -{
  -  "query": { "match_all": {} },
  -  "_source": ["account_number", "balance"]
  -}
  ---------------------------------------------------
  -// CONSOLE
  -// TEST[continued]
  -
  -Note that the above example simply reduces the `_source` field. It will still only return one field named `_source` but within it, only the fields `account_number` and `balance` are included.
  -
  -If you come from a SQL background, the above is somewhat similar in concept to the `SQL SELECT FROM` field list.
  -
  -Now let's move on to the query part. Previously, we've seen how the `match_all` query is used to match all documents. Let's now introduce a new query called the {ref}/query-dsl-match-query.html[`match` query], which can be thought of as a basic fielded search query (i.e. a search done against a specific field or set of fields).
  -
  -This example returns the account numbered 20:
  -
  -[source,js]
  ---------------------------------------------------
  -GET /bank/_search
  -{
  -  "query": { "match": { "account_number": 20 } }
  -}
  ---------------------------------------------------
  -// CONSOLE
  -// TEST[continued]
  -
  -This example returns all accounts containing the term "mill" in the address:
  -
  -[source,js]
  ---------------------------------------------------
  -GET /bank/_search
  -{
  -  "query": { "match": { "address": "mill" } }
  -}
  ---------------------------------------------------
  -// CONSOLE
  -// TEST[continued]
  -
  -This example returns all accounts containing the term "mill" or "lane" in the address:
  +Now that you've seen how to submit a basic search request, you can start to
  +construct queries that are a bit more interesting than `match_all`.
  +
  +To search for specific _terms_ within a field, you can use a `match` query. 
  +For example, the following request searches the `address` field to find 
  +customers whose addresses contain `mill` or `lane`:
   
   [source,js]
   --------------------------------------------------
  
positive.code: [[getting-started-install]]
  == Get {es} up and running
  
  To take {es} for a test drive, you can create a one-click cloud deployment
  on the https://www.elastic.co/cloud/elasticsearch-service/signup[Elasticsearch Service],
  or <<run-elasticsearch-local, set up a multi-node {es} cluster>> on your own
  Linux, macOS, or Windows machine.
  
  
  [float]
  [[run-elasticsearch-local]]
  === Run {es} locally on Linux, macOS, or Windows
  
  When you create a cluster on the Elasticsearch Service, you automatically
  get a three-node cluster. By installing from the tar or zip archive, you can
  start multiple instances of {es} locally to see how a multi-node cluster behaves.
  
  To run a three-node {es} cluster locally:
  
  
negative.code: [[getting-started-search]]
  == Start searching
  
  Once you have ingested some data into an {es} index, you can search it
  by sending requests to the `_search` endpoint. To access the full suite of
  search capabilities, you use the {es} Query DSL to specify the
  search criteria in the request body. You specify the name of the index you 
  want to search in the request URI.
  
  For example, the following request retrieves all of the documents in the `bank`
  index sorted by account number:
  
  [source,js]
  --------------------------------------------------
  GET /bank/_search
  {
    "query": { "match_all": {} },
    "sort": [
      { "account_number": "asc" }
    ]
  }
  --------------------------------------------------
  // CONSOLE
  // TEST[continued]
  
  By default, the `hits` section of the response includes the first 10 documents
  that match the search criteria:
  
  [source,js]
  --------------------------------------------------
  