官术网_书友最值得收藏!

Using explicit mapping creation

If we consider the index as a database in the SQL world, the mapping is similar to the table definition.

Getting ready

You need a working ElasticSearch cluster, a test index (refer to the Creating an index recipe in Chapter 4, Standard Operations), and basic knowledge of JSON.

How to do it...

For explicit mapping creation, we will perform the following steps:

  1. You can explicitly create a mapping by adding a new element in ElasticSearch.

    On bash:

    #create an index
    curl -XPUT http://127.0.0.1:9200/test
    #{"ok":true,"acknowledged":true}
    
    #put a record
    curl -XPUT http://127.0.0.1:9200/test/mytype/1 -d '{"name":"Paul", "age":35}'
    # {"ok":true,"_index":"test","_type":"mytype","_id":"1","_version":1}
    
    #get the mapping and pretty print it
    curl –XGET http://127.0.0.1:9200/test/mytype/_mapping?pretty=true
    
  2. The result mapping auto-created by ElasticSearch should be as follows:
    {
      "mytype" : {
        "properties" : {
          "age" : {
            "type" : "long"
          },
          "name" : {
            "type" : "string"
          }
        }
      }
    }

How it works...

The first command line creates the test index, decides where to put the document and the type/mapping.

The second command line inserts a document in the index. We'll see the index creation and record indexing in the next chapter.

During the document index phase, ElasticSearch controls if the mytype type exists, otherwise, it creates an empty one.

ElasticSearch reads all the default properties for the field of the mapping and starts to process them as follows:

  • If the field is already present in the mapping and the value of the field is valid, it processes the field
  • If the field is already present in the mapping, but the value of the field is of a different type, it processes the field as a new type, migrating the previous field format in a multifield
  • If the field is not present, it tries to auto-detect the type of field, it updates the mappings (or adding a new field mapping or converting the actual field in a multifield

There's more...

All the document types go in the same Lucene index, so there isn't full separation between them.

Every document has a unique identifier called UID, stored in the special uid field of the document. It's calculated by adding the type of document to the _id field.

The _id field can be provided at index time or can be assigned automatically by ElasticSearch if it's missing.

ElasticSearch transparently manages the propagation of a type mapping to all the nodes of a cluster, so that all the shards are aligned to processes of that particular type.

主站蜘蛛池模板: 长白| 灵川县| 开封市| 错那县| 长沙县| 射阳县| 周至县| 青浦区| 昂仁县| 江都市| 安福县| 外汇| 双柏县| 江西省| 宜宾县| 柳河县| 九龙县| 普洱| 景德镇市| 盐池县| 郎溪县| 宝山区| 昭平县| 昆明市| 广宗县| 双鸭山市| 邻水| 汉川市| 阳东县| 昭平县| 正阳县| 射阳县| 文水县| 深州市| 新乐市| 昌黎县| 启东市| 离岛区| 西安市| 嵊州市| 腾冲县|