You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AlterSchema and AlterOption are now persisted in the manifest. It would be better to keep manifest simple (only contains SST file information, sequence number, etc.). And schema modification is related to data, putting them in two separate places may bring some problems.
Proposal
Make manifest only to contain create, drop table, and version edit. The new procedure of altering schema and option is:
trigger flush
persist new schema/option to WAL
update OSS metadata (next PR)
update manifest to include the DDL record
update memory status
A new file that contains "present schema" and "present option" will be persisted to OSS as table's metadata.
Additional context
The text was updated successfully, but these errors were encountered:
Description
AlterSchema
andAlterOption
are now persisted in the manifest. It would be better to keep manifest simple (only contains SST file information, sequence number, etc.). And schema modification is related to data, putting them in two separate places may bring some problems.Proposal
Make manifest only to contain create, drop table, and version edit. The new procedure of altering schema and option is:
A new file that contains "present schema" and "present option" will be persisted to OSS as table's metadata.
Additional context
The text was updated successfully, but these errors were encountered: