2016-10-03 20:29:55 -04:00
|
|
|
/*
|
|
|
|
* Minio Cloud Storage, (C) 2014-2016 Minio, Inc.
|
|
|
|
*
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
* you may not use this file except in compliance with the License.
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
*
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
*
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
* limitations under the License.
|
|
|
|
*/
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
// PostgreSQL Notifier implementation. Two formats, "namespace" and
|
|
|
|
// "access" are supported.
|
|
|
|
//
|
|
|
|
// * Namespace format
|
|
|
|
//
|
|
|
|
// On each create or update object event in Minio Object storage
|
|
|
|
// server, a row is created or updated in the table in Postgres. On
|
|
|
|
// each object removal, the corresponding row is deleted from the
|
|
|
|
// table.
|
|
|
|
//
|
|
|
|
// A table with a specific structure (column names, column types, and
|
|
|
|
// primary key/uniqueness constraint) is used. The user may set the
|
|
|
|
// table name in the configuration. A sample SQL command that creates
|
|
|
|
// a table with the required structure is:
|
2016-10-03 20:29:55 -04:00
|
|
|
//
|
|
|
|
// CREATE TABLE myminio (
|
|
|
|
// key VARCHAR PRIMARY KEY,
|
|
|
|
// value JSONB
|
|
|
|
// );
|
|
|
|
//
|
|
|
|
// PostgreSQL's "INSERT ... ON CONFLICT ... DO UPDATE ..." feature
|
|
|
|
// (UPSERT) is used here, so the minimum version of PostgreSQL
|
|
|
|
// required is 9.5.
|
|
|
|
//
|
2017-03-27 14:27:25 -04:00
|
|
|
// * Access format
|
|
|
|
//
|
|
|
|
// On each event, a row is appended to the configured table. There is
|
|
|
|
// no deletion or modification of existing rows.
|
|
|
|
//
|
|
|
|
// A different table schema is used for this format. A sample SQL
|
|
|
|
// commant that creates a table with the required structure is:
|
|
|
|
//
|
|
|
|
// CREATE TABLE myminio (
|
|
|
|
// event_time TIMESTAMP WITH TIME ZONE NOT NULL,
|
|
|
|
// event_data JSONB
|
|
|
|
// );
|
2016-10-03 20:29:55 -04:00
|
|
|
|
|
|
|
package cmd
|
|
|
|
|
|
|
|
import (
|
|
|
|
"database/sql"
|
|
|
|
"encoding/json"
|
|
|
|
"fmt"
|
|
|
|
"io/ioutil"
|
|
|
|
"strings"
|
2017-03-27 14:27:25 -04:00
|
|
|
"time"
|
2016-10-03 20:29:55 -04:00
|
|
|
|
|
|
|
"github.com/Sirupsen/logrus"
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
// Register postgres driver
|
2016-10-03 20:29:55 -04:00
|
|
|
_ "github.com/lib/pq"
|
|
|
|
)
|
|
|
|
|
|
|
|
const (
|
2017-03-27 14:27:25 -04:00
|
|
|
// Queries for format=namespace mode. Here the `key` column is
|
|
|
|
// the bucket and object of the event. When objects are
|
|
|
|
// deleted, the corresponding row is deleted in the
|
|
|
|
// table. When objects are created or over-written, rows are
|
|
|
|
// inserted or updated respectively in the table.
|
|
|
|
upsertRowForNS = `INSERT INTO %s (key, value)
|
2016-10-03 20:29:55 -04:00
|
|
|
VALUES ($1, $2)
|
|
|
|
ON CONFLICT (key)
|
|
|
|
DO UPDATE SET value = EXCLUDED.value;`
|
2017-03-27 14:27:25 -04:00
|
|
|
deleteRowForNS = ` DELETE FROM %s
|
2016-10-03 20:29:55 -04:00
|
|
|
WHERE key = $1;`
|
2017-03-27 14:27:25 -04:00
|
|
|
createTableForNS = `CREATE TABLE %s (
|
2016-10-03 20:29:55 -04:00
|
|
|
key VARCHAR PRIMARY KEY,
|
|
|
|
value JSONB
|
|
|
|
);`
|
2017-03-27 14:27:25 -04:00
|
|
|
|
|
|
|
// Queries for format=access mode. Here the `event_time`
|
|
|
|
// column of the table, stores the time at which the event
|
|
|
|
// occurred in the Minio server.
|
|
|
|
insertRowForAccess = `INSERT INTO %s (event_time, event_data)
|
|
|
|
VALUES ($1, $2);`
|
|
|
|
createTableForAccess = `CREATE TABLE %s (
|
|
|
|
event_time TIMESTAMP WITH TIME ZONE NOT NULL,
|
|
|
|
event_data JSONB
|
|
|
|
);`
|
|
|
|
|
|
|
|
// Query to check if a table already exists.
|
2016-10-03 20:29:55 -04:00
|
|
|
tableExists = `SELECT 1 FROM %s;`
|
|
|
|
)
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
var (
|
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
|
|
|
pgErrFunc = newNotificationErrorFactory("PostgreSQL")
|
|
|
|
|
|
|
|
errPGFormatError = pgErrFunc(`"format" value is invalid - it must be one of "%s" or "%s".`, formatNamespace, formatAccess)
|
|
|
|
errPGTableError = pgErrFunc("Table was not specified in the configuration.")
|
2017-03-27 14:27:25 -04:00
|
|
|
)
|
|
|
|
|
2016-10-03 20:29:55 -04:00
|
|
|
type postgreSQLNotify struct {
|
|
|
|
Enable bool `json:"enable"`
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
Format string `json:"format"`
|
|
|
|
|
|
|
|
// Pass connection string in config directly. This string is
|
2016-10-03 20:29:55 -04:00
|
|
|
// formatted according to
|
|
|
|
// https://godoc.org/github.com/lib/pq#hdr-Connection_String_Parameters
|
|
|
|
ConnectionString string `json:"connectionString"`
|
|
|
|
// specifying a table name is required.
|
|
|
|
Table string `json:"table"`
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
// The values below, if non-empty are appended to
|
|
|
|
// ConnectionString above. Default values are shown in
|
|
|
|
// comments below (implicitly used by the library).
|
|
|
|
Host string `json:"host"` // default: localhost
|
|
|
|
Port string `json:"port"` // default: 5432
|
|
|
|
User string `json:"user"` // default: user running minio
|
|
|
|
Password string `json:"password"` // default: no password
|
|
|
|
Database string `json:"database"` // default: same as user
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
|
|
|
|
2017-03-15 19:30:34 -04:00
|
|
|
func (p *postgreSQLNotify) Validate() error {
|
|
|
|
if !p.Enable {
|
|
|
|
return nil
|
|
|
|
}
|
2017-03-27 14:27:25 -04:00
|
|
|
if p.Format != formatNamespace && p.Format != formatAccess {
|
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
|
|
|
return errPGFormatError
|
2017-03-27 14:27:25 -04:00
|
|
|
}
|
|
|
|
if p.ConnectionString == "" {
|
|
|
|
if _, err := checkURL(p.Host); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if p.Table == "" {
|
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
|
|
|
return errPGTableError
|
2017-03-15 19:30:34 -04:00
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2016-10-03 20:29:55 -04:00
|
|
|
type pgConn struct {
|
|
|
|
connStr string
|
|
|
|
table string
|
2017-03-27 14:27:25 -04:00
|
|
|
format string
|
2016-10-03 20:29:55 -04:00
|
|
|
preparedStmts map[string]*sql.Stmt
|
|
|
|
*sql.DB
|
|
|
|
}
|
|
|
|
|
2017-06-21 22:53:09 -04:00
|
|
|
func dialPostgreSQL(pgN postgreSQLNotify) (pc pgConn, e error) {
|
2016-10-03 20:29:55 -04:00
|
|
|
if !pgN.Enable {
|
2017-06-21 22:53:09 -04:00
|
|
|
return pc, errNotifyNotEnabled
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
// collect connection params
|
|
|
|
params := []string{pgN.ConnectionString}
|
|
|
|
if pgN.Host != "" {
|
|
|
|
params = append(params, "host="+pgN.Host)
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
2017-03-27 14:27:25 -04:00
|
|
|
if pgN.Port != "" {
|
|
|
|
params = append(params, "port="+pgN.Port)
|
|
|
|
}
|
|
|
|
if pgN.User != "" {
|
|
|
|
params = append(params, "user="+pgN.User)
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
2017-03-27 14:27:25 -04:00
|
|
|
if pgN.Password != "" {
|
|
|
|
params = append(params, "password="+pgN.Password)
|
|
|
|
}
|
|
|
|
if pgN.Database != "" {
|
|
|
|
params = append(params, "dbname="+pgN.Database)
|
|
|
|
}
|
|
|
|
connStr := strings.Join(params, " ")
|
2016-10-03 20:29:55 -04:00
|
|
|
|
|
|
|
db, err := sql.Open("postgres", connStr)
|
|
|
|
if err != nil {
|
2017-06-21 22:53:09 -04:00
|
|
|
return pc, pgErrFunc(
|
2017-03-27 14:27:25 -04:00
|
|
|
"Connection opening failure (connectionString=%s): %v",
|
|
|
|
connStr, err)
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
// ping to check that server is actually reachable.
|
|
|
|
err = db.Ping()
|
|
|
|
if err != nil {
|
2017-06-21 22:53:09 -04:00
|
|
|
return pc, pgErrFunc("Ping to server failed with: %v",
|
2017-03-27 14:27:25 -04:00
|
|
|
err)
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
// check that table exists - if not, create it.
|
|
|
|
_, err = db.Exec(fmt.Sprintf(tableExists, pgN.Table))
|
|
|
|
if err != nil {
|
2017-03-27 14:27:25 -04:00
|
|
|
createStmt := createTableForNS
|
|
|
|
if pgN.Format == formatAccess {
|
|
|
|
createStmt = createTableForAccess
|
|
|
|
}
|
|
|
|
|
2016-10-03 20:29:55 -04:00
|
|
|
// most likely, table does not exist. try to create it:
|
2017-03-27 14:27:25 -04:00
|
|
|
_, errCreate := db.Exec(fmt.Sprintf(createStmt, pgN.Table))
|
2016-10-03 20:29:55 -04:00
|
|
|
if errCreate != nil {
|
|
|
|
// failed to create the table. error out.
|
2017-06-21 22:53:09 -04:00
|
|
|
return pc, pgErrFunc(
|
2017-03-27 14:27:25 -04:00
|
|
|
"'Select' failed with %v, then 'Create Table' failed with %v",
|
2016-10-03 20:29:55 -04:00
|
|
|
err, errCreate,
|
|
|
|
)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// create prepared statements
|
|
|
|
stmts := make(map[string]*sql.Stmt)
|
2017-03-27 14:27:25 -04:00
|
|
|
switch pgN.Format {
|
|
|
|
case formatNamespace:
|
|
|
|
// insert or update statement
|
|
|
|
stmts["upsertRow"], err = db.Prepare(fmt.Sprintf(upsertRowForNS,
|
|
|
|
pgN.Table))
|
|
|
|
if err != nil {
|
2017-06-21 22:53:09 -04:00
|
|
|
return pc, pgErrFunc(
|
2017-03-27 14:27:25 -04:00
|
|
|
"create UPSERT prepared statement failed with: %v", err)
|
|
|
|
}
|
|
|
|
// delete statement
|
|
|
|
stmts["deleteRow"], err = db.Prepare(fmt.Sprintf(deleteRowForNS,
|
|
|
|
pgN.Table))
|
|
|
|
if err != nil {
|
2017-06-21 22:53:09 -04:00
|
|
|
return pc, pgErrFunc(
|
2017-03-27 14:27:25 -04:00
|
|
|
"create DELETE prepared statement failed with: %v", err)
|
|
|
|
}
|
|
|
|
case formatAccess:
|
|
|
|
// insert statement
|
|
|
|
stmts["insertRow"], err = db.Prepare(fmt.Sprintf(insertRowForAccess,
|
|
|
|
pgN.Table))
|
|
|
|
if err != nil {
|
2017-06-21 22:53:09 -04:00
|
|
|
return pc, pgErrFunc(
|
2017-03-27 14:27:25 -04:00
|
|
|
"create INSERT prepared statement failed with: %v", err)
|
|
|
|
}
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
return pgConn{connStr, pgN.Table, pgN.Format, stmts, db}, nil
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
func newPostgreSQLNotify(accountID string) (*logrus.Logger, error) {
|
2017-11-29 16:12:47 -05:00
|
|
|
pgNotify := globalServerConfig.Notify.GetPostgreSQLByID(accountID)
|
2016-10-03 20:29:55 -04:00
|
|
|
|
|
|
|
// Dial postgres
|
|
|
|
pgC, err := dialPostgreSQL(pgNotify)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
pgLog := logrus.New()
|
|
|
|
|
|
|
|
pgLog.Out = ioutil.Discard
|
|
|
|
|
|
|
|
pgLog.Formatter = new(logrus.JSONFormatter)
|
|
|
|
|
|
|
|
pgLog.Hooks.Add(pgC)
|
|
|
|
|
|
|
|
return pgLog, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (pgC pgConn) Close() {
|
|
|
|
// first close all prepared statements
|
|
|
|
for _, v := range pgC.preparedStmts {
|
|
|
|
_ = v.Close()
|
|
|
|
}
|
|
|
|
// close db connection
|
|
|
|
_ = pgC.DB.Close()
|
|
|
|
}
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
func jsonEncodeEventData(d interface{}) ([]byte, error) {
|
|
|
|
// json encode the value for the row
|
|
|
|
value, err := json.Marshal(map[string]interface{}{
|
|
|
|
"Records": d,
|
|
|
|
})
|
|
|
|
if err != nil {
|
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
|
|
|
return nil, pgErrFunc(
|
2017-03-27 14:27:25 -04:00
|
|
|
"Unable to encode event %v to JSON: %v", d, err)
|
|
|
|
}
|
|
|
|
return value, nil
|
|
|
|
}
|
|
|
|
|
2016-10-03 20:29:55 -04:00
|
|
|
func (pgC pgConn) Fire(entry *logrus.Entry) error {
|
|
|
|
// get event type by trying to convert to string
|
|
|
|
entryEventType, ok := entry.Data["EventType"].(string)
|
|
|
|
if !ok {
|
|
|
|
// ignore event if converting EventType to string
|
|
|
|
// fails.
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
switch pgC.format {
|
|
|
|
case formatNamespace:
|
|
|
|
// Check for event delete
|
|
|
|
if eventMatch(entryEventType, []string{"s3:ObjectRemoved:*"}) {
|
|
|
|
// delete row from the table
|
|
|
|
_, err := pgC.preparedStmts["deleteRow"].Exec(entry.Data["Key"])
|
|
|
|
if err != nil {
|
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
|
|
|
return pgErrFunc(
|
2017-03-27 14:27:25 -04:00
|
|
|
"Error deleting event with key=%v: %v",
|
|
|
|
entry.Data["Key"], err,
|
|
|
|
)
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
value, err := jsonEncodeEventData(entry.Data["Records"])
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
// upsert row into the table
|
|
|
|
_, err = pgC.preparedStmts["upsertRow"].Exec(entry.Data["Key"], value)
|
|
|
|
if err != nil {
|
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
|
|
|
return pgErrFunc(
|
2017-03-27 14:27:25 -04:00
|
|
|
"Unable to upsert event with key=%v and value=%v: %v",
|
|
|
|
entry.Data["Key"], entry.Data["Records"], err,
|
|
|
|
)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
case formatAccess:
|
|
|
|
// eventTime is taken from the first entry in the
|
|
|
|
// records.
|
|
|
|
events, ok := entry.Data["Records"].([]NotificationEvent)
|
|
|
|
if !ok {
|
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
|
|
|
return pgErrFunc("unable to extract event time due to conversion error of entry.Data[\"Records\"]=%v", entry.Data["Records"])
|
2017-03-27 14:27:25 -04:00
|
|
|
}
|
|
|
|
eventTime, err := time.Parse(timeFormatAMZ, events[0].EventTime)
|
2016-10-03 20:29:55 -04:00
|
|
|
if err != nil {
|
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
|
|
|
return pgErrFunc("unable to parse event time \"%s\": %v",
|
2017-03-27 14:27:25 -04:00
|
|
|
events[0].EventTime, err)
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
2017-03-27 14:27:25 -04:00
|
|
|
|
|
|
|
value, err := jsonEncodeEventData(entry.Data["Records"])
|
2016-10-03 20:29:55 -04:00
|
|
|
if err != nil {
|
2017-03-27 14:27:25 -04:00
|
|
|
return err
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
|
|
|
|
2017-03-27 14:27:25 -04:00
|
|
|
_, err = pgC.preparedStmts["insertRow"].Exec(eventTime, value)
|
2016-10-03 20:29:55 -04:00
|
|
|
if err != nil {
|
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
|
|
|
return pgErrFunc("Unable to insert event with value=%v: %v",
|
2017-03-27 14:27:25 -04:00
|
|
|
value, err)
|
2016-10-03 20:29:55 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (pgC pgConn) Levels() []logrus.Level {
|
|
|
|
return []logrus.Level{
|
|
|
|
logrus.InfoLevel,
|
|
|
|
}
|
|
|
|
}
|