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
|
|
|
|
|
|
|
|
// HasParentQuery accepts a query and a parent type. The query is executed
|
|
|
|
// in the parent document space which is specified by the parent type.
|
|
|
|
// This query returns child documents which associated parents have matched.
|
|
|
|
// For the rest has_parent query has the same options and works in the
|
|
|
|
// same manner as has_child 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-parent-query.html
|
2016-07-24 07:51:12 +02:00
|
|
|
type HasParentQuery struct {
|
|
|
|
query Query
|
|
|
|
parentType 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
|
|
|
score *bool
|
2016-07-24 07:51:12 +02:00
|
|
|
queryName string
|
|
|
|
innerHit *InnerHit
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewHasParentQuery creates and initializes a new has_parent query.
|
|
|
|
func NewHasParentQuery(parentType string, query Query) *HasParentQuery {
|
|
|
|
return &HasParentQuery{
|
|
|
|
query: query,
|
|
|
|
parentType: parentType,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Boost sets the boost for this query.
|
|
|
|
func (q *HasParentQuery) Boost(boost float64) *HasParentQuery {
|
|
|
|
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
|
|
|
// Score defines if the parent score is mapped into the child documents.
|
|
|
|
func (q *HasParentQuery) Score(score bool) *HasParentQuery {
|
|
|
|
q.score = &score
|
2016-07-24 07:51:12 +02:00
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
|
|
|
// QueryName specifies the query name for the filter that can be used when
|
|
|
|
// searching for matched filters per hit.
|
|
|
|
func (q *HasParentQuery) QueryName(queryName string) *HasParentQuery {
|
|
|
|
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 *HasParentQuery) InnerHit(innerHit *InnerHit) *HasParentQuery {
|
|
|
|
q.innerHit = innerHit
|
|
|
|
return q
|
|
|
|
}
|
|
|
|
|
|
|
|
// Source returns JSON for the function score query.
|
|
|
|
func (q *HasParentQuery) Source() (interface{}, error) {
|
|
|
|
// {
|
|
|
|
// "has_parent" : {
|
|
|
|
// "parent_type" : "blog",
|
|
|
|
// "query" : {
|
|
|
|
// "term" : {
|
|
|
|
// "tag" : "something"
|
|
|
|
// }
|
|
|
|
// }
|
|
|
|
// }
|
|
|
|
// }
|
|
|
|
source := make(map[string]interface{})
|
|
|
|
query := make(map[string]interface{})
|
|
|
|
source["has_parent"] = query
|
|
|
|
|
|
|
|
src, err := q.query.Source()
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
query["query"] = src
|
|
|
|
query["parent_type"] = q.parentType
|
|
|
|
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.score != nil {
|
|
|
|
query["score"] = *q.score
|
2016-07-24 07:51:12 +02:00
|
|
|
}
|
|
|
|
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
|
|
|
|
}
|