Upgrade notes for the forced-id change (#5400)
Add upgrade notes for forced-id
This commit is contained in:
parent
69780a3445
commit
cf3cf2547d
|
@ -1,3 +1,9 @@
|
|||
### Major Database Change
|
||||
|
||||
This release makes performance changes to the database definition in a way that is incompatible with releases before 6.4.
|
||||
Attempting to run version 6.2 or older simultaneously with this release may experience errors when saving new resources.
|
||||
|
||||
### Change Tracking and Subscriptions
|
||||
This release introduces significant a change to the mechanism performing submission of resource modification events
|
||||
to the message broker. Previously, an event would be submitted as part of the synchronous transaction
|
||||
modifying a resource. Synchronous submission yielded responsive publishing with the caveat that events would be dropped
|
||||
|
@ -8,6 +14,7 @@ database upon completion of the transaction and subsequently submitted to the br
|
|||
This new asynchronous submission mechanism will introduce a slight delay in event publishing. It is our view that such
|
||||
delay is largely compensated by the capability to retry submission upon failure which will eliminate event losses.
|
||||
|
||||
### Tag, Security Label, and Profile changes
|
||||
|
||||
There are some potentially breaking changes:
|
||||
* On resource retrieval and before storage, tags, security label and profile collections in resource meta will be
|
||||
|
|
Loading…
Reference in New Issue