Very dirty test to simulate multiple Atlas clients deleting and creating tables. It's not clear that our internal clients actually do this, but it does at least appear to highlight a concurrency problem within Atlas, even with the in-memory store.
Fixing the break likely requires ensuring that the KvTableMappingService is concurrency-safe.
What do the change types mean?
- `feature`: A new feature of the service.
- `improvement`: An incremental improvement in the functionality or operation of the service.
- `fix`: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
- `break`: Has the potential to break consumers of this service's API, inclusive of both Palantir services
and external consumers of the service's API (e.g. customer-written software or integrations).
- `deprecation`: Advertises the intention to remove service functionality without any change to the
operation of the service itself.
- `manualTask`: Requires the possibility of manual intervention (running a script, eyeballing configuration,
performing database surgery, ...) at the time of upgrade for it to succeed.
- `migration`: A fully automatic upgrade migration task with no engineer input required.
_Note: only one type should be chosen._
How are new versions calculated?
- ❗The `break` and `manual task` changelog types will result in a major release!
- 🐛 The `fix` changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
- ✨ All others will result in a minor version release.
Very dirty test to simulate multiple Atlas clients deleting and creating tables. It's not clear that our internal clients actually do this, but it does at least appear to highlight a concurrency problem within Atlas, even with the in-memory store.
Fixing the break likely requires ensuring that the
KvTableMappingService
is concurrency-safe.