OpenSearch から Zilliz Cloud への移行
このトピックでは、OpenSearch から移行する際のデータ型マッピング、コレクション命名規則、および考慮事項について説明します。
前提条件
OpenSearch から Zilliz Cloud への移行を開始する前に、以下の要件を満たしていることを確認してください。
OpenSearch の要件
Requirement | Details |
|---|---|
ネットワーク access | Source OpenSearch cluster must be accessible from the public internet |
Authentication | Valid cluster endpoint, username, and password with necessary permissions |
Vector field requirement | Each source index must contain at least one k-NN vector field |
データ availability | Source indexes must contain data. Empty indexes cannot be migrated. |
Zilliz Cloud の要件
Requirement | Details |
|---|---|
User role | 組織オーナー or プロジェクト管理者 |
Cluster capacity | Sufficient storage and compute resources (use the CU calculator to estimate CU size) |
ネットワーク access | Add Zilliz Cloud IPs to allowlists if using network restrictions |
データ型マッピング
以下の表は、OpenSearch のフィールド型が Zilliz Cloud のフィールド型にどのようにマッピングされるかを要約したものであり、カスタマイズオプションの詳細も含んでいます。
OpenSearch Field Type | Zilliz Cloud Field Type | Description |
|---|---|---|
Primary key | Primary key | OpenSearch's primary key (_id) is automatically mapped as the primary key in Zilliz Cloud. When migrating data, you can enable 自動ID. However, if you do so, the original primary key values from your source table will be discarded. |
FLOAT_VECTOR | The Vector dimensions remain unchanged. | |
Not supported | エイリアス fields are サポートされていません. | |
VARCHAR | Binary data is stored as a string on Zilliz Cloud. | |
| INT8 | Directly mapped. |
| DOUBLE | Directly mapped. |
| FLOAT | Directly mapped. |
| FLOAT | Mapped to |
| INT32 | Directly mapped. |
| INT64 | Directly mapped. |
| INT16 | Directly mapped. |
| Not supported | Not supported on Zilliz Cloud. |
| Not supported | Not supported on Zilliz Cloud. |
BOOL | Stores | |
VARCHAR | Stored as a string. Ensure correct format conversion. | |
VARCHAR | Stored as a string. | |
JSON | Stored in JSON format. | |
| JSON | Stored in JSON format. |
| JSON | Stored in JSON format. |
| JSON | Stored in JSON format. |
| VARCHAR | Stored as a string. |
| VARCHAR | Stored as a string. |
| VARCHAR | Mapped to |
| VARCHAR | Stored as a string. |
| INT32 | Stored as INT32. |
| Not supported | Not supported on Zilliz Cloud. |
VARCHAR | Stored as a string. | |
VARCHAR | Stored as a string. | |
VARCHAR | Stored as a string. | |
VARCHAR | Stored as a string. | |
Not supported | Derived fields are サポートされていません on Zilliz Cloud. | |
Not supported | Star-tree fields are サポートされていません on Zilliz Cloud. | |
Not supported | 配列s are サポートされていません for migration. | |
Not supported | Multifields are サポートされていません for migration. |
OpenSearch 固有の処理規則
コレクション命名規則
OpenSearch のインデックス名は、以下の考慮事項を踏まえて Zilliz Cloud に引き継がれます。
Scenario | Impact | ソリューション |
|---|---|---|
Default naming | Collection names match source index names exactly | Names are preserved as-is from OpenSearch |
Special characters | Index names with hyphens (-) or dots (.) will cause errors and prevent job submission | 手動で rename indexes to use underscores or other valid characters |
名前の競合 | Cannot submit job if a collection with the same name already exists | Delete existing collection, choose a different database, or rename during migration configuration |
移行に関する考慮事項
以下の機能は、OpenSearch からの移行においてサポートされていません。
制限ation | Impact | Alternative |
|---|---|---|
Dynamic to fixed field conversion | Cannot convert existing dynamic fields to fixed types | Fields maintain their original dynamic nature |
Add more fields | Cannot add new fields during migration | Only existing Elasticsearch fields are migrated |
Sparse vectors | Not supported in current release | Consider dense vector alternatives or contact support for roadmap |