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

labelmap POST /blocks behavior w.r.t. the label index #291

Open
stuarteberg opened this issue Oct 4, 2018 · 0 comments
Open

labelmap POST /blocks behavior w.r.t. the label index #291

stuarteberg opened this issue Oct 4, 2018 · 0 comments
Assignees
Labels

Comments

@stuarteberg
Copy link
Member

stuarteberg commented Oct 4, 2018

(Summarizing a brief in-person discussion.)

We need to review the behavior of POST /blocks and POST /raw for labelmap instances with respect to the label index and the kafka log.

  1. In general, do we intend to support those endpoints for labelmap instances (beyond the initial ingestion phase)? Currently, POST /blocks does NOT update the label index appropriately, and neither does POST /raw.

  2. If so, how should we track supervoxel/body provenance in such cases? Without the above endpoints, supervoxels can only appear/disappear via /split or /split-supervoxel, which are logged to kafka. Similarly, bodies can only appear via /cleave and disappear via /merge. But if we permit the above POST endpoints, then supervoxels and bodies can disappear without a trace in the kafka log. We should define new kafka messages to handle these cases.

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

No branches or pull requests

2 participants