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
|
|
|
|
|
|
|
|
// HasChildQuery accepts a query and the child type to run against, and results
|
|
|
|
// in parent documents that have child docs matching the query.
|
|
|
|
//
|
|
|
|
// For more details, see
|
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
|
|
|
// https://www.elastic.co/guide/en/elasticsearch/reference/5.2/query-dsl-has-child-query.html
|
2016-07-24 07:51:12 +02:00
|
|
|
type HasChildQuery struct {
|
|
|
|
query Query
|
|
|
|
childType string
|
|
|
|
boost *float64
|
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
|
|
|
scoreMode string
|
2016-07-24 07:51:12 +02:00
|
|
|
minChildren *int
|
|
|
|
maxChildren *int
|
|
|
|
shortCircuitCutoff *int
|
|
|
|
queryName string
|
|
|
|
innerHit *InnerHit
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewHasChildQuery creates and initializes a new has_child query.
|
|
|
|
func NewHasChildQuery(childType string, query Query) *HasChildQuery {
|
|
|
|
return &HasChildQuery{
|
|
|
|
query: query,
|
|
|
|
childType: childType,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Boost sets the boost for this query.
|
|
|
|
func (q *HasChildQuery) Boost(boost float64) *HasChildQuery {
|
|
|
|
q.boost = &boost
|
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
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
|
|
|
// ScoreMode defines how the scores from the matching child documents
|
|
|
|
// are mapped into the parent document. Allowed values are: min, max,
|
|
|
|
// avg, or none.
|
|
|
|
func (q *HasChildQuery) ScoreMode(scoreMode string) *HasChildQuery {
|
|
|
|
q.scoreMode = scoreMode
|
2016-07-24 07:51:12 +02:00
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
|
|
|
// MinChildren defines the minimum number of children that are required
|
|
|
|
// to match for the parent to be considered a match.
|
|
|
|
func (q *HasChildQuery) MinChildren(minChildren int) *HasChildQuery {
|
|
|
|
q.minChildren = &minChildren
|
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
|
|
|
// MaxChildren defines the maximum number of children that are required
|
|
|
|
// to match for the parent to be considered a match.
|
|
|
|
func (q *HasChildQuery) MaxChildren(maxChildren int) *HasChildQuery {
|
|
|
|
q.maxChildren = &maxChildren
|
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
|
|
|
// ShortCircuitCutoff configures what cut off point only to evaluate
|
|
|
|
// parent documents that contain the matching parent id terms instead
|
|
|
|
// of evaluating all parent docs.
|
|
|
|
func (q *HasChildQuery) ShortCircuitCutoff(shortCircuitCutoff int) *HasChildQuery {
|
|
|
|
q.shortCircuitCutoff = &shortCircuitCutoff
|
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
|
|
|
// QueryName specifies the query name for the filter that can be used when
|
|
|
|
// searching for matched filters per hit.
|
|
|
|
func (q *HasChildQuery) QueryName(queryName string) *HasChildQuery {
|
|
|
|
q.queryName = queryName
|
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
|
|
|
// InnerHit sets the inner hit definition in the scope of this query and
|
|
|
|
// reusing the defined type and query.
|
|
|
|
func (q *HasChildQuery) InnerHit(innerHit *InnerHit) *HasChildQuery {
|
|
|
|
q.innerHit = innerHit
|
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
|
|
|
// Source returns JSON for the function score query.
|
|
|
|
func (q *HasChildQuery) Source() (interface{}, error) {
|
|
|
|
// {
|
|
|
|
// "has_child" : {
|
|
|
|
// "type" : "blog_tag",
|
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
|
|
|
// "score_mode" : "min",
|
2016-07-24 07:51:12 +02:00
|
|
|
// "query" : {
|
|
|
|
// "term" : {
|
|
|
|
// "tag" : "something"
|
|
|
|
// }
|
|
|
|
// }
|
|
|
|
// }
|
|
|
|
// }
|
|
|
|
source := make(map[string]interface{})
|
|
|
|
query := make(map[string]interface{})
|
|
|
|
source["has_child"] = query
|
|
|
|
|
|
|
|
src, err := q.query.Source()
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
query["query"] = src
|
|
|
|
query["type"] = q.childType
|
|
|
|
if q.boost != nil {
|
|
|
|
query["boost"] = *q.boost
|
|
|
|
}
|
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
|
|
|
if q.scoreMode != "" {
|
|
|
|
query["score_mode"] = q.scoreMode
|
2016-07-24 07:51:12 +02:00
|
|
|
}
|
|
|
|
if q.minChildren != nil {
|
|
|
|
query["min_children"] = *q.minChildren
|
|
|
|
}
|
|
|
|
if q.maxChildren != nil {
|
|
|
|
query["max_children"] = *q.maxChildren
|
|
|
|
}
|
|
|
|
if q.shortCircuitCutoff != nil {
|
|
|
|
query["short_circuit_cutoff"] = *q.shortCircuitCutoff
|
|
|
|
}
|
|
|
|
if q.queryName != "" {
|
|
|
|
query["_name"] = q.queryName
|
|
|
|
}
|
|
|
|
if q.innerHit != nil {
|
|
|
|
src, err := q.innerHit.Source()
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
query["inner_hits"] = src
|
|
|
|
}
|
|
|
|
return source, nil
|
|
|
|
}
|