From 3b01bca4ea34e22fffab65b326e9bfe3e24aafd1 Mon Sep 17 00:00:00 2001 From: Garvit Gupta Date: Thu, 17 Oct 2024 16:13:25 +0530 Subject: [PATCH 1/5] [Vectorize] Announcement for the anticipated blocking of legacy index creation --- .../docs/vectorize/reference/transition-vectorize-legacy.mdx | 4 +++- src/content/partials/vectorize/vectorize-legacy.mdx | 2 ++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx b/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx index 02a3bcb5f64acca..be453c6fa72aa39 100644 --- a/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx +++ b/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx @@ -17,6 +17,8 @@ This document provides details around any transition steps that may be needed to Legacy Vectorize (V1) indexes are on a deprecation path. Support for these indexes would be limited and their usage is not recommended for any production workloads. +Furthemore, the creation of legacy Vectorize indexes would be blocked by December 2024. Other operations would be unaffected and would remain functional. + Additionally, the new Vectorize (V2) indexes can operate at a significantly larger scale (with a capacity for multi-million vectors), and provide faster performance. Please review the [Limits](/vectorize/platform/limits/) page to understand the latest capabilities supported by Vectorize. ## Notable changes @@ -41,7 +43,7 @@ Watch this space for the upcoming capability to migrate legacy (V1) indexes to t ::: -1. Wrangler now supports operations on the new version of Vectorize (V2) indexes by default. To use Wangler commands for legacy (V1) indexes, the `--deprecated-v1` flag must be enabled. Please note that this flag is only supported to create, get, list and delete indexes and to insert vectors. +1. Wrangler now supports operations on the new version of Vectorize (V2) indexes by default. To use Wrangler commands for legacy (V1) indexes, the `--deprecated-v1` flag must be enabled. Please note that this flag is only supported to create, get, list and delete indexes and to insert vectors. 2. Refer to the [REST API](/api/operations/vectorize-create-vectorize-index) page for details on the routes and payload types for the new Vectorize (V2) indexes. For legacy (V1) index operations, refer to [Deprecated REST API](). diff --git a/src/content/partials/vectorize/vectorize-legacy.mdx b/src/content/partials/vectorize/vectorize-legacy.mdx index a9628f4e9638481..ff5eed875705a03 100644 --- a/src/content/partials/vectorize/vectorize-legacy.mdx +++ b/src/content/partials/vectorize/vectorize-legacy.mdx @@ -6,6 +6,8 @@ Please use the `wrangler vectorize --deprecated-v1` flag to create, get, list, delete and insert vectors into legacy Vectorize V1 indexes. +Please note that the creation of legacy Vectorize indexes would be blocked by December 2024. Other operations would remain functional. + Refer to the [legacy transition](/vectorize/reference/transition-vectorize-legacy) page for more details on transitioning away from legacy indexes. ::: From 089bcd7d948b9000e38f78097631b81851248981 Mon Sep 17 00:00:00 2001 From: Yevgen Safronov Date: Thu, 17 Oct 2024 12:17:48 +0100 Subject: [PATCH 2/5] Update src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx --- .../docs/vectorize/reference/transition-vectorize-legacy.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx b/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx index be453c6fa72aa39..9db14d516f7f8f3 100644 --- a/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx +++ b/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx @@ -17,7 +17,7 @@ This document provides details around any transition steps that may be needed to Legacy Vectorize (V1) indexes are on a deprecation path. Support for these indexes would be limited and their usage is not recommended for any production workloads. -Furthemore, the creation of legacy Vectorize indexes would be blocked by December 2024. Other operations would be unaffected and would remain functional. +Furthemore, the creation of legacy Vectorize indexes will be blocked by December 2024. Other operations would be unaffected and would remain functional. Additionally, the new Vectorize (V2) indexes can operate at a significantly larger scale (with a capacity for multi-million vectors), and provide faster performance. Please review the [Limits](/vectorize/platform/limits/) page to understand the latest capabilities supported by Vectorize. From c3209b4921772f8f9d6ed2035ff3d266ea5fbce3 Mon Sep 17 00:00:00 2001 From: Yevgen Safronov Date: Thu, 17 Oct 2024 12:18:44 +0100 Subject: [PATCH 3/5] Update src/content/partials/vectorize/vectorize-legacy.mdx --- src/content/partials/vectorize/vectorize-legacy.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/partials/vectorize/vectorize-legacy.mdx b/src/content/partials/vectorize/vectorize-legacy.mdx index ff5eed875705a03..be02774e523aa95 100644 --- a/src/content/partials/vectorize/vectorize-legacy.mdx +++ b/src/content/partials/vectorize/vectorize-legacy.mdx @@ -6,7 +6,7 @@ Please use the `wrangler vectorize --deprecated-v1` flag to create, get, list, delete and insert vectors into legacy Vectorize V1 indexes. -Please note that the creation of legacy Vectorize indexes would be blocked by December 2024. Other operations would remain functional. +Please note that the creation of legacy Vectorize indexes will be blocked by December 2024. Other operations will remain functional. Refer to the [legacy transition](/vectorize/reference/transition-vectorize-legacy) page for more details on transitioning away from legacy indexes. From efbab862ee984e384f11ab9a235e15599fd97752 Mon Sep 17 00:00:00 2001 From: Yevgen Safronov Date: Thu, 17 Oct 2024 12:19:58 +0100 Subject: [PATCH 4/5] Update src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx --- .../docs/vectorize/reference/transition-vectorize-legacy.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx b/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx index 9db14d516f7f8f3..ebf954592f6f3e2 100644 --- a/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx +++ b/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx @@ -17,7 +17,7 @@ This document provides details around any transition steps that may be needed to Legacy Vectorize (V1) indexes are on a deprecation path. Support for these indexes would be limited and their usage is not recommended for any production workloads. -Furthemore, the creation of legacy Vectorize indexes will be blocked by December 2024. Other operations would be unaffected and would remain functional. +Furthemore, the creation of legacy Vectorize indexes will be blocked by December 2024. Other operations will be unaffected and will remain functional. Additionally, the new Vectorize (V2) indexes can operate at a significantly larger scale (with a capacity for multi-million vectors), and provide faster performance. Please review the [Limits](/vectorize/platform/limits/) page to understand the latest capabilities supported by Vectorize. From cc9f5daa4e400a2005e9214ab68f81ec433f9925 Mon Sep 17 00:00:00 2001 From: Garvit Gupta Date: Tue, 22 Oct 2024 07:21:26 -0500 Subject: [PATCH 5/5] Apply suggestions from code review Co-authored-by: Jun Lee --- .../docs/vectorize/reference/transition-vectorize-legacy.mdx | 2 +- src/content/partials/vectorize/vectorize-legacy.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx b/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx index ebf954592f6f3e2..8de37a919708c44 100644 --- a/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx +++ b/src/content/docs/vectorize/reference/transition-vectorize-legacy.mdx @@ -17,7 +17,7 @@ This document provides details around any transition steps that may be needed to Legacy Vectorize (V1) indexes are on a deprecation path. Support for these indexes would be limited and their usage is not recommended for any production workloads. -Furthemore, the creation of legacy Vectorize indexes will be blocked by December 2024. Other operations will be unaffected and will remain functional. +Furthermore, you will no longer be able to create legacy Vectorize indexes by December 2024. Other operations will be unaffected and will remain functional. Additionally, the new Vectorize (V2) indexes can operate at a significantly larger scale (with a capacity for multi-million vectors), and provide faster performance. Please review the [Limits](/vectorize/platform/limits/) page to understand the latest capabilities supported by Vectorize. diff --git a/src/content/partials/vectorize/vectorize-legacy.mdx b/src/content/partials/vectorize/vectorize-legacy.mdx index be02774e523aa95..2bcb113b567b416 100644 --- a/src/content/partials/vectorize/vectorize-legacy.mdx +++ b/src/content/partials/vectorize/vectorize-legacy.mdx @@ -6,7 +6,7 @@ Please use the `wrangler vectorize --deprecated-v1` flag to create, get, list, delete and insert vectors into legacy Vectorize V1 indexes. -Please note that the creation of legacy Vectorize indexes will be blocked by December 2024. Other operations will remain functional. +Please note that by December 2024, you will not be able to create legacy Vectorize indexes. Other operations will remain functional. Refer to the [legacy transition](/vectorize/reference/transition-vectorize-legacy) page for more details on transitioning away from legacy indexes.