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
As discussed, it would be great if files in the returned tarballs have a meaningful timestamp of some sort, if possible.
It would be nice if the .../tarfile option supported the HEAD method, or some other means of querying for the existence of a body (or subset) within the instance.
Some endpoint (e.g. .../exists) to ask "which of the following supervoxel files already exist?"
Someday: An equivalent to the /keys endpoint, which returns the complete list of all supervoxel files that exist in the filestore. This is tricky because it will be over ~200M items. Without some sort of pagination, it would be a ~2GB response.
The text was updated successfully, but these errors were encountered:
@stuarteberg For the /keys endpoint, I'll stream out N keys where N is some large limit. You can then do GET /keys?start=lastkeygiven where lastkeygiven is the very last key returned, and it will do another batch. If the data returned is not complete, it will return a 206 HTTP status code (partial content) so you know further queries are required.
As discussed, it would be great if files in the returned tarballs have a meaningful timestamp of some sort, if possible.
It would be nice if the
.../tarfile
option supported theHEAD
method, or some other means of querying for the existence of a body (or subset) within the instance.Some endpoint (e.g.
.../exists
) to ask "which of the following supervoxel files already exist?"Someday: An equivalent to the
/keys
endpoint, which returns the complete list of all supervoxel files that exist in the filestore. This is tricky because it will be over ~200M items. Without some sort of pagination, it would be a ~2GB response.The text was updated successfully, but these errors were encountered: