Since last week, we have been hit by the following error: SQL_SCHEMA_MISMATCH_ERROR: Timestamp with timezone types are not supported. Incorrect Column Type at Index 1 for Column 'tested_at' with DataprepLogicalType Date.
We’ve identified that recreating datasets in the new DataPrep editor resolves the issue. However, manually migrating all our datasets would require a massive amount of effort and time, making this approach highly inefficient for our team.
Furthermore, we are completely blocked on datasets that use geospatial fields, as the new editor does not yet support them.
Given the high volume of datasets involved, is there an alternative solution or a fix at the account level that doesn’t require us to manually recreate every dataset? We need a way to restore functionality without this significant operational overhead.
Hope everything is well with you! I would recommend trying to see if you can convert the timestamps to a Quick supported format. As of now, I do not believe there is an account fix that can be done for this action. Just to make sure though, I would definitely recommend creating a support ticket with AWS Support, as they might be able to guide you in this issue along with the geospatial fields.
Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.