Small elasticsearch Notes - Revision history

Admin: /* Search */

2013-12-25T21:19:07Z

‎Search

Admin: /* Put Mapping */

2013-02-18T14:58:52Z

‎Put Mapping

Admin: /* Mappings */

2013-01-29T16:30:41Z

‎Mappings

Admin at 20:47, 25 January 2013

2013-01-25T20:47:25Z

Admin at 14:56, 25 January 2013

2013-01-25T14:56:02Z

Admin: /* Example */

2013-01-24T12:10:46Z

‎Example

Admin: /* Specific Attributes */

2013-01-24T12:09:08Z

‎Specific Attributes

Admin: /* Mappings */

2013-01-24T11:37:47Z

‎Mappings

Admin at 09:55, 24 January 2013

2013-01-24T09:55:54Z

Admin: /* Create Mapping */

2013-01-24T09:46:33Z

‎Create Mapping

@@ Line 333: / Line 333: @@
 * ''retry_on_conflict'' - how many times to retry if there is a version conflict; default 0
-== [[ElasticSearch Search|Search]] ==
+== Search ==
 [http://www.elasticsearch.org/guide/reference/api/search/ official documentation]

← Older revision		Revision as of 14:58, 18 February 2013
Line 410:		Line 410:

	Mapping can be applied to multiple indices (passing CSV of index names), or to ''_all'' indices.		Mapping can be applied to multiple indices (passing CSV of index names), or to ''_all'' indices.
		+
		+	When an existing mapping already exists under the given type, the two mapping definitions, the one already defined, and the new ones are merged. In general, if a different core type is defined, it is considered as a conflict. New mapping definitions can be added to object types, and core type mapping can be upgraded to multi_field type.

	=== Get Mapping ===		=== Get Mapping ===

@@ Line 391: / Line 391: @@
 Mapping settings may be set while creating index, or separately.
 === Put Mapping ===
@@ Line 402: / Line 407: @@
 }'</pre>
-Fields are by default ''not'' stored, just indexed.
+Fields are by default ''not'' stored, just indexed (see below - common attributes).
 Mapping can be applied to multiple indices (passing CSV of index names), or to ''_all'' indices.
@@ Line 413: / Line 418: @@
 <pre>$ curl -XDELETE 'http://localhost:9200/twitter/tweet/'</pre>
 Note, most times, it make more sense to reindex the data into a fresh index compared to delete large chunks of it.
 === Common Attributes ===

@@ Line 118: / Line 118: @@
 You can create document without providing ID. Note that the call is '''POST not PUT'''! (this, of course, automatically sets <tt>op_type</tt> to <tt>create</tt>).
-<pre>curl -XPOST 'http://localhost:9200/twitter/tweet/' -d '{...}'</pre>
+<pre>$ curl -XPOST 'http://localhost:9200/twitter/tweet/' -d '{...}'</pre>
 You'll receive the generated (UUIDv4) ID in the response:
@@ Line 144: / Line 144: @@
 You can "control" this by providing the ID used for hashing manually, using ''routing'' parameter:
-<pre>curl -XPOST 'http://localhost:9200/twitter/tweet?routing=kimchy' -d '{...}'</pre>
+<pre>$ curl -XPOST 'http://localhost:9200/twitter/tweet?routing=kimchy' -d '{...}'</pre>
 The main advantage of routing is that you can use this information later on when search for documents, by providing the same ID:
-<pre>curl -XGET 'http://localhost:9200/twitter/tweet/_search?routing=kimchy' -d '{"query":{...}}'</pre>
+<pre>$ curl -XGET 'http://localhost:9200/twitter/tweet/_search?routing=kimchy' -d '{"query":{...}}'</pre>
 This will restrict the search only to shards that might store the documents for given routing.
@@ Line 169: / Line 169: @@
 You can get document from index by type and ID:
