AWS solutions documentation change
Summary
Expanded documentation about automatic transformations during metadata migration to include vector-compatibility adjustments and analysis-component compatibility rules
Security assessment
The changes describe functional enhancements to migration transformations (vector compatibility and analysis components) without any mention of security vulnerabilities, patches, or security features. Updates focus on compatibility adjustments between Elasticsearch and OpenSearch versions.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/tft-built-in.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/tft-built-in.md index f6324e763..5eea4a293 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/tft-built-in.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/tft-built-in.md @@ -9 +9 @@ -Migration Assistant applies the following field-type transformations automatically during metadata migration. You do not need to configure or invoke them — they run as part of the Metadata Migration phase whenever the source and target engine versions require them. Each built-in transformation has its own detail page that explains the source and target types, the properties that influence the result, and how to confirm the outcome on the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection: +Migration Assistant applies the following field-type and vector-compatibility transformations automatically during metadata migration. You do not need to configure or invoke them — they run as part of the Metadata Migration phase whenever the source and target engine versions require them: @@ -15 +15,3 @@ Migration Assistant applies the following field-type transformations automatical - * **`dense_vector` to `knn_vector` ** — Converts `dense_vector` (Elasticsearch 7.x) to `knn_vector` with appropriate similarity mappings and HNSW algorithm parameters, including additional vector compatibility adjustments for newer Amazon OpenSearch Service and Amazon OpenSearch Serverless targets. See [Transform dense_vector fields to knn_vector](./transform-dense-vector-knn.html). + * **`dense_vector` to `knn_vector` ** — Converts `dense_vector` (Elasticsearch 7.x) to `knn_vector` with appropriate similarity mappings and HNSW algorithm parameters, including additional vector compatibility adjustments for newer Amazon OpenSearch Service and Amazon OpenSearch Serverless NextGen targets. See [Transform dense_vector fields to knn_vector](./transform-dense-vector-knn.html). + + * **`knn_vector` compatibility** — Lifts legacy `index.knn.*` build parameters into field-level method configuration, converts `nmslib` engines to `faiss` for OpenSearch 3.x targets, and rewrites incompatible `knn_vector` definitions to Faiss HNSW for Amazon OpenSearch Serverless NextGen. @@ -22 +24 @@ Migration Assistant applies the following field-type transformations automatical -The built-in transformations cover the common version-upgrade cases. If your source contains field types that none of these transformations address — for example a custom or third-party field type, or a type whose mapping you need to reshape in a way the defaults do not — supply a custom transformer as described in the next section. +The built-in transformations cover the common version-upgrade cases. Metadata migration also applies analysis-component compatibility rules for analyzer, tokenizer, char-filter, and token-filter names that changed between source and target versions. If your source contains field types or analysis components that none of these transformations address — for example a custom or third-party field type, or a type whose mapping you need to reshape in a way the defaults do not — supply a custom transformer as described in the next section.