- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 03:02 AM
For example there is a table called "cars", if I remove the table from DLT pipeline and drop the table from catalogue. Now if I change the schema of the table, and create the table again using the same table name "cars" through the same pipeline, Why I am getting schema mismatched error?
Why it didn't remove the schema, is there any other files that we need to be aware of in the backend which doesn't get deleted automatically?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 03:05 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 03:15 AM
It does tell me to try full refresh in the error. I haven't changed schema evolution, it is taking the default settings.
By full refresh do you mean to do Spark.Read instead of Spark.ReadStream? (Just to add I have tried doing Spark.Read but that creates a materialised view)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 03:20 AM
When executing the pipeline, click Full Refresh, which will clear the old checkpoints/schemas. In the future, please share the code snippets, too.
~
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 09:48 AM
Thanks @gchandra , "full refresh all" worked.
Does "Is schema evolution made true?" need to be added through the code or somewhere else in DLT?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 10:02 AM