Dataset with id: de54b108-bdac-4371-ab96-d74649d17c75 is not eligible for incremental refresh. Configure Incremental refresh correctly.
Could you please advise me on how to resolve this issue?
I would like to know the correct configuration for enabling incremental refresh for this dataset.
What is the Data Source (Amazon S3, RDS or anything else)?
Some things to check -
Does the data source have a valid primary key and is incremental refresh supported on it? Additional configuration may be needed if incremental refresh is not supported.
Check if ‘Enable incremental refresh’ setting is turned on in the datasets page.
If the size of the dataset is too large, incremental refresh may not work.
Thanks!
Incremental refresh was working fine when I used a single table.
However, after I joined two tables (both having timestamp fields) to create a new dataset, incremental refresh stopped working and I received the error.
Is incremental refresh not supported for datasets created by joining multiple tables in Athena?
Incremental refresh is supported for datasets created by joining multiple tables in Athena.
Issue may be due to:
Timestamp Field Conflict: When joining two tables with timestamp fields, Athena might struggle to determine which timestamp field to use for tracking changes.
Lack of Unique Identifier: If the joined tables do not have a unique identifier, Athena might not be able to track changes correctly.
Recommendations:
Ensure both tables have Timestamp fields with same data type and format
Add a unique identifier column to each table if not already present.
Explicitly specify which Timestamp field to use for incremental refresh when creating the dataset.
Hi @InseokSeo,
Since we have not heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community.