Do we really want to store all the label columns in every task dataframe even when the task will just have one kind of label?

[mmcdermott]

@EthanSteinberg, should we somehow indicate that the label columns are optional or don't all need to be included? It seems silly that we'll need to make every label dataframe have columns for every kind of task when all but one will be empty.

meds/src/meds/schema.py

Line 58 in 5f87c2f

# Possible values for the label.

[EthanSteinberg]

I'd be open to that, but I'm not sure the best way to do it

[mmcdermott]

I don't think there is a clean way to support it, after googling around a bit. If/when we solve #37 we can integrate this capability in there (e.g., make it so that if you use meds utilities to re-cast and/or validate and/or read your data in the specified schemas, optional columns are enforced and/or cast to the right types if they are present but no issue is raised if they are not?

I also filed apache/arrow#43626 but I don't know if this is in scope or something they'd want on their end.