Added snippets for 054_Query_DSL

Author: clintongormley

054_Query_DSL/55_Request_body_search.asciidoc

@@ -20,6 +20,7 @@ which returns all documents in all indices.
 GET /_search
 {} <1>
 --------------------------------------------------
+// SENSE: 054_Query_DSL/60_Empty_query.json
 <1> This is an empty request body.
 
 Just as with query-string search, you can search on one, many or `_all`

054_Query_DSL/60_Query_DSL.asciidoc

@@ -28,7 +28,7 @@ GET /_search
     }
 }
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/60_Empty_query.json
 
 ==== Structure of a query clause
 
@@ -87,7 +87,7 @@ GET /_search
     }
 }
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/60_Match_query.json
 
 ==== Combining multiple clauses
 
@@ -106,11 +106,12 @@ other to create complex queries. Clauses can be:
 {
     "bool": {
         "must":     { "match": { "tweet": "elasticsearch" }},
-        "must_not": { "match": { "name":  "john" }},
+        "must_not": { "match": { "name":  "mary" }},
         "should":   { "match": { "tweet": "full text" }}
     }
 }
 --------------------------------------------------
+// SENSE: 054_Query_DSL/60_Bool_query.json
 
 
 It is important to note that a compound clause can combine *any* other

054_Query_DSL/70_Important_clauses.asciidoc

@@ -17,7 +17,7 @@ booleans, or `not_analyzed` exact value string fields:
 { "term": { "tag":    "full_text"  }}
 { "term": { "public": true         }}
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/70_Term_filter.json
 
 ==== `terms` filter
 
@@ -29,7 +29,7 @@ the specified values, then the document matches:
 --------------------------------------------------
 { "terms": { "tag": [ "search", "full_text", "nosql" ] }}
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/70_Terms_filter.json
 
 ==== `range` filter
 
@@ -47,7 +47,7 @@ the specified range:
     }
 }
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/70_Range_filter.json
 
 The operators that it accepts are:
 
@@ -72,7 +72,7 @@ any values (`missing`). It is similar in nature to `IS_NULL` in SQL:
     }
 }
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/70_Exists_filter.json
 
 These filters are frequently used to apply a condition only if a field is
 present, and to apply a different condition if it is missing.
@@ -103,6 +103,7 @@ of filter clauses:
     }
 }
 --------------------------------------------------
+// SENSE: 054_Query_DSL/70_Bool_filter.json
 
 
 ==== `match_all` query
@@ -114,6 +115,7 @@ query which is used if no query has been specified.
 --------------------------------------------------
 { "match_all": {}}
 --------------------------------------------------
+// SENSE: 054_Query_DSL/70_Match_all_query.json
 
 
 This query is frequently used in combination with a filter, for instance to
@@ -131,8 +133,9 @@ the search:
 
 [source,js]
 --------------------------------------------------
-{ "match": { "tweet": "Cool, bonsai cool" }}
+{ "match": { "tweet": "About Search" }}
 --------------------------------------------------
+// SENSE: 054_Query_DSL/70_Match_query.json
 
 If you use it on a field containing an exact value, such as a date, a number,
 a boolean or a `not_analyzed` string field, then it will search for that
@@ -145,6 +148,7 @@ exact value:
 { "match": { "tag":    "full_text"  }}
 { "match": { "public": true         }}
 --------------------------------------------------
+// SENSE: 054_Query_DSL/70_Match_query.json
 
 TIP: For exact value searches, you probably want to use a filter instead of a
 query, as a filter will be cached.
@@ -169,7 +173,7 @@ fields:
     }
 }
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/70_Multi_match_query.json
 
 ==== `bool` query
 
@@ -200,14 +204,14 @@ match *both* conditions will rank even higher:
     "bool": {
         "must":     { "match": { "title": "how to make millions" }},
         "must_not": { "match": { "tag":   "spam" }},
-        "should: [
+        "should": [
             { "match": { "tag": "starred" }},
-            { "match": { "date": { "gte": "2014-01-01" }}
+            { "range": { "date": { "gte": "2014-01-01" }}}
         ]
     }
 }
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/70_Bool_query.json
 
 If there are no `must` clauses, then at least one `should` clause has to
 match, but if there is at least one `must` clause, then no `should`

054_Query_DSL/75_Queries_with_filters.asciidoc

@@ -65,6 +65,7 @@ GET /_search
     }
 }
 --------------------------------------------------
+// SENSE: 054_Query_DSL/75_Filtered_query.json
 
 
 ==== Just a filter
@@ -84,6 +85,7 @@ GET /_search
     }
 }
 --------------------------------------------------
+// SENSE: 054_Query_DSL/75_Filtered_query.json
 
 
 If a query is not specified then it defaults to using the `match_all` query, so
@@ -130,11 +132,12 @@ GET /_search
     }
 }
 --------------------------------------------------
+// SENSE: 054_Query_DSL/75_Filtered_query.json
 <1> Note the `query` filter, which is allowing us to use the `match` *query*
     inside a `bool` *filter*.
 
 
-You seldom need to use a query as a filter, but we have included it for
+NOTE: You seldom need to use a query as a filter, but we have included it for
 completeness' sake.  The only time you may need it is when you need to use
 full text matching while in filter context.
 

054_Query_DSL/80_Validating_queries.asciidoc

@@ -15,6 +15,7 @@ GET /gb/tweet/_validate/query
    }
 }
 --------------------------------------------------
+// SENSE: 054_Query_DSL/80_Validate_query.json
 
 
 The response to the above `validate` request tells us that the query is
@@ -49,6 +50,7 @@ GET /gb/tweet/_validate/query?explain <1>
    }
 }
 --------------------------------------------------
+// SENSE: 054_Query_DSL/80_Validate_query.json
 <1> The `explain` flag provides more information about why a query is
     invalid.
 
@@ -87,7 +89,7 @@ GET /_validate/query?explain
    }
 }
 --------------------------------------------------
-
+// SENSE: 054_Query_DSL/80_Understanding_queries.json
 
 An `explanation` is returned for each index that we query, because each
 index can have different mapping and analyzers:

snippets/054_Query_DSL/60_Bool_query.json

@@ -0,0 +1,26 @@
+# First load the test data
+# https://gist.github.com/clintongormley/8579281
+
+# Bool query
+GET /_search
+{
+  "query": {
+    "bool": {
+      "must": {
+        "match": {
+          "tweet": "elasticsearch"
+        }
+      },
+      "must_not": {
+        "match": {
+          "name": "mary"
+        }
+      },
+      "should": {
+        "match": {
+          "tweet": "full text"
+        }
+      }
+    }
+  }
+}

snippets/054_Query_DSL/60_Empty_query.json

@@ -0,0 +1,14 @@
+# First load the test data
+# https://gist.github.com/clintongormley/8579281
+
+# Empty query
+GET /_search
+{}
+
+# Match all query
+GET /_search
+{
+    "query": {
+        "match_all": {}
+    }
+}

snippets/054_Query_DSL/60_Match_query.json

@@ -0,0 +1,9 @@
+# Match query
+GET /_search
+{
+    "query": {
+        "match": {
+            "tweet": "elasticsearch"
+        }
+    }
+}

snippets/054_Query_DSL/70_Bool_filter.json

@@ -0,0 +1,72 @@
+# Delete the `test` index
+DELETE /test
+
+# Insert some examples
+PUT /test/test/1
+{
+  "folder": "inbox",
+  "tag": [
+    "work"
+  ],
+  "starred": true,
+  "unread": false
+}
+
+PUT /test/test/2
+{
+  "folder": "inbox",
+  "tag": [
+    "spam"
+  ],
+  "starred": true,
+  "unread": false
+}
+
+PUT /test/test/3
+{
+  "folder": "inbox",
+  "tag": [
+    "other"
+  ],
+  "starred": false,
+  "unread": true
+}
+
+
+
+# Where `folder` is "inbox"
+# and `tag` is not spam
+# and either `starred` or `unread` is true
+GET /test/test/_search
+{
+  "query": {
+    "filtered": {
+      "filter": {
+        "bool": {
+          "must": {
+            "term": {
+              "folder": "inbox"
+            }
+          },
+          "must_not": {
+            "term": {
+              "tag": "spam"
+            }
+          },
+          "should": [
+            {
+              "term": {
+                "starred": true
+              }
+            },
+            {
+              "term": {
+                "unread": true
+              }
+            }
+          ]
+        }
+      }
+    }
+  }
+}

snippets/054_Query_DSL/70_Bool_query.json

@@ -0,0 +1,68 @@
+# Delete the `test` index
+DELETE /test
+
+# Insert some example docs
+PUT /test/test/1
+{
+  "title": "How to make millions!",
+  "tag": [
+    "opportunity"
+  ],
+  "date": "2014-01-09"
+}
+
+PUT /test/test/2
+{
+  "title": "How to make millions!",
+  "tag": [
+    "spam"
+  ],
+  "date": "2014-01-09"
+}
+
+PUT /test/test/3
+{
+  "title": "How to make millions!",
+  "tag": [
+    "opportunity",
+    "starred"
+  ],
+  "date": "2013-01-09"
+}
+
+
+# Match "how to make millions" in the `title`
+# and `tag` must not include "spam"
+# and either `tag` should include "starred"
+# or `date` must be >= "2014-01-01"
+GET /test/test/_search
+{
+  "query": {
+    "bool": {
+      "must": {
+        "match": {
+          "title": "how to make millions"
+        }
+      },
+      "must_not": {
+        "match": {
+          "tag": "spam"
+        }
+      },
+      "should": [
+        {
+          "match": {
+            "tag": "starred"
+          }
+        },
+        {
+          "range": {
+            "date": {
+              "gte": "2014-01-01"
+            }
+          }
+        }
+      ]
+    }
+  }
+}