Issue
When performing an incremental extract refresh using a non-unique key (e.g. date), the job succeeds however the extracted data may be incorrect.
When performing an incremental extract refresh using a non-unique key (e.g. date), the job succeeds however the extracted data may be incorrect.
Follow the steps under the Run a refresh on Tableau Cloud section in our Product Help.
Follow the steps under the Run a refresh on Tableau Cloud section in our Product Help
Disable the NonUniqueIncrementalKey feature flag by taking the following steps:
Windows:
Mac:
Open a terminal window
Run:
If you do not have sudo permission, run the following command
Run the below TSM commands to disable the non-unique incremental key feature.
tsm configuration set -k features.NonUniqueIncrementalKey -v false
tsm pending-changes apply
See tsm Command Line Reference for more information.
Regarding Non-Unique key, “unique” means the source database must have a uniqueness constraint for the column. If it doesn’t, then the extract may be impacted, regardless of whether every row is unique or not.
The window of time in which incremental refreshes were affected on Tableau Cloud, was from the time that the pod was upgraded to version 2023.1 until 5:45 PM UTC on March 21, 2023. Content affected during this window must use the options from the resolution section to address the issue.
POD |
2023.1 UPGRADE |
eu-west-1a |
2/21/2023 10:50 PM UTC - 2/23/2023 12:00 AM UTC 3/1/2023 9:00 PM UTC |
10az, us-west-2b, prod-uk-a, prod-ca-a |
3/8/2023 12:00 AM |
prod-apsoutheast-a, prod-apnortheast-a |
3/13/2023 3:00 9M UTC |
10ay, us-east-1, dub01, prod-useast-a, prod-useast-b |
3/13/2023 11:00 PM UTC |