@kapa.ai With airbyte cloud and databricks destination, is there a way to automatically add clustering keys to the output table?

The knowledge sources do not mention any option to define or automatically add clustering keys for tables created by the Databricks Lakehouse destination. The Databricks destination docs describe how to configure the connector (hostname, HTTP path, Unity Catalog database, auth, schema, etc.) and what extra metadata columns are added, but there is no reference to clustering, indexing, or table-level physical design options you can control from Airbyte Cloud. [[Databricks dest](https://docs.airbyte.com/integrations/destinations/databricks)] Based on the available documentation, there is no documented way in Airbyte Cloud today to automatically set clustering keys on the Databricks destination tables. You would need to manage any clustering/optimization directly in Databricks (e.g., via separate SQL/maintenance jobs) outside of what is described here.