Consequently, there are few changes/guidelines that are worth pointing out:
Writes are no longer possible to the preexisting tables which were created prior to Seafowl v0.3.x (aka legacy tables).
The only exception are VACUUM and DROP commands, in order to facilitate easier cleanup of legacy tables.
Reading (including time-travel) is still supported for legacy tables.
All newly created tables will be Delta tables, and all functionalities are supported for them as they were for legacy tables (including the full range of DDL & DML statements as before; see the updated docs).
The idea is to enable migration of data from legacy tables to new tables throughout all 0.3.x versions—for instance via CREATE TABLE AS statement where the subquery targets a legacy table.
At some point the legacy tables will be completely phased out, and we'll bump the minor version again (0.4.x versions).
Finally, If you find any problems related to migration or working with new Delta tables please file a new issue or report it in this pinned issue.
As of version 0.3.x Seafowl doesn't use a custom MVCC implementation anymore, but instead relies on delta-rs to accommodate Delta tables for it's new underlying storage layer.
Consequently, there are few changes/guidelines that are worth pointing out:
VACUUMandDROPcommands, in order to facilitate easier cleanup of legacy tables.CREATE TABLE ASstatement where the subquery targets a legacy table.Finally, If you find any problems related to migration or working with new Delta tables please file a new issue or report it in this pinned issue.