[PROPOSAL] Deprecate and remove OpenDistro APIs/properties

[dlvenable]

What kind of business use case are you trying to solve? What are your requirements?

As a user of OpenSearch, I'd like to know when I need to migrate away from old APIs and properties that have opendistro in them.

What is the problem? What is preventing you from meeting the requirements?

There are some APIs and properties from OpenDistro which users can use to support both OpenSearch 1.x and Elasticsearch 7.x. This is helpful for developers who are writing code against OpenSearch APIs.

Some example APIs:

• /_opendistro/_ism/policies/
• /_opendistro/_ism/explain/

Some example properties:

• opendistro.index_state_management.enabled
• opendistro.index_state_management.policy_id
• opendistro.index_state_management.rollover_alias

What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?

• Provide clear migration documentation for all opendistro APIs and properties.
• Remove the properties in the desired version.

What are your assumptions or prerequisites?

N/A

What are remaining open questions?

What is the best major version to remove these in? Keeping them does help client developers support more versions. But, removing them can clean-up the code and possibly help make progress on valuable features.

[saratvemulapalli]

@dlvenable thanks for the issue, could you open up issues on all OpenSearch plugins?
You could use Meta[1]

[1] https://github.com/opensearch-project/opensearch-plugins/blob/main/META.md#create-an-issue-in-all-plugin-repos