No reloading after saving
Open
@giovp is already working on this.
Since Jun 14, 2023.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
- Currently when
write()is called, the data is re-read to be made lazy. We have to prevent this because it leads to undesired behavior when one wants to overwrite the data (i.e. data that was in memory should remain in-memory unless the user explicitly wants to load it lazily). - In doing this we need to warn the user that the in-memory object may be not performant (especially relevant if calling
Interactive()to the output of functions likexenium()). So we should add a check that controls if the data is lazy and backed by a.zarror.parquetstorage (we already have the code for that (see the teststest_io_and_lazy_loading_points()andtest_io_and_lazy_loading_raster()), if it is not backed, then when callingInteractive()we should display this warning.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.