I am getting 504 Gateway Timeouts intermittently when running `wrangler vectorize list` . Is there a

A

acOP•9/13/24, 8:55 PM

Also getting this intermittently on deploys, which has never happened before:

Error: Failed to publish your Function. Got error: binding <vectorize index name> of type vectorize failed to generate: internal error; please try again later or contact support

Error: Failed to publish your Function. Got error: binding <vectorize index name> of type vectorize failed to generate: internal error; please try again later or contact support

Error: Failed to publish your Function. Got error: binding <vectorize index name> of type vectorize failed to generate: internal error; please try again later or contact support

Error: Failed to publish your Function. Got error: binding <vectorize index name> of type vectorize failed to generate: internal error; please try again later or contact support

Aac I am getting 504 Gateway Timeouts intermittently when running `wrangler vectoriz...

Y

yevgen•9/15/24, 12:42 PM

We saw intermittent issues with one of the service instances running in our Core datacenter. It has resolved now.

C

cosbgn•9/15/24, 4:07 PM

Any way to filter metadata as array includes?

In my use case I have some files and they have tags like ["books", "work"], etc these tags are set by the users and I don't know them in advance.

Ideally I would be able to query embeddings only for "work" or only for "books" ]

C

cosbgn•9/16/24, 8:51 AM

Any way to delete a namespace and all the vectors inside it via rest API? doesn't seem to be documented

C

charl.dev•9/16/24, 8:32 PM

Is setting a ttl on a vector entry, similar to kv on the cards?

Have items I want to clear out like 3 months after creation. Can do like a nightly purge but would be a great feature IMO

Ccosbgn Any way to delete a namespace and all the vectors inside it via rest API? doesn'...

S

Sunny•9/17/24, 5:04 PM

I've been deleting through "wrangler vectorize delete <index_name>"

S

Sunny•9/17/24, 5:04 PM

though I'm running into an issue when trying to create a new index under the same name

S

Sunny•9/17/24, 5:05 PM

it gets deleted off my dashboard but I get this error when creating a duplicate index. Not sure how to fully remove it and its history

S

Sunny•9/17/24, 5:06 PM

🚧 Creating index: 'database-name'

✘ [ERROR] A request to the Cloudflare API (/accounts/b7b5a2f84f22862a502266ecc6abb2a0/vectorize/v2/indexes) failed.

  vectorize.index.deleted - Index name "database-name" [code: 3005]
  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

🚧 Creating index: 'database-name'

✘ [ERROR] A request to the Cloudflare API (/accounts/b7b5a2f84f22862a502266ecc6abb2a0/vectorize/v2/indexes) failed.

  vectorize.index.deleted - Index name "database-name" [code: 3005]
  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

🚧 Creating index: 'database-name'

✘ [ERROR] A request to the Cloudflare API (/accounts/b7b5a2f84f22862a502266ecc6abb2a0/vectorize/v2/indexes) failed.

  vectorize.index.deleted - Index name "database-name" [code: 3005]
  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

🚧 Creating index: 'database-name'

✘ [ERROR] A request to the Cloudflare API (/accounts/b7b5a2f84f22862a502266ecc6abb2a0/vectorize/v2/indexes) failed.

  vectorize.index.deleted - Index name "database-name" [code: 3005]
  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

C

chronark•9/18/24, 8:47 AM

is there a way to clear data in an index in the UI?
I can't see any and the docs aren't helping either

S

Sunny•9/18/24, 3:28 PM

I think you can only delete elements through the wrangler cli, and it’s only element by element, reference by id

S

Sunny•9/18/24, 3:28 PM

Otherwise, again through cli, you delete the whole index and make a new one

M

matt•9/19/24, 7:15 PM

Any roadmap for when max dimensions will be increased? I'd love to use text-embedding-3-large but it's 3072 dimensions.

Mmatt Any roadmap for when max dimensions will be increased? I'd love to use text-embe...

T

thipperz•9/20/24, 12:13 AM

you know that in the meantime you can specify 1536 dimensions in the open ai api call right?

M

matt•9/20/24, 3:25 AM

Yes I’m aware thank you. I’d like to take full advantage of it though.

M

mikibo•9/20/24, 5:51 PM

Hello there! Looking for how to use logical OR in vectorize metadata filtering. Is it possible? I've seen

AND

AND

AND

AND (implicit) but can't find

OR

OR

OR

OR.

C

charl.dev•9/20/24, 7:30 PM

Is vectorize available in DOs? I’ve bound it via toml and via env type but when I log this.env, I can see all my other bindings but not vectorize.

When I run wrangler dev, it does say the worker has access to vectorize

Ccharl.dev Is vectorize available in DOs? I’ve bound it via toml and via env type but when ...

C

charl.dev•9/20/24, 7:32 PM

Nvm was running remote flag with npm run dev lol

E

Eric•9/25/24, 4:24 AM

Hi all, when I delete an index, and try to create it with the same name through the API, I get

{
    "result": null,
    "success": false,
    "errors": [{
        "code": 3005,
        "message": "vectorize.index.deleted - Index name \"your_index_name\""
    }],
    "messages": []
}

{
    "result": null,
    "success": false,
    "errors": [{
        "code": 3005,
        "message": "vectorize.index.deleted - Index name \"your_index_name\""
    }],
    "messages": []
}

{
    "result": null,
    "success": false,
    "errors": [{
        "code": 3005,
        "message": "vectorize.index.deleted - Index name \"your_index_name\""
    }],
    "messages": []
}

{
    "result": null,
    "success": false,
    "errors": [{
        "code": 3005,
        "message": "vectorize.index.deleted - Index name \"your_index_name\""
    }],
    "messages": []
}

Is that by design? Is there a timelimit that it'll be purged on the backend?

E

Eric•9/25/24, 4:28 AM

Also note that I can't find anything related to this error message in the docs.

E

Eric•9/25/24, 4:36 AM

@Jerome (tagging because you seem familiar with this)

EEric Hi all, when I delete an index, and try to create it with the same name through ...

J

Jerome•9/25/24, 5:08 AM

Hi there! Yes index names are single use, cannot reuse after deletion. We are working on the documentation to clarify this

JJerome Hi there! Yes index names are single use, cannot reuse after deletion. We are wo...

E

Eric•9/25/24, 6:53 AM

Gotcha. I created the index

test

test

test

test and deleted it. Does that mean I can never create an index called

test

test

test

test for the life of my account?

E

Eric•9/25/24, 7:05 AM

Also, say I want to have multiple collections of data be indexed, but such data is completely unrelated to each other. Is it better to:

Create a single index and have it search the embeddings by namespace? (Also: Is the intended usage for namespaces specifically for file/data types?)
Store grouping information in the metadata, and have it query by the metadata? I doubt this one, since the collections are intended to be completely unrelated.
Create new indexes for each collection of data?

EEric Hi all, when I delete an index, and try to create it with the same name through ...

E

Eric•9/25/24, 7:06 AM

@nullptr

EEric Gotcha. I created the index `test` and deleted it. Does that mean I can never cr...

J

Jerome•9/25/24, 9:23 AM

Yes

EEric Also, say I want to have multiple collections of data be indexed, but such data ...

J

Jerome•9/25/24, 9:34 AM

1 index per collection seems the way to go if you will not want to run queries spanning several collections, and the number of collections is small and constant (as you'll want to bind against them in your worker, which is a manual operation).

Otherwise, one index with logic partitioning of the collections; namespace is the designated way to achieve this (but metadata would also work as you pointed out). With this approach (1 index with logic partitioning) you need to make sure however that your collections all use vectors that are the same dimension, indexed and queried with the same distance metric, and ideally from the same source (the same LLM for instance) to ensure consistency in the vector data, for best indexing accuracy.

EEric Hi all, when I delete an index, and try to create it with the same name through ...

R

Rihan•9/25/24, 12:45 PM

I've just ran into this limitation today too

JJerome Hi there! Yes index names are single use, cannot reuse after deletion. We are wo...

R

Rihan•9/25/24, 1:10 PM

Is there a planned way to empty a Vectorize index? My use case is resetting a preview environment's index. If not, the only way forward I see is recreating with a random string suffix.

R

Rihan•9/25/24, 3:03 PM

Furthermore would it be possible to support name reuse in the future?

RRihan Furthermore would it be possible to support name reuse in the future?

J

Jerome•9/25/24, 3:42 PM

Yes, we are aware this is an inconvenience and supporting index name reuse after deletion is on the roadmap, no shipping date yet

E

Eric•9/25/24, 11:25 PM

Gotcha. Thanks for the info!

E

Eric•9/26/24, 3:32 AM

A little follow up; I still don't quite understand the design for multi-collection dynamic data storage. Binding an index to a worker is a manual operation so dynamically created indexes aren't possible. This infers that having multiple indexes exist only for the purpose of different dimension sizes/metrics/embedding functions (since these are determined at creation time, and are constant) OR unless the data stored is also constant.

Say I have a user in my application with his/her own collection of data and they want to put it into an index dynamically. This must be done within a single index that all users share (separated by namespace for each user). Looking at the limits here:
https://developers.cloudflare.com/vectorize/platform/limits/
"Maximum vectors per index" shows a max of 5mil for the beta. Say the limit grows to 100mil- although 100mil embeddings is a lot for a single user, this won't scale well if I enable my users to upload data, forced to upload to a single index.

The (current beta) limit for number of indexes is 100. Say in the future we're able to bind indexes to workers dynamically. That still won't suffice for a user base even if that number grows to 10k or more.

In order to properly handle dynamic scaling, I could create all 100 possible indexes now, all empty, and use them as overflow space once the current index fills up. Coding this containerization algo would suck and I doubt that's the intended purpose.

I get the impression that uploading data and initializing indexes is a constant operation. I'm designing an application now so any advice on how to properly design my architecture for the future would help! @Jerome

E

Eric•9/26/24, 3:37 AM

Currently I'll be limited by:

100 users max where each index name can only be used once OR
5 mil embeddings total for the application OR
My coding ability to whip up a containerization algo, then limited by 100 indexes * 5mil vectors (in beta i know, but still)

I guess my question boils down to- how should I design my application such that it scales dynamically once beta is over? Thank you for being informative so far

Yyevgen yes, Q1 2025 we plan to ship support for Vectorize dynamic bindings.

R

Rihan•9/26/24, 9:49 AM

@Eric Vectorize dynamic bindings are coming hopefully in Q1. I believe Cloudflare can increase the number of indexes limit on an account basis too.

EEric Currently I'll be limited by: - 100 users max where each index name can only be ...

A

Akanbi•9/26/24, 5:43 PM

Cindy thud

AAkanbi Cindy thud

E

Eric•9/27/24, 12:44 AM

Who's Chindy thud?

R

Rubi•9/27/24, 8:11 AM

Is there any way to export Vectorize data? I want to migrate to another provider

Ccfnathan This is a symptom of how we have the beta deployed. As mentioned in the above th...

R

Rubi•9/27/24, 8:46 AM

hi, is the new deployed?

U

uri•9/29/24, 1:41 PM

hi, there is an option to backup and restore indexes?

U

uri•9/29/24, 1:43 PM

also, vectorize limit to the number of indexes one can create?

U

uri•9/29/24, 2:15 PM

I noticed on this page "https://developers.cloudflare.com/vectorize/platform/limits/" that the current limits are 100 indexes and 1,000 namespaces. While this might be sufficient for testing, it's far from enough for production use. Are there any plans to scale these limits—at least by a couple of orders of magnitude? Something closer to 1,000,000 or more would be ideal.

U

uri•9/29/24, 2:26 PM

I want to building my SaaS around 'Vectorize' as I really like the platform. However, with the current limitations in place, if these are expected to remain for the foreseeable future, I won't be able to use it for my needs. Additionally, dedicated functions or tools for backup and restore are essential for anyone looking to use this platform in production environments. Could someone provide insight into the current roadmap for 'Vectorize' in terms of limitations and development? What can we expect in the near future?

R

Rihan•10/2/24, 4:56 PM

With terminology, are Vectorize indexes and databases exchangeable terms, or are indexes the preferred way to refer to them?

R

Rihan•10/2/24, 4:56 PM

This is on Pages -> Settings -> Bindings -> Add -> Vectorize database

A

Ashley•10/2/24, 9:09 PM

Is the billing page broken? I clicked view next to monthly usage on the Vectorize dashboard and I get an oops page

E

echoes221•10/3/24, 10:56 PM

Remix + Cloudflare - running wrangler types generates the correct vectorize types, however the proxy stub doesn't exist in the loader (cloudflareDevProxyVitePlugin). Is this due to beta?

  const {
    params,
    context: { cloudflare },
  } = args;
 
  if (!cloudflare.env.VECTORIZE) { // <-- doesn't exist
    console.log("no key"); 
    return;
  }

  const {
    params,
    context: { cloudflare },
  } = args;
 
  if (!cloudflare.env.VECTORIZE) { // <-- doesn't exist
    console.log("no key"); 
    return;
  }

  const {
    params,
    context: { cloudflare },
  } = args;
 
  if (!cloudflare.env.VECTORIZE) { // <-- doesn't exist
    console.log("no key"); 
    return;
  }

  const {
    params,
    context: { cloudflare },
  } = args;
 
  if (!cloudflare.env.VECTORIZE) { // <-- doesn't exist
    console.log("no key"); 
    return;
  }

S

sathoro•10/4/24, 8:20 AM

can the 1,000 namespaces per index limit be easily increased? we use Pinecone but was looking at using Vectorize for a new feature and this limit is really putting us off

Eechoes221 Remix + Cloudflare - running wrangler types generates the correct vectorize type...

R

Rubi•10/4/24, 11:42 AM

yes, vectorize is currently not available on local

I am getting 504 Gateway Timeouts intermittently when running `wrangler vectorize list` . Is there a

Similar Threads

Similar Threads

Similar Threads