I'm getting the same error as @nclevenger ``` VECTOR_QUERY_ERROR: Status + 404 ```

I'm getting the same error as @nclevenger

VECTOR_QUERY_ERROR: Status + 404

VECTOR_QUERY_ERROR: Status + 404

Old Man MakerOP•10/4/23, 4:47 PM

just started happening

Old Man MakerOP•10/4/23, 4:54 PM

Account ID: 43310a46ee87ca6683a51510f7a57241

Old Man MakerOP•10/4/23, 4:55 PM

Can some please take a look for me.
The vectors are being created in the query correctly, calling <vectorize>.query() is failing

Old Man MakerOP•10/4/23, 4:56 PM

the index is ais-vec-bakedcontent-index

OOld Man Maker I'm getting the same error as @nclevenger ``` VECTOR_QUERY_ERROR: Status + 404...

Jerome•10/4/23, 5:08 PM

looking into it

JJerome looking into it

Old Man MakerOP•10/4/23, 5:09 PM

Thanks Sir

KKarl Hey, i'm playing around with vectorize and workers AI. Really impressed so far....

Matt Silverlock•10/5/23, 10:15 AM

You’d want some form of metadata filtering (we are working on it) for that.

MMatt Silverlock It’s not meant as a replacement. Some folks want more indexes for isolating diff...

Zak @ insertchat.com•10/5/23, 11:24 AM

Yup, that's my case. Do you see any advantages/disadvantages to using one big index with all user vectors + metadata filtering by a user id vs. one index per user?

ZZak @ insertchat.com Yup, that's my case. Do you see any advantages/disadvantages to using one big in...

Matt Silverlock•10/5/23, 11:30 AM

It will depend on your index size. If the count of vectors per user is very small, and will remain so, a larger single index will remain “hot”

Zak @ insertchat.com•10/5/23, 11:31 AM

Oh I see, there is a notion of hot/cold storage involved. What's your definition of small? Millions? Tens of millions? 1 billion?

ZZak @ insertchat.com Oh I see, there is a notion of hot/cold storage involved. What's your definition...

Matt Silverlock•10/5/23, 11:33 AM

per user or per index? Small would be thousands per user - over hundreds of thousands of users -> an index in the millions.

Zak @ insertchat.com•10/5/23, 11:34 AM

I don't have more then a million vector per user

Matt Silverlock•10/5/23, 11:34 AM

To step back a second: it really doesn’t matter that much, and it probably doesn’t make a lot of sense to over engineer this right now

Zak @ insertchat.com•10/5/23, 11:34 AM

The total in my db right now is between 5 and 10 millions vectors

Matt Silverlock•10/5/23, 11:35 AM

That’s fine.

Matt Silverlock•10/5/23, 11:36 AM

Write your raw embeddings to R2. If you want to change your approach, it’s much easier to repopulate an index vs a traditional RDBMS

Zak @ insertchat.com•10/5/23, 11:39 AM

Will dump a few million vectors to Vectorize once we have filtering to see how it performs with a user id filter, if it's good then it's a go for production, and will see if we change it later to multiple indexes

Zak @ insertchat.com•10/5/23, 12:35 PM

Can we also expect a way to CRUD a vector (row) directly by its id/uid?

ZZak @ insertchat.com Can we also expect a way to CRUD a vector (row) directly by its id/uid?

Jerome•10/5/23, 12:45 PM

there is

getByIds

getByIds

and

deleteByIds

deleteByIds

operations;

insert

insert

and

upsert

upsert

take the id you provide as well

Zak @ insertchat.com•10/5/23, 12:46 PM

I'm an API user, don't have those (I think)

Zak @ insertchat.com•10/5/23, 1:31 PM

Hopefully, API users will get some love from Cloudflare x)

prmptCoder•10/5/23, 3:14 PM

Is it possible to train or fine-tune the text-generation-model distilbert-sst-2-int8 and deploy@everyone

PprmptCoder Is it possible to train or fine-tune the text-generation-model distilbert-sst-2-...

Old Man MakerOP•10/5/23, 3:23 PM

AFAIK - model hosting with Hugging Face is on the road map to be exposed by cloudflare, so you should be able to at some point

Andrew Mayne•10/6/23, 12:07 AM

Hey folks! Two questions:

1. Is there some knack to saving meta data? Everything else saves in this example except the metadata:

const embedding = await getOpenAIEmbedding(description, env.OPENAI_KEY);
await env.VECTORIZE.upsert([{ id: promptId, values: embedding, metadata:{ title:"Updated title", description: "Description"} }]);

console.log("Item vector added:", { title: title, description: description })

2. Everytime I update from the CLI my vector binding are erased. Adding this to the TOML doesn't seem to help:

vectorize = [
{ binding = "VECTORIZE", index_name = "my-index" }
]

Or:

[[vectorize]]
binding = "VECTORIZE"
index_name = "my-index"

AAndrew Mayne Hey folks! Two questions: 1. Is there some knack to saving meta data? Everythin...

Old Man MakerOP•10/6/23, 2:48 AM

Keep in mind that metadata as a type may change in future if filtering by metadata is added.

At the moment, this is how I create it:

//I defined a new object type for the metadata - MetadataSchema 
let newMetaData:MetadataSchema ={
    d1Key: keyValue,
    prjRef: projectRef,
    accRef: accountRef,
    parentRef:parentRef
}

//Stuff the object in there
const metaRecord:Record<string,VectorizeVectorMetadata>= { 
    "data": JSON.stringify(newMetaData)
};

