Limitations

Partition specifications cannot be changed after an integration is created. To use a different partitioning strategy, you must create a new integration.

The maximum number of partition columns is limited to 10.

When creating cross-account integrations, Amazon Glue Console has a limitation where it doesn't invoke CreateIntegrationTableProperty API for configuring UnnestSpec and PartitionSpec for target Amazon Glue tables that are hosted in the account where integration does not exist.

Workaround: The CreateIntegrationTableProperty API must be invoked by CX from the account where the target database exists.

If you need to replicate the same source with different schema unnest/partition configurations, it is required to create a new Amazon Glue database for each integration separately. Later invoke CreateIntegrationTableProperty for each table from individual Amazon Glue Database with desired schema unnesting and partitioning configurations.