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
The Flux KVS keeps track of the "version" of its entries through a "ver" field. We should use this to help determine if a file has changed. If the version of the KVS entry changes, we transfer. Otherwise, we don't.
The text was updated successfully, but these errors were encountered:
The Flux KVS keeps track of the "version" of its entries through a "ver" field. We should use this to help determine if a file has changed. If the version of the KVS entry changes, we transfer. Otherwise, we don't.
Just an FYI, ver in KVS entries probably isn't what you think it is. It's the version of the tree object format that data is stored in. You can see it doesn't get updated in this example ...
>flux kvs put foo=1
>flux kvs get --treeobj foo
{"data":"MQ==","type":"val","ver":1}
>flux kvs put foo=blarg
>flux kvs get --treeobj foo
{"data":"Ymxhcmc=","type":"val","ver":1}
The Flux KVS keeps track of the "version" of its entries through a "ver" field. We should use this to help determine if a file has changed. If the version of the KVS entry changes, we transfer. Otherwise, we don't.
The text was updated successfully, but these errors were encountered: