notify_postgres       publish bucket notifications to Postgres databases
notify_elasticsearch  publish bucket notifications to Elasticsearch endpoints
notify_redis          publish bucket notifications to Redis datastores
```

### Accessing configuration

All configuration changes can be made using [`mc admin config` get/set/reset/export/import commands](https://github.com/minio/mc/blob/master/docs/minio-admin-complete-guide.md).

			MultipleTargets: true,
		},
		config.HelpKV{
			Key:             config.NotifyRedisSubSys,
			Description:     "publish bucket notifications to Redis datastores",
			MultipleTargets: true,
		},
		config.HelpKV{
			Key:             config.LambdaWebhookSubSys,
			Description:     "manage remote lambda functions",
			MultipleTargets: true,
		},
		config.HelpKV{

notify_postgres       publish bucket notifications to Postgres databases
notify_elasticsearch  publish bucket notifications to Elasticsearch endpoints
notify_redis          publish bucket notifications to Redis datastores
```

> NOTE:
>
> - '\*' at the end of arg means its mandatory.
> - '\*' at the end of the values, means its the default value for the arg.

    public void test_multipleDataStores() {
        TestDataStore dataStore1 = new TestDataStore("Store1");
        TestDataStore2 dataStore2 = new TestDataStore2("Store2");

        dataStoreFactory.add("store1", dataStore1);
        dataStoreFactory.add("store2", dataStore2);

        assertSame(dataStore1, dataStoreFactory.getDataStore("store1"));
        assertSame(dataStore2, dataStoreFactory.getDataStore("store2"));

        IndexUpdateCallback callback = new TestIndexUpdateCallback();

        // Execute on both instances
        dataStore1.store(config, callback, params);
        dataStore2.store(config, callback, params);
        dataStore2.store(config, callback, params);

        // Verify independent operation
        assertEquals(1, store1CallCount.get());
        assertEquals(2, store2CallCount.get());

to use S3 and other S3-compatible object stores such as MinIO. MapReduce workloads typically interact with object stores in the same way they do with HDFS. These workloads rely on HDFS atomic rename functionality to complete writing data to the datastore. Object storage operations are atomic by nature and they do not require/implement rename API. The default S3A committer emulates renames through copy and delete APIs. This interaction pattern causes significant loss of performance because of the...

- cloud.google.com/go/datalabeling: v0.8.4
- cloud.google.com/go/dataplex: v1.14.0
- cloud.google.com/go/dataproc/v2: v2.3.0
- cloud.google.com/go/dataqna: v0.8.4
- cloud.google.com/go/datastore: v1.15.0
- cloud.google.com/go/datastream: v1.10.3
- cloud.google.com/go/deploy: v1.17.0
- cloud.google.com/go/dialogflow: v1.48.1
- cloud.google.com/go/dlp: v1.11.1
- cloud.google.com/go/documentai: v1.23.7

- cloud.google.com/go/datalabeling: v0.8.1 → v0.8.4
- cloud.google.com/go/dataplex: v1.9.0 → v1.14.0
- cloud.google.com/go/dataproc/v2: v2.0.1 → v2.3.0
- cloud.google.com/go/dataqna: v0.8.1 → v0.8.4
- cloud.google.com/go/datastore: v1.13.0 → v1.15.0
- cloud.google.com/go/datastream: v1.10.0 → v1.10.3
- cloud.google.com/go/deploy: v1.13.0 → v1.17.0
- cloud.google.com/go/dialogflow: v1.40.0 → v1.48.1
- cloud.google.com/go/dlp: v1.10.1 → v1.11.1