Is Databricks S3 Commit Service enabled by default if Unity Catalog is not enabled and the compute resources run in our AWS account (classic compute plane)? If not, how can it be enabled?
This service seems to resolve the limitations with multi-cluster write to Delta Lake tables stored in S3 to guarantee ACID transactions.
I understand this Delta Lake limitation can also be resolved by setting up DynamoDB for delta logs, but wanted to confirm if this is still necessary as it seems Databricks has its own solution for this problem.
