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
|
|
|
// Copyright 2012-present Oliver Eilhard. All rights reserved.
|
2016-07-24 01:51:12 -04:00
|
|
|
// Use of this source code is governed by a MIT-license.
|
|
|
|
// See http://olivere.mit-license.org/license.txt for details.
|
|
|
|
|
|
|
|
package elastic
|
|
|
|
|
|
|
|
import (
|
|
|
|
"fmt"
|
|
|
|
"net/url"
|
|
|
|
|
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
|
|
|
"golang.org/x/net/context"
|
|
|
|
|
|
|
|
"gopkg.in/olivere/elastic.v5/uritemplates"
|
2016-07-24 01:51:12 -04:00
|
|
|
)
|
|
|
|
|
|
|
|
// IndexService adds or updates a typed JSON document in a specified index,
|
|
|
|
// making it searchable.
|
|
|
|
//
|
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
|
2016-07-24 01:51:12 -04:00
|
|
|
// for details.
|
|
|
|
type IndexService struct {
|
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
|
|
|
client *Client
|
|
|
|
pretty bool
|
|
|
|
id string
|
|
|
|
index string
|
|
|
|
typ string
|
|
|
|
parent string
|
|
|
|
routing string
|
|
|
|
timeout string
|
|
|
|
timestamp string
|
|
|
|
ttl string
|
|
|
|
version interface{}
|
|
|
|
opType string
|
|
|
|
versionType string
|
|
|
|
refresh string
|
|
|
|
waitForActiveShards string
|
|
|
|
pipeline string
|
|
|
|
bodyJson interface{}
|
|
|
|
bodyString string
|
2016-07-24 01:51:12 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
// NewIndexService creates a new IndexService.
|
|
|
|
func NewIndexService(client *Client) *IndexService {
|
|
|
|
return &IndexService{
|
|
|
|
client: client,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Id is the document ID.
|
|
|
|
func (s *IndexService) Id(id string) *IndexService {
|
|
|
|
s.id = id
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Index is the name of the index.
|
|
|
|
func (s *IndexService) Index(index string) *IndexService {
|
|
|
|
s.index = index
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Type is the type of the document.
|
|
|
|
func (s *IndexService) Type(typ string) *IndexService {
|
|
|
|
s.typ = typ
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
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
|
|
|
// WaitForActiveShards sets the number of shard copies that must be active
|
|
|
|
// before proceeding with the index operation. Defaults to 1, meaning the
|
|
|
|
// primary shard only. Set to `all` for all shard copies, otherwise set to
|
|
|
|
// any non-negative value less than or equal to the total number of copies
|
|
|
|
// for the shard (number of replicas + 1).
|
|
|
|
func (s *IndexService) WaitForActiveShards(waitForActiveShards string) *IndexService {
|
|
|
|
s.waitForActiveShards = waitForActiveShards
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Pipeline specifies the pipeline id to preprocess incoming documents with.
|
|
|
|
func (s *IndexService) Pipeline(pipeline string) *IndexService {
|
|
|
|
s.pipeline = pipeline
|
2016-07-24 01:51:12 -04:00
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Refresh the index after performing the operation.
|
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
|
|
|
func (s *IndexService) Refresh(refresh string) *IndexService {
|
|
|
|
s.refresh = refresh
|
2016-07-24 01:51:12 -04:00
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Ttl is an expiration time for the document.
|
|
|
|
func (s *IndexService) Ttl(ttl string) *IndexService {
|
|
|
|
s.ttl = ttl
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// TTL is an expiration time for the document (alias for Ttl).
|
|
|
|
func (s *IndexService) TTL(ttl string) *IndexService {
|
|
|
|
s.ttl = ttl
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Version is an explicit version number for concurrency control.
|
|
|
|
func (s *IndexService) Version(version interface{}) *IndexService {
|
|
|
|
s.version = version
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// OpType is an explicit operation type, i.e. "create" or "index" (default).
|
|
|
|
func (s *IndexService) OpType(opType string) *IndexService {
|
|
|
|
s.opType = opType
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Parent is the ID of the parent document.
|
|
|
|
func (s *IndexService) Parent(parent string) *IndexService {
|
|
|
|
s.parent = parent
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Routing is a specific routing value.
|
|
|
|
func (s *IndexService) Routing(routing string) *IndexService {
|
|
|
|
s.routing = routing
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Timeout is an explicit operation timeout.
|
|
|
|
func (s *IndexService) Timeout(timeout string) *IndexService {
|
|
|
|
s.timeout = timeout
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Timestamp is an explicit timestamp for the document.
|
|
|
|
func (s *IndexService) Timestamp(timestamp string) *IndexService {
|
|
|
|
s.timestamp = timestamp
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// VersionType is a specific version type.
|
|
|
|
func (s *IndexService) VersionType(versionType string) *IndexService {
|
|
|
|
s.versionType = versionType
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Pretty indicates that the JSON response be indented and human readable.
|
|
|
|
func (s *IndexService) Pretty(pretty bool) *IndexService {
|
|
|
|
s.pretty = pretty
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// BodyJson is the document as a serializable JSON interface.
|
|
|
|
func (s *IndexService) BodyJson(body interface{}) *IndexService {
|
|
|
|
s.bodyJson = body
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// BodyString is the document encoded as a string.
|
|
|
|
func (s *IndexService) BodyString(body string) *IndexService {
|
|
|
|
s.bodyString = body
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// buildURL builds the URL for the operation.
|
|
|
|
func (s *IndexService) buildURL() (string, string, url.Values, error) {
|
|
|
|
var err error
|
|
|
|
var method, path string
|
|
|
|
|
|
|
|
if s.id != "" {
|
|
|
|
// Create document with manual id
|
|
|
|
method = "PUT"
|
|
|
|
path, err = uritemplates.Expand("/{index}/{type}/{id}", map[string]string{
|
|
|
|
"id": s.id,
|
|
|
|
"index": s.index,
|
|
|
|
"type": s.typ,
|
|
|
|
})
|
|
|
|
} else {
|
|
|
|
// Automatic ID generation
|
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-creation
|
2016-07-24 01:51:12 -04:00
|
|
|
method = "POST"
|
|
|
|
path, err = uritemplates.Expand("/{index}/{type}/", map[string]string{
|
|
|
|
"index": s.index,
|
|
|
|
"type": s.typ,
|
|
|
|
})
|
|
|
|
}
|
|
|
|
if err != nil {
|
|
|
|
return "", "", url.Values{}, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Add query string parameters
|
|
|
|
params := url.Values{}
|
|
|
|
if s.pretty {
|
|
|
|
params.Set("pretty", "1")
|
|
|
|
}
|
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 s.waitForActiveShards != "" {
|
|
|
|
params.Set("wait_for_active_shards", s.waitForActiveShards)
|
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
|
|
|
if s.refresh != "" {
|
|
|
|
params.Set("refresh", s.refresh)
|
2016-07-24 01:51:12 -04:00
|
|
|
}
|
|
|
|
if s.opType != "" {
|
|
|
|
params.Set("op_type", s.opType)
|
|
|
|
}
|
|
|
|
if s.parent != "" {
|
|
|
|
params.Set("parent", s.parent)
|
|
|
|
}
|
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 s.pipeline != "" {
|
|
|
|
params.Set("pipeline", s.pipeline)
|
2016-07-24 01:51:12 -04:00
|
|
|
}
|
|
|
|
if s.routing != "" {
|
|
|
|
params.Set("routing", s.routing)
|
|
|
|
}
|
|
|
|
if s.timeout != "" {
|
|
|
|
params.Set("timeout", s.timeout)
|
|
|
|
}
|
|
|
|
if s.timestamp != "" {
|
|
|
|
params.Set("timestamp", s.timestamp)
|
|
|
|
}
|
|
|
|
if s.ttl != "" {
|
|
|
|
params.Set("ttl", s.ttl)
|
|
|
|
}
|
|
|
|
if s.version != nil {
|
|
|
|
params.Set("version", fmt.Sprintf("%v", s.version))
|
|
|
|
}
|
|
|
|
if s.versionType != "" {
|
|
|
|
params.Set("version_type", s.versionType)
|
|
|
|
}
|
|
|
|
return method, path, params, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Validate checks if the operation is valid.
|
|
|
|
func (s *IndexService) Validate() error {
|
|
|
|
var invalid []string
|
|
|
|
if s.index == "" {
|
|
|
|
invalid = append(invalid, "Index")
|
|
|
|
}
|
|
|
|
if s.typ == "" {
|
|
|
|
invalid = append(invalid, "Type")
|
|
|
|
}
|
|
|
|
if s.bodyString == "" && s.bodyJson == nil {
|
|
|
|
invalid = append(invalid, "BodyJson")
|
|
|
|
}
|
|
|
|
if len(invalid) > 0 {
|
|
|
|
return fmt.Errorf("missing required fields: %v", invalid)
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Do executes the operation.
|
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
|
|
|
func (s *IndexService) Do(ctx context.Context) (*IndexResponse, error) {
|
2016-07-24 01:51:12 -04:00
|
|
|
// Check pre-conditions
|
|
|
|
if err := s.Validate(); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Get URL for request
|
|
|
|
method, path, params, err := s.buildURL()
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Setup HTTP request body
|
|
|
|
var body interface{}
|
|
|
|
if s.bodyJson != nil {
|
|
|
|
body = s.bodyJson
|
|
|
|
} else {
|
|
|
|
body = s.bodyString
|
|
|
|
}
|
|
|
|
|
|
|
|
// Get HTTP response
|
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
|
|
|
res, err := s.client.PerformRequest(ctx, method, path, params, body)
|
2016-07-24 01:51:12 -04:00
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Return operation response
|
|
|
|
ret := new(IndexResponse)
|
|
|
|
if err := s.client.decoder.Decode(res.Body, ret); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return ret, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// IndexResponse is the result of indexing a document in Elasticsearch.
|
|
|
|
type IndexResponse struct {
|
|
|
|
// TODO _shards { total, failed, successful }
|
|
|
|
Index string `json:"_index"`
|
|
|
|
Type string `json:"_type"`
|
|
|
|
Id string `json:"_id"`
|
|
|
|
Version int `json:"_version"`
|
|
|
|
Created bool `json:"created"`
|
|
|
|
}
|