[BWC] Verify impact for type and include_type_name no longer being supported
#1290
Comments
7 tasks
|
Here is the meta issue regarding type removal from OpenSearch engine. A high level changes done as part of type removal |
|
Will also now need verify impact of this as well: opensearch-project/OpenSearch#2397 Removal of |
kavilla
changed the title
type no longer being supportedtype and include_type_name no longer being supported
21 tasks
67 tasks
|
Assigning to @kavilla since it's labeled 2.0, just so we don't lose it. |
|
@kavilla : Is there anything pending here ? |
7 tasks
kavilla
pushed a commit
that referenced
this issue
Jun 24, 2022
…meout (#1788) As part of the meta issue opensearch-project/OpenSearch#2589 to track the plan and progress of applying inclusive naming across OpenSearch Repositories. Includes updates from generation with the removal of type. Issues: #1685 #1290 Signed-off-by: Manasvini B Suryanarayana <manasvis@amazon.com>
opensearch-trigger-bot bot
pushed a commit
that referenced
this issue
Jun 24, 2022
…meout (#1788) As part of the meta issue opensearch-project/OpenSearch#2589 to track the plan and progress of applying inclusive naming across OpenSearch Repositories. Includes updates from generation with the removal of type. Issues: #1685 #1290 Signed-off-by: Manasvini B Suryanarayana <manasvis@amazon.com> (cherry picked from commit c659831)
kavilla
pushed a commit
that referenced
this issue
Jun 24, 2022
…meout (#1788) (#1794) As part of the meta issue opensearch-project/OpenSearch#2589 to track the plan and progress of applying inclusive naming across OpenSearch Repositories. Includes updates from generation with the removal of type. Issues: #1685 #1290 Signed-off-by: Manasvini B Suryanarayana <manasvis@amazon.com> (cherry picked from commit c659831) Co-authored-by: Manasvini B Suryanarayana <manasvis@amazon.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We will need to verify if the removal of the
typehere: opensearch-project/OpenSearch#2239 has impact to backwards compatibility for OpenSearch Dashboards.If it doesn't then we can close this issue. If it does, does it require a migration script on startup?
If we it does require a migration script then we will take note of a migration path and any documents to ensure that OpenSearch Dashboards and the compatible OpenSearch. If it's somewhat compatible then we will have to make sure if a legacy version goes from 6.8 to OpenSearch Dashboards does not fail to start. Or we will need to update documents.
If we discover no BWC issues than the commented out code added here: #1289 can be removed.
The text was updated successfully, but these errors were encountered: