1. 修改数据
Elasticsearch几乎实时提供数据操作和搜索功能。 默认情况下,从索引/更新/删除数据到搜索结果中显示的时间,您可能会有一秒钟的延迟(刷新间隔)。 这是与SQL等其他平台的重要区别。
索引/替换文档
先查看
GET /customer/_doc/1?pretty
结果如下:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 1,
"found" : true,
"_source" : {
"name" : "John Doe"
}
}
再次执行如下代码:
PUT /customer/_doc/1?pretty
{
"name": "John Doe"
}
结果:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 2, -- 版本为2
"result" : "updated", -- 这里是更新,如果是第一次的话,这里是created
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 1, -- 序列化增加1
"_primary_term" : 1
}
对比第一次新建的结果:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 1,
"result" : "created", -- 这里是创建
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 0,
"_primary_term" : 1
}
如果document的id相同,则回来的数据会替换之前的数据。
执行如下代码:
PUT /customer/_doc/2?pretty
{
"name": "Jane Doe"
}
注意:这里会创建索引ID为2的新document。
结果如下:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "2",
"_version" : 1,
"result" : "created", -- 这里表示新建
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 0,
"_primary_term" : 1
}
索引时,ID部分是可选的。 如果未指定,Elasticsearch将生成随机ID,然后使用它来索引文档。 Elasticsearch生成的实际ID(或前面示例中显式指定的内容)将作为索引API调用的一部分返回。
以下示例显示如何在没有显式ID的情况下索引文档:
注意:这里是POST请求
POST /customer/_doc?pretty
{
"name": "Jane snow post"
}
结果如下:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "HH8_UGgB4DiB3AKG7sYS", -- 随机的id
"_version" : 1,
"result" : "created",
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 2,
"_primary_term" : 1
}
查询刚才创建的文档:
GET /customer/_doc/HH8_UGgB4DiB3AKG7sYS?pretty
结果如下:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "HH8_UGgB4DiB3AKG7sYS",
"_version" : 1,
"found" : true,
"_source" : {
"name" : "Jane snow post"
}
}
2. 更新文档document
除了能够索引和替换文档,我们还可以更新文档。 请注意,Elasticsearch实际上并没有在内部进行就地更新。 每当我们进行更新时,Elasticsearch都会删除旧文档,然后一次性对应用了更新的新文档编制索引。
更新示例:
POST /customer/_doc/1/_update?pretty
{
"doc": { "name": "Jane Doe" }
}
响应:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 3,
"result" : "updated",
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 3,
"_primary_term" : 1
}
查询:
GET /customer/_doc/1?pretty
响应:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 3,
"found" : true,
"_source" : {
"name" : "Jane Doe"
}
}
更新并添加新内容:
POST /customer/_doc/1/_update?pretty
{
"doc": { "name": "Jane Doe", "age": 20 }
}
查询结果:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 4,
"found" : true,
"_source" : {
"name" : "Jane Doe",
"age" : 20
}
}
通过脚本更新:
POST /customer/_doc/1/_update?pretty
{
"script" : "ctx._source.age += 5"
}
再次查询结果如下:
{
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 5,
"found" : true,
"_source" : {
"name" : "Jane Doe",
"age" : 25
}
}
在上面的示例中,ctx._source指的是即将更新的当前源文档。
3. 删除文档
DELETE /customer/_doc/2?pretty
4. 批处理
除了能够索引,更新和删除单个文档之外,Elasticsearch还提供了使用_bulk API批量执行上述任何操作的功能。 此功能非常重要,因为它提供了一种非常有效的机制,可以尽可能快地执行多个操作,并尽可能少地进行网络往返。
下面示例 创建两个索引:
curl -X POST "localhost:9200/customer/_doc/_bulk?pretty" -H 'Content-Type: application/json' -d'
{"index":{"_id":"1"}}
{"name": "John Doe" }
{"index":{"_id":"2"}}
{"name": "Jane Doe" }'
结果如下:
{
"took" : 1810,
"errors" : false,
"items" : [
{
"index" : {
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 6,
"result" : "updated",
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 6,
"_primary_term" : 1,
"status" : 200
}
},
{
"index" : {
"_index" : "customer",
"_type" : "_doc",
"_id" : "2",
"_version" : 2,
"result" : "updated",
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 1,
"_primary_term" : 1,
"status" : 200
}
}
]
}
下面的示例更新第一个文档(ID为1),然后在一个批量操作中删除第二个文档(ID为2):
curl -X POST "localhost:9200/customer/_doc/_bulk?pretty" -H 'Content-Type: application/json' -d'
{"update":{"_id":"1"}}
{"doc": { "name": "John Doe becomes Jane Doe" } }
{"delete":{"_id":"2"}}
'
结果:
{
"took" : 1867,
"errors" : false,
"items" : [
{
"update" : {
"_index" : "customer",
"_type" : "_doc",
"_id" : "1",
"_version" : 7,
"result" : "updated",
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 7,
"_primary_term" : 1,
"status" : 200
}
},
{
"delete" : {
"_index" : "customer",
"_type" : "_doc",
"_id" : "2",
"_version" : 3,
"result" : "deleted",
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"_seq_no" : 2,
"_primary_term" : 1,
"status" : 200
}
}
]
}
Bulk API不会因其中一个操作失败而失败。 如果单个操作因任何原因失败,它将继续处理其后的其余操作。 批量API返回时,它将为每个操作提供一个状态(按照发送的顺序),以便您可以检查特定操作是否失败。