AWS solutions documentation change
Summary
Updated terminology from 'SPLIT/UNION strategy' to 'split/union routing' and changed references from 'Amazon OpenSearch Serverless collection' to 'Amazon OpenSearch Serverless NextGen collection'.
Security assessment
Changes involve product naming updates and terminology refinement without any security context. No vulnerabilities, security features, or security implications are addressed in the modifications.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/ttm-validate.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/ttm-validate.md index ac87def1f..13e3870bf 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/ttm-validate.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/ttm-validate.md @@ -11 +11 @@ After the transformer has run, confirm that the resulting indexes and mappings o -List the indexes that were created on the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection: +List the indexes that were created on the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless NextGen collection: @@ -21 +21 @@ Then inspect the mapping of a specific index to confirm the types were routed, m -For a `SPLIT` strategy, verify that each former type now appears as its own index (for example, `new_users` and `new_posts`). For a `UNION` strategy, verify that the single target index contains the combined set of fields from all merged types, with no conflicting field definitions. If the mappings do not match your intent, change the transformer configuration and re-run the migration as described in [Apply a changed transformer configuration](./ttm-restart-required.html). +For split routing, verify that each former type now appears as its own index (for example, `new_users` and `new_posts`). For union routing, verify that the single target index contains the combined set of fields from all merged types, with no conflicting field definitions. If the mappings do not match your intent, change the transformer configuration and re-run the migration as described in [Apply a changed transformer configuration](./ttm-restart-required.html).