mirror of
https://github.com/elastic/kibana.git
synced 2025-06-28 11:05:39 -04:00
Part of https://github.com/elastic/kibana/issues/152807 ## Summary Change the way the `update` API of the savedObjects repository works, to stop using ES `update` and perform the update manually instead by fetching the document, applying the update and then re-indexing the whole document. This is required for BWC and version cohabitation reasons, to allow us converting the document to the last known version before applying the update. The retry on conflict behavior is manually performed too, by detecting conflict errors during the `index` calls and performing the whole loop (fetch->migrate->update->index) again. Upserts are done in a similar way, by checking the document's existence first, and then using the `create` API. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: pgayvallet <pierre.gayvallet@elastic.co> |
||
---|---|---|
.. | ||
src | ||
index.ts | ||
jest.config.js | ||
kibana.jsonc | ||
package.json | ||
README.md | ||
tsconfig.json |
@kbn/core-saved-objects-server-internal
This package contains the internal implementation of core's server-side savedObjects service.