-
Type: New Feature
-
Status: Resolved
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: 8.2
-
Fix Version/s: 9.1
-
Component/s: Clustering, Core
-
Epic Link:
-
Impact type:API change
-
Upgrade notes:
-
Sprint:nxFG 9.1.6, nxFG 9.1.7, nxFG 9.1.8, nxFG 9.1.9, nxFG 9.1.10
-
Story Points:5
Having an auto incremented change token on a document on each write operation will help to implement optimistic version control pattern.
It will be also useful to keep Elasticsearch index in sync.
For 9.1 this feature is disabled by default. Running tests with nuxeo.test.changetoken.enabled=true will activate it.
- is duplicated by
-
NXP-12281 Implement a new cache key (change token)
- Resolved
- is required by
-
NXP-19283 Possible race condition on Elasticsearch indexing command
- Resolved
-
NXP-19542 Fix TestSQLBackendArrayColumns.tes​tParallelArrayUpdate on PostgreSQL
- Resolved
-
NXP-22127 Fix spurious ConcurrentUpdateException
- Resolved
-
NXP-22019 Improve internal change token for optimistic locking
- Resolved
-
NXP-22259 Internal document version/timestamp (system change token)
- Resolved
-
NXDRIVE-454 Compare client hash and serverside one on update to avoid overwrite
- Open
-
NXP-16144 Add a system modification field in all documents
- Resolved