Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new columns? #29

Open
mrocklin opened this issue Jul 31, 2015 · 3 comments
Open

Add new columns? #29

mrocklin opened this issue Jul 31, 2015 · 3 comments

Comments

@mrocklin
Copy link
Member

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.

@esc
Copy link
Contributor

esc commented Aug 8, 2015

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)?

@mrocklin
Copy link
Member Author

mrocklin commented Aug 8, 2015

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.

@esc
Copy link
Contributor

esc commented Aug 8, 2015

Easy case first sounds good, it would be sort-of a concat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants