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 23:11:27 +02:00
|
|
|
// Copyright 2012-present Oliver Eilhard. All rights reserved.
|
2016-07-24 07:51:12 +02: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 23:11:27 +02:00
|
|
|
"golang.org/x/net/context"
|
|
|
|
|
|
|
|
"gopkg.in/olivere/elastic.v5/uritemplates"
|
2016-07-24 07:51:12 +02:00
|
|
|
)
|
|
|
|
|
|
|
|
// IndicesCloseService closes an index.
|
|
|
|
//
|
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 23:11:27 +02:00
|
|
|
// See https://www.elastic.co/guide/en/elasticsearch/reference/5.2/indices-open-close.html
|
2016-07-24 07:51:12 +02:00
|
|
|
// for details.
|
|
|
|
type IndicesCloseService struct {
|
|
|
|
client *Client
|
|
|
|
pretty bool
|
|
|
|
index string
|
|
|
|
timeout string
|
|
|
|
masterTimeout string
|
|
|
|
ignoreUnavailable *bool
|
|
|
|
allowNoIndices *bool
|
|
|
|
expandWildcards string
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewIndicesCloseService creates and initializes a new IndicesCloseService.
|
|
|
|
func NewIndicesCloseService(client *Client) *IndicesCloseService {
|
|
|
|
return &IndicesCloseService{client: client}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Index is the name of the index to close.
|
|
|
|
func (s *IndicesCloseService) Index(index string) *IndicesCloseService {
|
|
|
|
s.index = index
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Timeout is an explicit operation timeout.
|
|
|
|
func (s *IndicesCloseService) Timeout(timeout string) *IndicesCloseService {
|
|
|
|
s.timeout = timeout
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// MasterTimeout specifies the timeout for connection to master.
|
|
|
|
func (s *IndicesCloseService) MasterTimeout(masterTimeout string) *IndicesCloseService {
|
|
|
|
s.masterTimeout = masterTimeout
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// IgnoreUnavailable indicates whether specified concrete indices should be
|
|
|
|
// ignored when unavailable (missing or closed).
|
|
|
|
func (s *IndicesCloseService) IgnoreUnavailable(ignoreUnavailable bool) *IndicesCloseService {
|
|
|
|
s.ignoreUnavailable = &ignoreUnavailable
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// AllowNoIndices indicates whether to ignore if a wildcard indices
|
|
|
|
// expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified).
|
|
|
|
func (s *IndicesCloseService) AllowNoIndices(allowNoIndices bool) *IndicesCloseService {
|
|
|
|
s.allowNoIndices = &allowNoIndices
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// ExpandWildcards indicates whether to expand wildcard expression to
|
|
|
|
// concrete indices that are open, closed or both.
|
|
|
|
func (s *IndicesCloseService) ExpandWildcards(expandWildcards string) *IndicesCloseService {
|
|
|
|
s.expandWildcards = expandWildcards
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// Pretty indicates that the JSON response be indented and human readable.
|
|
|
|
func (s *IndicesCloseService) Pretty(pretty bool) *IndicesCloseService {
|
|
|
|
s.pretty = pretty
|
|
|
|
return s
|
|
|
|
}
|
|
|
|
|
|
|
|
// buildURL builds the URL for the operation.
|
|
|
|
func (s *IndicesCloseService) buildURL() (string, url.Values, error) {
|
|
|
|
// Build URL
|
|
|
|
path, err := uritemplates.Expand("/{index}/_close", map[string]string{
|
|
|
|
"index": s.index,
|
|
|
|
})
|
|
|
|
if err != nil {
|
|
|
|
return "", url.Values{}, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Add query string parameters
|
|
|
|
params := url.Values{}
|
|
|
|
if s.allowNoIndices != nil {
|
|
|
|
params.Set("allow_no_indices", fmt.Sprintf("%v", *s.allowNoIndices))
|
|
|
|
}
|
|
|
|
if s.expandWildcards != "" {
|
|
|
|
params.Set("expand_wildcards", s.expandWildcards)
|
|
|
|
}
|
|
|
|
if s.timeout != "" {
|
|
|
|
params.Set("timeout", s.timeout)
|
|
|
|
}
|
|
|
|
if s.masterTimeout != "" {
|
|
|
|
params.Set("master_timeout", s.masterTimeout)
|
|
|
|
}
|
|
|
|
if s.ignoreUnavailable != nil {
|
|
|
|
params.Set("ignore_unavailable", fmt.Sprintf("%v", *s.ignoreUnavailable))
|
|
|
|
}
|
|
|
|
|
|
|
|
return path, params, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Validate checks if the operation is valid.
|
|
|
|
func (s *IndicesCloseService) Validate() error {
|
|
|
|
var invalid []string
|
|
|
|
if s.index == "" {
|
|
|
|
invalid = append(invalid, "Index")
|
|
|
|
}
|
|
|
|
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 23:11:27 +02:00
|
|
|
func (s *IndicesCloseService) Do(ctx context.Context) (*IndicesCloseResponse, error) {
|
2016-07-24 07:51:12 +02:00
|
|
|
// Check pre-conditions
|
|
|
|
if err := s.Validate(); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Get URL for request
|
|
|
|
path, params, err := s.buildURL()
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// 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 23:11:27 +02:00
|
|
|
res, err := s.client.PerformRequest(ctx, "POST", path, params, nil)
|
2016-07-24 07:51:12 +02:00
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Return operation response
|
|
|
|
ret := new(IndicesCloseResponse)
|
|
|
|
if err := s.client.decoder.Decode(res.Body, ret); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return ret, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// IndicesCloseResponse is the response of IndicesCloseService.Do.
|
|
|
|
type IndicesCloseResponse struct {
|
|
|
|
Acknowledged bool `json:"acknowledged"`
|
|
|
|
}
|