Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

This page documents settings for configuring an Kafka service as a target for Bucket Notifications. See Publish Events to Kafka for a tutorial on using these settings. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

This page covers settings that control root (superuser) access for the MinIO AIStor process. The root user has complete access and permissions to perform operations on the MinIO AIStor deployment. Root User and Root Password are required even if you use the MinIO Key Encryption Service or other key management utility. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the MinIO AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

The mc table view create command creates a new Iceberg view on an MinIO AIStor cluster. Views are virtual tables defined by SQL queries. You can provide multiple SQL representations with different dialects for cross-engine compatibility. Example The following command creates a view named monthly_sales in the prod namespace of the analytics warehouse on the myaistor MinIO AIStor cluster:

The mc table namespace remove command deletes an Iceberg namespace from a warehouse on an MinIO AIStor cluster. A namespace must be empty before it can be removed. Remove all tables and views in the namespace before deleting it. Example The following command removes the prod namespace from the analytics warehouse on the myaistor MinIO AIStor cluster:

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

The mc support top locks command lists active locks on an MinIO AIStor deployment. By default, the command outputs a table showing the age of each lock, type of lock, owner, and resource: Since Type Owner Resource 13 hours ago WRITE 10.68.100.18:9000 .minio.sys/leader.lock 13 hours ago WRITE 10.68.100.18:9000 .minio.sys/callhome/runCallhome.lock 13 hours ago WRITE 10.68.100.23:9000 .minio.sys/new-drive-healing/0/0 Use --watch to monitor locks in real-time with an interactive TUI. Syntax Example The following command displays the active locks on the alias myaistor.

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

This page documents settings for enabling external identity management using an Active Directory or LDAP service. See Configure MinIO AIStor for Authentication using Active Directory / LDAP for a tutorial on using these settings. MinIO AIStor supports configuring multiple LDAP providers. You provide a unique name for each provider configuration, allowing you to integrate with different directory services or organizational units within your environment. MinIO recommends using the mc idp ldap commands for LDAP management operations. These commands offer better validation and additional features, while providing the same settings as the identity_ldap configuration key. The identity_ldap configuration settings remains available for existing scripts and other tools.