//Add to the vector
let tempVec:VectorizeVector ={
    id:id,
    values: data[0], //the embeddings
    namespace:<The Namespace>,
    metadata:metaRecord
}

//I defined a new object type for the metadata - MetadataSchema 
let newMetaData:MetadataSchema ={
    d1Key: keyValue,
    prjRef: projectRef,
    accRef: accountRef,
    parentRef:parentRef
}

//Stuff the object in there
const metaRecord:Record<string,VectorizeVectorMetadata>= { 
    "data": JSON.stringify(newMetaData)
};

//Add to the vector
let tempVec:VectorizeVector ={
    id:id,
    values: data[0], //the embeddings
    namespace:<The Namespace>,
    metadata:metaRecord
}

Ccfnathan Can you explain what behavior you're seeing a bit more? It sounds like the upser...

Andrew Mayne•10/6/23, 9:56 PM

I get a null value when I try to get the metadata. I can't tell if it's not added or not found:

I can retrieve the id and score, but not the meta.

Ccfnathan for (2): do you mean your Worker loses your Vectorize binding (e.g. `env.VECTORI...

Andrew Mayne•10/6/23, 10:00 PM

npm install wrangler@latest install 3.6.0, so that's what I've been using.

npm install wrangler@3.11.0 also installs 3.6.0.

npx wrangler deploy works though.

To be honest, I may be completely ignorant of how npm install works.

Ccfnathan we'll dig a bit more into (1) and get back to you. for (2), 3.11.0 should be ava...

Andrew Mayne•10/6/23, 11:31 PM

Thank you!

Keiagi•10/7/23, 7:45 AM

Hi, I just found this open-beta awesome project for a serverless vector database!
Is anyone developing python SDK? I couldn't find one!

KKeiagi Hi, I just found this open-beta awesome project for a serverless vector database...

Matt Silverlock•10/7/23, 12:09 PM

Vectorize has a REST API that you can call from Python.

KKeiagi Hi, I just found this open-beta awesome project for a serverless vector database...

Matt Silverlock•10/7/23, 12:10 PM

https://developers.cloudflare.com/vectorize/learning/insert-vectors/#http-api - example

Insert vectors · Vectorize

Vectorize indexes allow you to insert vectors at any point: Vectorize will optimize the index behind the scenes to ensure that vector search remains …

MMatt Silverlock Vectorize has a REST API that you can call from Python.

Keiagi•10/7/23, 2:11 PM

Great! Thanks for sharing, Matt!
I hope that python SDK will be available in the near future, but I will try REST API first in the meantime, because serverless vector db is awesome!

JJohnny Is anyone else running into the issue of `env.VECTORIZE_INDEX` not being loaded ...

craigsdennis•10/7/23, 3:37 PM

I'm thinking you should remove the comment on the binding line and try again.

Sobev•10/9/23, 9:01 AM

wrangler vectorize create vector-index --dimensions=768 --metric=cosine

X [ERROR] Unknown arguments: dimensions, metric, vectorize, create, vector-index
why i get an error

SSobev wrangler vectorize create vector-index --dimensions=768 --metric=cosine X [ERRO...

Hello, I’m Allie!•10/9/23, 9:11 AM

What's your

wrangler

wrangler

version?

HHello, I’m Allie!What's your `wrangler` version?

Sobev•10/9/23, 9:18 AM

3.8.0, ok i upgraded ,it worked

juand4.dev•10/10/23, 12:50 AM

I'm following this the get-starter https://developers.cloudflare.com/vectorize/get-started/embeddings/,

But when I do npx wrangler vectorize create embeddings-index --dimensions=768 --metric=cosinenpx wrangler vectorize create embeddings-index --dimensions=768 --metric=cosine, I got

"

Creating index: 'tutorial-index'

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

vectorize.not_entitled [code: 1005]"

I'm new, so I think I'm missing some configuration !!

kian•10/10/23, 12:50 AM

Do you have a paid Workers plan?

juand4.dev•10/10/23, 1:18 AM

Oh no, I just thought that had a "free layer" :c

-> I figure it out, it work just for paid worker planes, for now. And CF is planning to launch a free tier soon.

So, someone know when is It planed to come?

charl.dev•10/10/23, 8:47 AM

I need some info around the security due diligence etc around vectorize, like is the data encrypted, is there encryption at rest, GDPR, CCPA, HIPAA compliance.

Is there a doc or something we can give to our infosec guys?

kian•10/10/23, 8:50 AM

The information generic to Cloudflare is likely all that is available so far - https://www.cloudflare.com/en-gb/trust-hub/

Assuming that Vectorize is built on top of the existing primitives like Workers, Durable Objects and Workers KV then there will be information that already covers those.

Generally all of Cloudflare's offerings are covered under Standard Contractual Clauses with regards to GDPR.

charl.dev•10/10/23, 8:57 AM

thanks kian, just fyi there's a dead link on cloudflare.com/en-gb/ssl/

//I defined a new object type for the metadata - MetadataSchema let newMetaData:MetadataSchema ={ d1Key: keyValue, prjRef: projectRef, accRef: accountRef, parentRef:parentRef } //Stuff the object in there const metaRecord:Record<string,VectorizeVectorMetadata>= { "data": JSON.stringify(newMetaData) }; //Add to the vector let tempVec:VectorizeVector ={ id:id, values: data[0], //the embeddings namespace:<The Namespace>, metadata:metaRecord }

I'm getting the same error as @nclevenger ``` VECTOR_QUERY_ERROR: Status + 404 ```

Similar Threads

Similar Threads

Similar Threads