feat(api): one processing operation per upload session #1533
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/upload-session-operations"
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
Replaces the single aggregated
upload-batchoperation in /api/processing-summary with one operation per upload session (upload:<sessionId>). Top-level activity elements are now the user's concrete upload runs: a 300k-file backup = one card; a later restarted backup = a new card.Changes
ProcessingSummary.Operation: new optionalsessionId+lanes(per-session lane breakdown: finished/total/processing/failed per process type), both NON_NULL — reprocess ops keep today's JSON byte-for-byteProcessingSummaryService: aggregateupload-batchop removed; per-session ops use the exact legacy batch selection rule (notified watermark, 7-day window, cancelled/failed/expired excluded); newest 10 sessions, grouped lane queries (bounded)processedTotal= terminal upload-file statuses (documented media-based approximation, same formula as the web session cards);finishedCountcounts jobs (retries can exceed totalCount)recentBatchkept for backward compatibility (old web builds)Deployment note
Web consumes this contract in feat/activity-cards-vB. Contract is additive (old web ignores sessionId/lanes; new web falls back to legacy aggregate when absent) — atomic compose deploy, no coordination gap.
Part of the activity-feed redesign (design variant B, user-approved).