Second instance of DynamoDBMapperConfig being created

In updating to 5.1.0, on startup we’re now getting:

Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'dynamoDBMapper' defined in class path resource [{Propriety class details removed}]: Unsatisfied dependency expressed through method 'dynamoDBMapper' parameter 1; nested exception is org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type 'com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMapperConfig' available: expected single matching bean but found 2: dynamoDBMapperConfig,dynamoDB-DynamoDBMapperConfig

We’re creating the DynamoDBMapperConfig as per https://github.com/derjust/spring-data-dynamodb/wiki/Alter-table-name-during-runtime. Looks like something else is also now creating a DynamoDBMapperConfig.

Should these be created now in a different fashion?

[GynnRickerbyNZPost]

Yes, but I need to configure the DynamoDBMapperConfig to specify table name overrides.

The dynamoDB-DynamoDBMapperConfig one is being created internally (and seems didn’t use to be in previous versions), and there’s no obvious new documentation on how to turn it off.

[rratliff]

Like others, I already had a @Bean DynamoDBMapperConfig defined.

For me a combination of removing dynamoDBMapperConfigRef from the @EnableDynamoDBRepositories annotation and also marking my existing DynamoDBMapperConfig bean definition as @Primary seemed to do the trick.