`https://api.cloudflare.com/client/v4/accounts/920b1a6e159cf77dab28969103a4765b/vectorize/indexes/cu
https://api.cloudflare.com/client/v4/accounts/920b1a6e159cf77dab28969103a4765b/vectorize/indexes/customers-650a02c2a5be79517a7f79e2/query11 Replies
Hey folks, love the work on the AI stuff! Just wanted to drop in to chime in that I would love it for the limits on Vectorize index to be way higher, to the tune of a couple of indices per user of my app. That's all!
for survey purposes, what limit would fit your use case?
I don't want to give a number because it would scale with the number of users my app has, e.g. I need to be able to make vector searches against documents belonging only to a single user.
Even if it was 10,000, then what do I do at 10k users!
There's a world where I can filter post search, but that doesn't seem inefficient and probably severely limited by the
topK limitUnknown User•11mo ago
Message Not Public
Sign In & Join Server To View
Oh wow somehow I completely missed namespaces
Yeah I suppose without creating new indices with the API in order to "bin" the namespaces you're limited at 1000
But I guess my request now is more along the lines of increasing the namespace limit
I am getting "error code: 502" errors for the last few minutes on two different vectorize indices
The body literally only says "error code: 502" if I see this right. I am doing a normal request (that used to work a few days ago) on /query. It uses topK: 2 with a namespace filter and returnMetadata: true
This happens on both of my indices, if a cloudflare staff can DM me, I can provide the specific indices maybe there's more info on the cause on your isde
Greetings! Are there any hints on when we can expect vector DELETE and GET to be available through the REST api?
we're working on vector DELETE. For GET, is that get vector by id?
Hi @Vy, yes, that'd be what I'm interested in
thanks, we should be able to tackle GET same time as DELETE
Hey all!
I have a question regarding billing, if using metadata filters, would total queried vector dimensions be calculated towards the entire index or only the vectors matching the metadata filter?
I am currently studying the use case of partitioning user documents using filters, but don't want to be billed on a search through all vectors for a question regarding a single document
Sorry everyone, dumb question, it seems I misunderstood the pricing, a query is billed as 1 queried vector regardless of how many vectors are in the index, right? Now it makes sense why my estimations were coming out so absurd