Remove SavedObjects missing index error handling and associated error UI. #55667
Labels
chore
Feature:Legacy Removal
Issues related to removing legacy Kibana
Feature:New Platform
Feature:Saved Objects
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
From what I can tell, before we had Saved Object migrations, it was possible for the SavedObjectsClient/repository to get a NotFound error when creating an Saved Object because the
.kibana
index doesn't yet exist and ES's auto create index setting was disabled. Since the migration framework handles creating the index, this would no longer be a common occurrence and would only happen in exceptional circumstances like if someone manually deleted their indexes. Simply throwing the rawNotFound
error from ES is probably sufficient.kibana/src/core/server/saved_objects/service/lib/repository.ts
Lines 267 to 270 in bbf703a
kibana/src/core/public/saved_objects/saved_objects_client.ts
Lines 32 to 37 in 9d3d3cd
kibana/src/core/server/saved_objects/types.ts
Lines 218 to 225 in 054ec70
kibana/src/core/server/saved_objects/service/lib/errors.ts
Lines 167 to 177 in 260d907
https://github.com/elastic/kibana/blob/ea9721ad13d1496ebb96dfc6647699c21967fb91/src/legacy/ui/public/error_auto_create_index/error_auto_create_index.ts
The text was updated successfully, but these errors were encountered: