Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Tickets:

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyCIRC-573
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUICIRC-736

...

This endpoint would follow a similar design structure as to those described here:

References:

...

The existing renewal process is too slow. However, having a batch perform one operation at a time has also proven problematic. The suggested design is to have a batch process renewals and when it has accrued a designated number of successful renewals, submit them to the storage module as a sub-batch.
The business logic can perform a pre-process where it checks to see if any of the renewals would fail for business logic reasons. Hold all renewals that pass the business logic test and then when the sub-batch size is reached make a request to the storage module using the sub-batch. This is potentially problematic in that if something fails in the sub-batch the entire sub-batch might be considered a failure. If this is undesired then a sub-batch size of 1 must be used. The size of the sub-batch will need to be determined, and could be configurable or a property specified in the request if desired. This approach would require a bulk update endpoint to be available from the storage module.

...

The "error" represents technical failures, such as an SQL failure.


Image RemovedImage Added

SVGJPG: circ-573.svgjpg

Example Multi-update SQL

Postgresql can update multiple rows in a single statement, such as:

...

Ticket

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLIO-1156
 describes active work to in this regard that might provide a way to do the above or something similar.