A Collection can specify the variables that will be updated using the Collection.update() method. This prevents zcollection having to guess the updated variables by launching the callback over the first partition. This is very useful if the callback needs heavy auxiliary data that can only be loaded on a dask worker.
A View cannot use the same 'variables' and cannot bypass this variables inference step. It would be a great for View.update() to have the same behavior as the Collection
A Collection can specify the variables that will be updated using the Collection.update() method. This prevents zcollection having to guess the updated variables by launching the callback over the first partition. This is very useful if the callback needs heavy auxiliary data that can only be loaded on a dask worker.
A View cannot use the same 'variables' and cannot bypass this variables inference step. It would be a great for View.update() to have the same behavior as the Collection