feat(api): churn filter modes for admin job events #950
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/admin-logs-processing-api"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds an optional
churnquery param toGET /api/admin/job-events(super-admin):status=failedor explicitjobType)Invalid request(same convention asstatusvalidation)Single branch structure in the SQL construction, no UNION duplication. Degenerate
churn=only&jobType=<run type>short-circuits to an empty page (avoids empty-UNION SQL).Motivation
Admin Logs currently hides all media-processing completions (thumbnail/preview/metadata jobs are churn-excluded), so there is no way to see when a photo was processed. A following web PR adds a Processing section to the Admin Logs tab using
churn=only.Test plan
JobEventsServiceTest: 13/13 green (legacy assertions untouched; +3 new: include mixes sources, only returns exclusively churn worker jobs with all three run tables seeded, invalid modes rejected incl. case/whitespace)JobEventsControllerTest: 5/5 green (+2: param forwarding, MockMvc 400 on invalid churn)rtk ./gradlew :apps:api:compileJava :apps:api:compileTestJavacleanVersion bump 1.21.57.