Make artifact and media metadata first-class server records

Artifact and media metadata were previously reconstructed from job result
refs and JSON sidecar files. This change regularizes metadata into SQLite,
keeps filesystem blobs in place, and preserves backward compatibility via
lazy fallback and backfill from existing job refs and JSON metadata.

Constraint: Blob storage remains on the local filesystem in this phase
Rejected: Migrate blobs into SQLite | larger scope and worse operational profile for current media sizes
Rejected: Hard cutover without fallback | unsafe for historical data already on the test server
Confidence: medium
Scope-risk: moderate
Directive: Treat SQLite as the metadata source of truth; JSON sidecars are compatibility fallback only
Tested: go test ./...; deployed to test server 101.42.99.35; verified /v1/artifacts, /v1/artifacts/:id, signed media URL 200, unsigned content 401
Not-tested: Full historical backfill sweep over all existing artifact rows under production-sized data volume
This commit is contained in:
wtgoku
2026-04-18 23:06:34 +08:00
parent 07fd1ad0a7
commit d0318292c1
12 changed files with 1303 additions and 75 deletions
+11
View File
@@ -25,3 +25,14 @@ type RouteRepository interface {
SetRoute(projectID, routeKey, modelID string) error
UnsetRoute(projectID, routeKey string) error
}
type MediaRepository interface {
UpsertMedia(record mediaRecord) error
GetMedia(mediaID string) (*mediaRecord, bool, error)
}
type ArtifactRepository interface {
UpsertArtifacts(userID, projectID string, items []artifact) error
GetArtifact(userID, artifactID string) (*artifact, resultRef, bool, error)
ListArtifacts(userID, projectID, jobID string, limit, offset int) ([]artifact, int, error)
}