Snapshots as archives improvements

[ywelsch]

This issue is to capture future enhancements for snapshots as archives (#81210).

The project still requires users during a major version upgrade to take extra steps: snapshot the data that can't make it to the next major version, and delete it from the cluster, then do the upgrade, and finally restore / mount the data against as legacy indices. This could be automatized, making it easier for user to go through a major version upgrade. Some steps could include providing an ILM integration so that indices can be transitioned to an "archive" where they will be limited to doc-values / source-only access, as well as allow users to upgrade to the next major version by auto-converting indices to archival. Other enhancement tasks:

• [ ] auto-map source-only indices (from source-only snapshot repositories) automatically as runtime fields
• [ ] better error messages on nested fields
• [ ] running queries on _id or disallowing it

[elasticmachine]

Pinging @elastic/es-search (Team:Search)

[elasticsearchmachine]

Pinging @elastic/es-search-foundations (Team:Search Foundations)