Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature requests for tarsupervoxels #274

Open
3 of 4 tasks
stuarteberg opened this issue Jul 10, 2018 · 3 comments
Open
3 of 4 tasks

Feature requests for tarsupervoxels #274

stuarteberg opened this issue Jul 10, 2018 · 3 comments
Assignees

Comments

@stuarteberg
Copy link
Member

stuarteberg commented Jul 10, 2018

  • 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.

@DocSavage
Copy link
Member

Timestamps are already meaningful. If the backing store can give meaningful timestamps, it will do so and the tar file will have that timestamp.

@DocSavage DocSavage self-assigned this Jul 12, 2018
@stuarteberg
Copy link
Member Author

I edited the list above and put it in priority order.

@DocSavage
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants