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
Apparently people often want to add new columns that are results from the old columns.
Do we want to support adding another column onto an existing castra? We would assume that the new column has the exact same partition structure and number of elements per partition.
The text was updated successfully, but these errors were encountered:
We can do that. Would we need to store which partitions contain what columns? How would we deal with slices that have both partitions that contain a given colunmn and ones that don't? Should we return some kind of NotAvailable instead for the values in the missing column(s)?
The easy case is that we require new columns to exactly match and completely fill the partition structure. This is the common case in pandas workflows but probably not the common case in other timeseries.
Apparently people often want to add new columns that are results from the old columns.
Do we want to support adding another column onto an existing castra? We would assume that the new column has the exact same partition structure and number of elements per partition.
The text was updated successfully, but these errors were encountered: