Please note that currently, Redshift does not Support the 'Time Travel' feature that exists in the Delta Tables.
Further, as you are aware, every time changes are made in the Delta Tables, they create new parquet files which contain the latest data. Thus, we are required to generate a new manifest file in order to get a consistent snapshot of the data stored in the table. That is how the Time Travel functionality works, i.e. it is able to look back through these older parquet files and see the previous values.
Considering the above, we can use a workaround where you can create a new table each time the data changes, that is, once the new parquet files are created and the manifest is updated and you can create an external table at the time using the specific manifest file. This would require that you maintain the copies of all the manifest files as well as all of the parquet files, doing so would allow you to do something similar to Delta Tables time travel but in Redshift
I do hope, that the above workaround can point you in the right direction or provide more information as to how you could possibly implement something similar as well as determine if it would be suitable for your use case.
- asked 3 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 6 days ago
- AWS OFFICIALUpdated 2 months ago
- EXPERTpublished 5 months ago
- EXPERTpublished 4 months ago