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
There is quite a bit of confusion about what mutable means, what behavior it limits, etc., but one of the biggest causes for confusion is that mutable and streaming do not appear to be mutually exclusive. For that reason make_mutable should really take a parameter for streaming that will also ensure the returned MutableDataset has the desired streaming-ness.
The text was updated successfully, but these errors were encountered:
ds.edit(streaming="no") seems to get us around this for now but an integrated solution for make_mutable would be much appreciated, as well as a FAQ/explanation about exactly what mutable and streaming, as states, are, are not and how they relate to each other.
There is a connection here that also needs to hook in for replace_from_csv, which internally needs to manage these states for the user based on whatever state it is before replace_from_csv is called. @xbito i'll take your advice about what additional ticket might be needed there.
scrunch/scrunch/datasets.py
Lines 992 to 994 in 4cfc508
There is quite a bit of confusion about what mutable means, what behavior it limits, etc., but one of the biggest causes for confusion is that mutable and streaming do not appear to be mutually exclusive. For that reason
make_mutable
should really take a parameter forstreaming
that will also ensure the returnedMutableDataset
has the desired streaming-ness.The text was updated successfully, but these errors were encountered: