Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Epic Link:
-
Sprint:DB_S21_12
-
Team:Data Access and Database
-
Urgent?:No
Description
The bug
The big is caused by the incomplete implementation of the feature explained in
DM-26101.
The worker-side ingest service that processes requests over the proprietary binary protocol (BOOST ASIO, Google Protobuf) is not recording contributions in the persistent state of the Replication/System when processing the request. This excludes contributions from being properly handled by the system at the transaction commit time and the catalog publishing time. Other algorithms (see DM-28603) relying on the persistent records for the contributions made during the transactions are also affected by the problem.
The second improvement is to allow passing back to a client the retry_allowed flag that's meant to indicate if a failed contribution could be retried.
NOTE: the file contributions will be recorded with file URLs adhering to this scheme https://en.wikipedia.org/wiki/File_URI_scheme
PR: https://github.com/lsst/qserv/pull/621