-
Notifications
You must be signed in to change notification settings - Fork 1
feat(transfer): support MCAP-only scanning and upload readiness #97
Copy link
Copy link
Closed
Labels
area:metadataEpisode metadata, provenance, and schema completenessEpisode metadata, provenance, and schema completenessarea:uploadUpload queue, transfer, and sync workflowsUpload queue, transfer, and sync workflowscppC++ codeC++ codecross-repo:keystoneRequires coordination with archebase/keystoneRequires coordination with archebase/keystoneenhancementNew feature or requestNew feature or requestpriority:p1High priority for production operationsHigh priority for production operations
Metadata
Metadata
Assignees
Labels
area:metadataEpisode metadata, provenance, and schema completenessEpisode metadata, provenance, and schema completenessarea:uploadUpload queue, transfer, and sync workflowsUpload queue, transfer, and sync workflowscppC++ codeC++ codecross-repo:keystoneRequires coordination with archebase/keystoneRequires coordination with archebase/keystoneenhancementNew feature or requestNew feature or requestpriority:p1High priority for production operationsHigh priority for production operations
Type
Fields
Give feedbackNo fields configured for issues without a type.
Context
axon_transfercurrently uses the presence of a matching JSON sidecar as the default signal that an MCAP recording is finalized and ready to upload. Once sidecar JSON is optional, transfer scanning needs a completion signal that does not depend on a.jsonfile.Scope
.donemarker, SQLite state, or atomic final filename convention.require_json_sidecardeployments.Acceptance Criteria
require_json_sidecarbehavior.Depends On
Related