2016-07-24 01:51:12 -04:00
|
|
|
// Copyright 2012-present Oliver Eilhard. All rights reserved.
|
|
|
|
// Use of this source code is governed by a MIT-license.
|
|
|
|
// See http://olivere.mit-license.org/license.txt for details.
|
|
|
|
|
|
|
|
package elastic
|
|
|
|
|
|
|
|
import (
|
|
|
|
"encoding/json"
|
|
|
|
"fmt"
|
|
|
|
"strings"
|
|
|
|
)
|
|
|
|
|
Add `access` format support for Elasticsearch notification target (#4006)
This change adds `access` format support for notifications to a
Elasticsearch server, and it refactors `namespace` format support.
In the case of `access` format, for each event in Minio, a JSON
document is inserted into Elasticsearch with its timestamp set to the
event's timestamp, and with the ID generated automatically by
elasticsearch. No events are modified or deleted in this mode.
In the case of `namespace` format, for each event in Minio, a JSON
document is keyed together by the bucket and object name is updated in
Elasticsearch. In the case of an object being created or over-written
in Minio, a new document or an existing document is inserted into the
Elasticsearch index. If an object is deleted in Minio, the
corresponding document is deleted from the Elasticsearch index.
Additionally, this change upgrades Elasticsearch support to the 5.x
series. This is a breaking change, and users of previous elasticsearch
versions should upgrade.
Also updates documentation on Elasticsearch notification target usage
and has a link to an elasticsearch upgrade guide.
This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
|
|
|
// BulkIndexRequest is a request to add a document to Elasticsearch.
|
2016-07-24 01:51:12 -04:00
|
|
|
//
|
Add `access` format support for Elasticsearch notification target (#4006)
This change adds `access` format support for notifications to a
Elasticsearch server, and it refactors `namespace` format support.
In the case of `access` format, for each event in Minio, a JSON
document is inserted into Elasticsearch with its timestamp set to the
event's timestamp, and with the ID generated automatically by
elasticsearch. No events are modified or deleted in this mode.
In the case of `namespace` format, for each event in Minio, a JSON
document is keyed together by the bucket and object name is updated in
Elasticsearch. In the case of an object being created or over-written
in Minio, a new document or an existing document is inserted into the
Elasticsearch index. If an object is deleted in Minio, the
corresponding document is deleted from the Elasticsearch index.
Additionally, this change upgrades Elasticsearch support to the 5.x
series. This is a breaking change, and users of previous elasticsearch
versions should upgrade.
Also updates documentation on Elasticsearch notification target usage
and has a link to an elasticsearch upgrade guide.
This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
|
|
|
// See https://www.elastic.co/guide/en/elasticsearch/reference/5.2/docs-bulk.html
|
2016-07-24 01:51:12 -04:00
|
|
|
// for details.
|
|
|
|
type BulkIndexRequest struct {
|
|
|
|
BulkableRequest
|
Add `access` format support for Elasticsearch notification target (#4006)
This change adds `access` format support for notifications to a
Elasticsearch server, and it refactors `namespace` format support.
In the case of `access` format, for each event in Minio, a JSON
document is inserted into Elasticsearch with its timestamp set to the
event's timestamp, and with the ID generated automatically by
elasticsearch. No events are modified or deleted in this mode.
In the case of `namespace` format, for each event in Minio, a JSON
document is keyed together by the bucket and object name is updated in
Elasticsearch. In the case of an object being created or over-written
in Minio, a new document or an existing document is inserted into the
Elasticsearch index. If an object is deleted in Minio, the
corresponding document is deleted from the Elasticsearch index.
Additionally, this change upgrades Elasticsearch support to the 5.x
series. This is a breaking change, and users of previous elasticsearch
versions should upgrade.
Also updates documentation on Elasticsearch notification target usage
and has a link to an elasticsearch upgrade guide.
This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
|
|
|
index string
|
|
|
|
typ string
|
|
|
|
id string
|
|
|
|
opType string
|
|
|
|
routing string
|
|
|
|
parent string
|
|
|
|
version int64 // default is MATCH_ANY
|
|
|
|
versionType string // default is "internal"
|
|
|
|
doc interface{}
|
|
|
|
pipeline string
|
|
|
|
retryOnConflict *int
|
|
|
|
ttl string
|
2016-07-24 01:51:12 -04:00
|
|
|
|
|
|
|
source []string
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewBulkIndexRequest returns a new BulkIndexRequest.
|
|
|
|
// The operation type is "index" by default.
|
|
|
|
func NewBulkIndexRequest() *BulkIndexRequest {
|
|
|
|
return &BulkIndexRequest{
|
|
|
|
opType: "index",
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Index specifies the Elasticsearch index to use for this index request.
|
|
|
|
// If unspecified, the index set on the BulkService will be used.
|
|
|
|
func (r *BulkIndexRequest) Index(index string) *BulkIndexRequest {
|
|
|
|
r.index = index
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// Type specifies the Elasticsearch type to use for this index request.
|
|
|
|
// If unspecified, the type set on the BulkService will be used.
|
|
|
|
func (r *BulkIndexRequest) Type(typ string) *BulkIndexRequest {
|
|
|
|
r.typ = typ
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// Id specifies the identifier of the document to index.
|
|
|
|
func (r *BulkIndexRequest) Id(id string) *BulkIndexRequest {
|
|
|
|
r.id = id
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// OpType specifies if this request should follow create-only or upsert
|
|
|
|
// behavior. This follows the OpType of the standard document index API.
|
Add `access` format support for Elasticsearch notification target (#4006)
This change adds `access` format support for notifications to a
Elasticsearch server, and it refactors `namespace` format support.
In the case of `access` format, for each event in Minio, a JSON
document is inserted into Elasticsearch with its timestamp set to the
event's timestamp, and with the ID generated automatically by
elasticsearch. No events are modified or deleted in this mode.
In the case of `namespace` format, for each event in Minio, a JSON
document is keyed together by the bucket and object name is updated in
Elasticsearch. In the case of an object being created or over-written
in Minio, a new document or an existing document is inserted into the
Elasticsearch index. If an object is deleted in Minio, the
corresponding document is deleted from the Elasticsearch index.
Additionally, this change upgrades Elasticsearch support to the 5.x
series. This is a breaking change, and users of previous elasticsearch
versions should upgrade.
Also updates documentation on Elasticsearch notification target usage
and has a link to an elasticsearch upgrade guide.
This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
|
|
|
// See https://www.elastic.co/guide/en/elasticsearch/reference/5.2/docs-index_.html#operation-type
|
2016-07-24 01:51:12 -04:00
|
|
|
// for details.
|
|
|
|
func (r *BulkIndexRequest) OpType(opType string) *BulkIndexRequest {
|
|
|
|
r.opType = opType
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// Routing specifies a routing value for the request.
|
|
|
|
func (r *BulkIndexRequest) Routing(routing string) *BulkIndexRequest {
|
|
|
|
r.routing = routing
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// Parent specifies the identifier of the parent document (if available).
|
|
|
|
func (r *BulkIndexRequest) Parent(parent string) *BulkIndexRequest {
|
|
|
|
r.parent = parent
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// Version indicates the version of the document as part of an optimistic
|
|
|
|
// concurrency model.
|
|
|
|
func (r *BulkIndexRequest) Version(version int64) *BulkIndexRequest {
|
|
|
|
r.version = version
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// VersionType specifies how versions are created. It can be e.g. internal,
|
|
|
|
// external, external_gte, or force.
|
|
|
|
//
|
Add `access` format support for Elasticsearch notification target (#4006)
This change adds `access` format support for notifications to a
Elasticsearch server, and it refactors `namespace` format support.
In the case of `access` format, for each event in Minio, a JSON
document is inserted into Elasticsearch with its timestamp set to the
event's timestamp, and with the ID generated automatically by
elasticsearch. No events are modified or deleted in this mode.
In the case of `namespace` format, for each event in Minio, a JSON
document is keyed together by the bucket and object name is updated in
Elasticsearch. In the case of an object being created or over-written
in Minio, a new document or an existing document is inserted into the
Elasticsearch index. If an object is deleted in Minio, the
corresponding document is deleted from the Elasticsearch index.
Additionally, this change upgrades Elasticsearch support to the 5.x
series. This is a breaking change, and users of previous elasticsearch
versions should upgrade.
Also updates documentation on Elasticsearch notification target usage
and has a link to an elasticsearch upgrade guide.
This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
|
|
|
// See https://www.elastic.co/guide/en/elasticsearch/reference/5.2/docs-index_.html#index-versioning
|
2016-07-24 01:51:12 -04:00
|
|
|
// for details.
|
|
|
|
func (r *BulkIndexRequest) VersionType(versionType string) *BulkIndexRequest {
|
|
|
|
r.versionType = versionType
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// Doc specifies the document to index.
|
|
|
|
func (r *BulkIndexRequest) Doc(doc interface{}) *BulkIndexRequest {
|
|
|
|
r.doc = doc
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
Add `access` format support for Elasticsearch notification target (#4006)
This change adds `access` format support for notifications to a
Elasticsearch server, and it refactors `namespace` format support.
In the case of `access` format, for each event in Minio, a JSON
document is inserted into Elasticsearch with its timestamp set to the
event's timestamp, and with the ID generated automatically by
elasticsearch. No events are modified or deleted in this mode.
In the case of `namespace` format, for each event in Minio, a JSON
document is keyed together by the bucket and object name is updated in
Elasticsearch. In the case of an object being created or over-written
in Minio, a new document or an existing document is inserted into the
Elasticsearch index. If an object is deleted in Minio, the
corresponding document is deleted from the Elasticsearch index.
Additionally, this change upgrades Elasticsearch support to the 5.x
series. This is a breaking change, and users of previous elasticsearch
versions should upgrade.
Also updates documentation on Elasticsearch notification target usage
and has a link to an elasticsearch upgrade guide.
This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
|
|
|
// RetryOnConflict specifies how often to retry in case of a version conflict.
|
|
|
|
func (r *BulkIndexRequest) RetryOnConflict(retryOnConflict int) *BulkIndexRequest {
|
|
|
|
r.retryOnConflict = &retryOnConflict
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// TTL is an expiration time for the document.
|
|
|
|
func (r *BulkIndexRequest) TTL(ttl string) *BulkIndexRequest {
|
|
|
|
r.ttl = ttl
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
|
|
|
// Pipeline to use while processing the request.
|
|
|
|
func (r *BulkIndexRequest) Pipeline(pipeline string) *BulkIndexRequest {
|
|
|
|
r.pipeline = pipeline
|
|
|
|
r.source = nil
|
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
2016-07-24 01:51:12 -04:00
|
|
|
// String returns the on-wire representation of the index request,
|
|
|
|
// concatenated as a single string.
|
|
|
|
func (r *BulkIndexRequest) String() string {
|
|
|
|
lines, err := r.Source()
|
|
|
|
if err != nil {
|
|
|
|
return fmt.Sprintf("error: %v", err)
|
|
|
|
}
|
|
|
|
return strings.Join(lines, "\n")
|
|
|
|
}
|
|
|
|
|
|
|
|
// Source returns the on-wire representation of the index request,
|
|
|
|
// split into an action-and-meta-data line and an (optional) source line.
|
Add `access` format support for Elasticsearch notification target (#4006)
This change adds `access` format support for notifications to a
Elasticsearch server, and it refactors `namespace` format support.
In the case of `access` format, for each event in Minio, a JSON
document is inserted into Elasticsearch with its timestamp set to the
event's timestamp, and with the ID generated automatically by
elasticsearch. No events are modified or deleted in this mode.
In the case of `namespace` format, for each event in Minio, a JSON
document is keyed together by the bucket and object name is updated in
Elasticsearch. In the case of an object being created or over-written
in Minio, a new document or an existing document is inserted into the
Elasticsearch index. If an object is deleted in Minio, the
corresponding document is deleted from the Elasticsearch index.
Additionally, this change upgrades Elasticsearch support to the 5.x
series. This is a breaking change, and users of previous elasticsearch
versions should upgrade.
Also updates documentation on Elasticsearch notification target usage
and has a link to an elasticsearch upgrade guide.
This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
|
|
|
// See https://www.elastic.co/guide/en/elasticsearch/reference/5.2/docs-bulk.html
|
2016-07-24 01:51:12 -04:00
|
|
|
// for details.
|
|
|
|
func (r *BulkIndexRequest) Source() ([]string, error) {
|
|
|
|
// { "index" : { "_index" : "test", "_type" : "type1", "_id" : "1" } }
|
|
|
|
// { "field1" : "value1" }
|
|
|
|
|
|
|
|
if r.source != nil {
|
|
|
|
return r.source, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
lines := make([]string, 2)
|
|
|
|
|
|
|
|
// "index" ...
|
|
|
|
command := make(map[string]interface{})
|
|
|
|
indexCommand := make(map[string]interface{})
|
|
|
|
if r.index != "" {
|
|
|
|
indexCommand["_index"] = r.index
|
|
|
|
}
|
|
|
|
if r.typ != "" {
|
|
|
|
indexCommand["_type"] = r.typ
|
|
|
|
}
|
|
|
|
if r.id != "" {
|
|
|
|
indexCommand["_id"] = r.id
|
|
|
|
}
|
|
|
|
if r.routing != "" {
|
|
|
|
indexCommand["_routing"] = r.routing
|
|
|
|
}
|
|
|
|
if r.parent != "" {
|
|
|
|
indexCommand["_parent"] = r.parent
|
|
|
|
}
|
|
|
|
if r.version > 0 {
|
|
|
|
indexCommand["_version"] = r.version
|
|
|
|
}
|
|
|
|
if r.versionType != "" {
|
|
|
|
indexCommand["_version_type"] = r.versionType
|
|
|
|
}
|
Add `access` format support for Elasticsearch notification target (#4006)
This change adds `access` format support for notifications to a
Elasticsearch server, and it refactors `namespace` format support.
In the case of `access` format, for each event in Minio, a JSON
document is inserted into Elasticsearch with its timestamp set to the
event's timestamp, and with the ID generated automatically by
elasticsearch. No events are modified or deleted in this mode.
In the case of `namespace` format, for each event in Minio, a JSON
document is keyed together by the bucket and object name is updated in
Elasticsearch. In the case of an object being created or over-written
in Minio, a new document or an existing document is inserted into the
Elasticsearch index. If an object is deleted in Minio, the
corresponding document is deleted from the Elasticsearch index.
Additionally, this change upgrades Elasticsearch support to the 5.x
series. This is a breaking change, and users of previous elasticsearch
versions should upgrade.
Also updates documentation on Elasticsearch notification target usage
and has a link to an elasticsearch upgrade guide.
This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
|
|
|
if r.retryOnConflict != nil {
|
|
|
|
indexCommand["_retry_on_conflict"] = *r.retryOnConflict
|
|
|
|
}
|
|
|
|
if r.ttl != "" {
|
|
|
|
indexCommand["_ttl"] = r.ttl
|
|
|
|
}
|
|
|
|
if r.pipeline != "" {
|
|
|
|
indexCommand["pipeline"] = r.pipeline
|
2016-07-24 01:51:12 -04:00
|
|
|
}
|
|
|
|
command[r.opType] = indexCommand
|
|
|
|
line, err := json.Marshal(command)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
lines[0] = string(line)
|
|
|
|
|
|
|
|
// "field1" ...
|
|
|
|
if r.doc != nil {
|
|
|
|
switch t := r.doc.(type) {
|
|
|
|
default:
|
|
|
|
body, err := json.Marshal(r.doc)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
lines[1] = string(body)
|
|
|
|
case json.RawMessage:
|
|
|
|
lines[1] = string(t)
|
|
|
|
case *json.RawMessage:
|
|
|
|
lines[1] = string(*t)
|
|
|
|
case string:
|
|
|
|
lines[1] = t
|
|
|
|
case *string:
|
|
|
|
lines[1] = *t
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
lines[1] = "{}"
|
|
|
|
}
|
|
|
|
|
|
|
|
r.source = lines
|
|
|
|
return lines, nil
|
|
|
|
}
|