-<pre>curl -XGET 'http://localhost:9200/twitter/tweet/1'</pre>
+<pre>$ curl -XGET 'http://localhost:9200/twitter/tweet/1'</pre>
 <pre>{
      "_index" : "twitter",
@@ Line 183: / Line 183: @@
 To simply check if the document exists, use HEAD:
-<pre>curl -XHEAD 'http://localhost:9200/twitter/tweet/1'</pre>
+<pre>$ curl -XHEAD 'http://localhost:9200/twitter/tweet/1'</pre>
 === Get Options ===
@@ Line 191: / Line 191: @@
 You can also specify <tt>fields</tt> parameter to get only selected fields from the document. You may also fetch sub-objects, using <tt>obj1.obj2</tt> notation.
-<pre>curl -XGET 'http://localhost:9200/twitter/tweet/1?fields=title,content'</pre>
+<pre>$ curl -XGET 'http://localhost:9200/twitter/tweet/1?fields=title,content'</pre>
 Type of the document is optional, and passing ''_all'' as type for the GET call will return all documents from index based on ID.
@@ Line 204: / Line 204: @@
 '''From various indices'''
-<pre>curl 'localhost:9200/_mget' -d '{
+<pre>$ curl 'http://localhost:9200/_mget' -d '{
      "docs" : [
+         {
@@ Line 220: / Line 220: @@
 '''From same index, various types'''
-<pre>curl 'localhost:9200/test/_mget' -d '{
+<pre>$ curl 'http://localhost:9200/test/_mget' -d '{
      "docs" : [
+         {
@@ Line 234: / Line 234: @@
 '''Same index, same type'''
-<pre>curl 'localhost:9200/test/type/_mget' -d '{ "ids" : ["1", "2"] }'</pre>
+<pre>$ curl 'http://localhost:9200/test/type/_mget' -d '{ "ids" : ["1", "2"] }'</pre>
 You can also specify fields to fetch:
-<pre>curl 'localhost:9200/_mget' -d '{
+<pre>$ curl 'http://localhost:9200/_mget' -d '{
      "docs" : [
+         {
@@ Line 265: / Line 265: @@
 <pre># create a document
-curl -XPUT localhost:9200/test/type1/1 -d '{
+$ curl -XPUT 'http://localhost:9200/test/type1/1' -d '{
      "counter" : 1,
      "tags" : ["red"]
@@ Line 271: / Line 271: @@
 # update the counter - increment by 4
-curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
+$ curl -XPOST 'http://localhost:9200/test/type1/1/_update' -d '{
      "script" : "ctx._source.counter += count",
      "params" : {
@@ Line 279: / Line 279: @@
 # add a tag (might add a duplicate, since it's just a list!)
-curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
+$ curl -XPOST 'http://localhost:9200/test/type1/1/_update' -d '{
      "script" : "ctx._source.tags += tag",
      "params" : {
@@ Line 287: / Line 287: @@
 # add a new field
-curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
+$ curl -XPOST 'http://localhost:9200/test/type1/1/_update' -d '{
      "script" : "ctx._source.text = \"some text\""
 }'
 # remove a field
-curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
+$ curl -XPOST 'http://localhost:9200/test/type1/1/_update' -d '{
      "script" : "ctx._source.remove(\"text\")"
 }'
 # delete documents with tag 'blue', or ignore/noop
-curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
+$ curl -XPOST 'http://localhost:9200/test/type1/1/_update' -d '{
      "script" : "ctx._source.tags.contains(tag) ? ctx.op = \"delete\" : ctx.op = \"none\"",
      "params" : {
@@ Line 305: / Line 305: @@
 # "full" document may also be POST'ed, causing the final document to be a merge of original and update
-curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
+$ curl -XPOST 'http://localhost:9200/test/type1/1/_update' -d '{
      "doc" : {
          "name" : "new_name"
@@ Line 312: / Line 312: @@
 # if field does not exist, its "default" may be specified as 'upsert'
-curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
+$ curl -XPOST 'http://localhost:9200/test/type1/1/_update' -d '{
      "script" : "ctx._source.counter += count",
      "params" : {
@@ Line 354: / Line 354: @@
 You may also provide mappings settings (see below) when creating index:
-<pre>$ curl -XPOST localhost:9200/test -d '{
+<pre>$ curl -XPOST 'http://localhost:9200/test' -d '{
      "settings" : {
          "number_of_shards" : 1

@@ Line 133: / Line 133: @@
 Index is automatically created if it does not exist. Data type mapping is also automatically created/updated.
-Indices can also be [http://www.elasticsearch.org/guide/reference/api/admin-indices-create-index.html created "manually"], as well as [http://www.elasticsearch.org/guide/reference/api/admin-indices-put-mapping.html type mappings].
+Indices can also be [[#Indices_Management|created "manually"]], as well as [[#Mappings|mappings]].
 By setting <tt>action.auto_create_index</tt> to <tt>false</tt> in configuration, indices need to be created manually before use. Same goes for type mapping - <tt>index.mapper.dynamic</tt>.

@@ Line 442: / Line 442: @@
      "tweet" : {
          "properties" : {
-            "rank" : { "type" : "float", "null_value" : 1.0 },
+             "user" : { "type" : "string", "index" : "not_analyzed" },
-             "user" : {"type" : "string", "index" : "not_analyzed"},
+             "message" : { "type" : "string", "null_value" : "na" },
-             "message" : {"type" : "string", "null_value" : "na"},
+             "postDate" : { "type" : "date" },
-             "postDate" : {"type" : "date"},
+             "priority" : { "type" : "integer", "boost" : 3.0 },
-             "priority" : {"type" : "integer"},
+             "rank" : { "type" : "float", "null_value" : 1.0 }
              "rank" : {"type" : "float"}
+         }
+     }

@@ Line 434: / Line 434: @@
 === Specific Attributes ===
 '''Date'''
-* ''format'' - default ''dateOptionalTime''
+* ''format'' - default ''dateOptionalTime'' (see [http://www.elasticsearch.org/guide/reference/mapping/date-format.html full date formats list])
 '''Binary'''
 * base64 representation of binary data, always stored and not indexed at all

← Older revision		Revision as of 09:55, 24 January 2013
Line 413:		Line 413:
	<pre>$ curl -XDELETE 'http://localhost:9200/twitter/tweet/'</pre>		<pre>$ curl -XDELETE 'http://localhost:9200/twitter/tweet/'</pre>
	Note, most times, it make more sense to reindex the data into a fresh index compared to delete large chunks of it.		Note, most times, it make more sense to reindex the data into a fresh index compared to delete large chunks of it.
		+
		+	== Diagnostics ==
		+
		+	=== Status ===
		+	<pre>$ curl -XGET 'http://localhost:9200/twitter/_status'</pre>
		+	* ''recovery=true'' to see status of recovery,
		+	* ''snapshot=true'' for snapshot status.
		+	Again, CSV indices or ''_all'' (the same as omitted) can be used.
		+
		+	=== Stats ===
		+	<pre>$ curl -XGET 'http://localhost:9200/twitter/_stats'</pre>
		+	Again, CSV indices or ''_all'' (the same as omitted) can be used.

@@ Line 384: / Line 384: @@
 <pre>$ curl -XGET 'http://localhost:9200/twitter/_settings'</pre>
-== Create Mapping ==
+== Mappings ==
-[http://www.elasticsearch.org/guide/reference/mapping/index.html mapping]
+[http://www.elasticsearch.org/guide/reference/mapping/index.html official documentation]