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
APPEND to an existing table. The Arrow Table will have to conform to the existing Table Descriptor and Data Managers.
UPDATE an existing table. The Arrow Table will have to conform to the existing Table Descriptor and Data Managers. New Table Descriptor and Data Manager entries must be synthesised for any columns that are not present on the CASA Table.
From experience with dask-ms, (3) is the most complex case. I think this should be low priority unless there is a demonstrably useful case for returning to the CTDS format.
The text was updated successfully, but these errors were encountered:
Initially only conversion of CASA Tables to Arrow Tables is supported. It may be worth supporting CASA Table writes.
There are three general cases to consider:
CREATE a new table. Table Descriptors and Data Managers must be synthesised from the schema of the supplied Arrow Table and the MSv2.0 spec.
APPEND to an existing table. The Arrow Table will have to conform to the existing Table Descriptor and Data Managers.
UPDATE an existing table. The Arrow Table will have to conform to the existing Table Descriptor and Data Managers. New Table Descriptor and Data Manager entries must be synthesised for any columns that are not present on the CASA Table.
From experience with dask-ms, (3) is the most complex case. I think this should be low priority unless there is a demonstrably useful case for returning to the CTDS format.
The text was updated successfully, but these errors were encountered: