File tree Expand file tree Collapse file tree 1 file changed +1
-5
lines changed Expand file tree Collapse file tree 1 file changed +1
-5
lines changed Original file line number Diff line number Diff line change @@ -26,7 +26,6 @@ in several formats. The most common one is the same as returned by
26
26
27
27
{
28
28
' _index' : ' index-name' ,
29
- ' _type' : ' document' ,
30
29
' _id' : 42 ,
31
30
' _routing' : 5 ,
32
31
' pipeline' : ' my-ingest-pipeline' ,
@@ -57,13 +56,11 @@ action (``_op_type`` defaults to ``index``):
57
56
{
58
57
' _op_type' : ' delete' ,
59
58
' _index' : ' index-name' ,
60
- ' _type' : ' document' ,
61
59
' _id' : 42 ,
62
60
}
63
61
{
64
62
' _op_type' : ' update' ,
65
63
' _index' : ' index-name' ,
66
- ' _type' : ' document' ,
67
64
' _id' : 42 ,
68
65
' doc' : {' question' : ' The life, universe and everything.' }
69
66
}
@@ -83,7 +80,6 @@ document is like ``{"word": "<myword>"}``.
83
80
for word in mywords:
84
81
yield {
85
82
" _index" : " mywords" ,
86
- " _type" : " document" ,
87
83
" doc" : {" word" : word},
88
84
}
89
85
@@ -114,7 +110,7 @@ If you don't care about the results, you can use deque from collections:
114
110
115
111
When reading raw json strings from a file, you can also pass them in
116
112
directly (without decoding to dicts first). In that case, however, you lose
117
- the ability to specify anything (index, type, even id) on a per-record
113
+ the ability to specify anything (index, op_type and even id) on a per-record
118
114
basis, all documents will just be sent to elasticsearch to be indexed
119
115
as-is.
120
116
You can’t perform that action at this time.
0 commit comments