Changes to Container Information Overrides
Customers that have both a default container, and a message container extractor configured will be affected by this update.
In version 3.1 and under, when a default container and a message container extractor are both configured, the container information is not overwritten by the message container extractor and falls back to the configured default container. The expected outcome is that the container information sourced from the message extractor overrides the default container configured.
From version 3.2 and over, the message container extractor correctly overrides the configured default container information.
Impact
As a result of the above issue, customers may be unintentionally relying on the use of the default container over the configured message container extractor.
Solution
Affected customers should perform one of the below options prior to updating to version 3.2:
- Customers can remove the configured message container extractor and only rely on the default container.
- Customers can update their message container extractor to use the same container specified as the default container.
- Customers can migrate relevant records from the default container to the container specified in the message container extractor. This option may require changing the container partition key.