-
Notifications
You must be signed in to change notification settings - Fork 12
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
Create an endpoint to trigger asset summary generation #391
Comments
since the summary is at the dandiset level, perhaps:
note that at present any update to metadata should also trigger summarization, perhaps the summary endpoint is better, but it does also need to be triggered on a delay timer (relative to last asset update; preferred) or a cron-job (fallback). however, more generally, we should consider how much of this should be in the api or part of the server workflow. |
Back ref #385 |
Doing a What exactly was the use case for this endpoint? |
relates to #431 as might be providing a workaround for testing if this end-point would cause the task without any delay |
@dchiquito, what's the status on this issue? |
I can see this being useful as way to quickly flush the asset summary queue when running tests. Right now the test has to wait at max 60s for the job to run, which is never a nice thing to do in a test. |
It's possible it might resolve the flaky test issues we've been seeing with asset summary validation #567 (comment) |
Yarik wrote:
Originally posted by @yarikoptic in #389 (comment)
I would recommend the endpoint
PUT /dandisets/{versions__dandiset__pk}/versions/{versions__version}/assets/summary
for this purpose.Design doc: https://github.com/dandi/dandi-api/blob/master/doc/design/scheduled-tasks.md
The text was updated successfully, but these errors were encountered: