Make Use Of "authoritative" APIs Optional
Bug #2012402 reported by
Bill Erickson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Committed
|
Wishlist
|
Unassigned |
Bug Description
Evergreen 3.10 / Wishlist
List discussion: http://
Evergreen's "authoritative" APIs are useful in scenarios where Evergreen may read from multiple replicated databases. In practice, this does not happen so much anymore.
The goal of this bug is to make the use of authoritative API's optional in Evergreen, disabled by default. The change will affect ".authoritative" registered APIs and use of the "authoritative" flag in the Angular pcrud service.
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
milestone: | 3.11-beta → 3.12-beta |
Changed in evergreen: | |
assignee: | nobody → Jane Sandberg (sandbergja) |
tags: | added: signedoff |
To post a comment you must log in.
A branch:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp2012402- authoritative- optional
Two main things to look for when testing and the setting is disabled:
1. There should be practically zero open-ils. pcrud.transacti on.begin / open-ils. pcrud.transacti on.rollback calls in the activity log.
2. Authoritative methods should not be wrapped in open-ils. cstore. transaction. begin / open-ils. cstore. transaction. rollback calls in the osrfsys logs.
E.g.
srfsh# request open-ils.actor open-ils. actor.user. opac.vital_ stats.authorita tive "$AUTHTOKEN" 1
--
Includes release notes.