SavedObject enhancements for CM

[mattapperson]

We would love to used SavedObjects API in CM so as to take advantage of things like spaces, however a number of issues, sole larger and some smaller, prevent us from doing this just yet. The currently known issues are:

• SOs dont scale past querying where over 10k documents are returned at once or by pages * page size due to index.max_result_window. We can work around this for now, but in practice we would like to be able to page results up to 100s of thousands
• SOs can only query with AND operators and we need and, and or in the same query (critical)
• SOs dont support KQL bar (as far as I can tell, if true, this is also critical) SavedObjects KQL support: remove dependency on IndexPatterns #47012
• SOs need to migrate 100s of thousands of docs (critical)
• SO migrations need to be able to split a document into two (second document could potentially be a new type) Allow migrations to split documents into new document type #26602
• SOs need to support indexes other then .kibana (most critical) Add multiple index support to saved objects #35747

[rudolf]

Can you explain "SOs need to split documents into new types" ?

[mattapperson]

Right now I might have a SO of type “user” with fields defined for it.
But one of those fields was a json string, the contents of I now want to be its own document. Migrations currently does not allow for doing this

[rudolf]

thanks, I updated the description to help me remember :)

[rudolf]

@mattapperson I've updated the description after KQL support was merged, I believe this would also solve the following item?

SOs can only query with AND operators and we need and, and or in the same query (critical)

I also marked off and linked to your custom saved objects index PR.

[mattapperson]

It does thank you!

[rudolf]

Closing as this is no longer a requirement.