If I do the req via postman I get the html 502 error that explains that my browser and cloudflare fr

D

divby0OP•1/20/24, 8:48 AM

So the 502 code likely isn't what your api-gateway responded with, but I can't see more unfortunately. I've had this before once, and I can't recall if the issue was solved at all, maybe it's just still there.

My guess is that somewhere before my request gets to vectorize (maybe the api gateway?) the big post body gets rejected (cause 1536 vectors that take up much place in a string that contains

0.018004786

0.018004786

0.018004786

0.018004786 format numbers. The post body is 6kb big.

KKarl Hey everyone, i've come back to some old code and updated the types for CF and i...

K

kingmesal•1/20/24, 5:55 PM

I have a question on this exact same thing... which is...

Is it supposed to be id or vectorId ?
wrangler:

compatibility_date = "2024-01-20"

compatibility_date = "2024-01-20"

compatibility_date = "2024-01-20"

compatibility_date = "2024-01-20"
and using the latest data types:

"@cloudflare/workers-types": "^4.20240117.0",

"@cloudflare/workers-types": "^4.20240117.0",

"@cloudflare/workers-types": "^4.20240117.0",

"@cloudflare/workers-types": "^4.20240117.0", shows this:

declare interface VectorizeMatches {
  matches: VectorizeMatch[];
  count: number;
}
declare interface VectorizeMatch {
  /** The ID for the vector. This can be user-defined, and must be unique. It should uniquely identify the object, and is best set based on the ID of what the vector represents. */
  vectorId: string;
  /** The score or rank for similarity, when returned as a result */
  score: number;
  /** Vector data for the match. Included only if the user specified they want it returned (via {@link VectorizeQueryOptions}). */
  vector?: VectorizeVector;
}

declare interface VectorizeMatches {
  matches: VectorizeMatch[];
  count: number;
}
declare interface VectorizeMatch {
  /** The ID for the vector. This can be user-defined, and must be unique. It should uniquely identify the object, and is best set based on the ID of what the vector represents. */
  vectorId: string;
  /** The score or rank for similarity, when returned as a result */
  score: number;
  /** Vector data for the match. Included only if the user specified they want it returned (via {@link VectorizeQueryOptions}). */
  vector?: VectorizeVector;
}

declare interface VectorizeMatches {
  matches: VectorizeMatch[];
  count: number;
}
declare interface VectorizeMatch {
  /** The ID for the vector. This can be user-defined, and must be unique. It should uniquely identify the object, and is best set based on the ID of what the vector represents. */
  vectorId: string;
  /** The score or rank for similarity, when returned as a result */
  score: number;
  /** Vector data for the match. Included only if the user specified they want it returned (via {@link VectorizeQueryOptions}). */
  vector?: VectorizeVector;
}

declare interface VectorizeMatches {
  matches: VectorizeMatch[];
  count: number;
}
declare interface VectorizeMatch {
  /** The ID for the vector. This can be user-defined, and must be unique. It should uniquely identify the object, and is best set based on the ID of what the vector represents. */
  vectorId: string;
  /** The score or rank for similarity, when returned as a result */
  score: number;
  /** Vector data for the match. Included only if the user specified they want it returned (via {@link VectorizeQueryOptions}). */
  vector?: VectorizeVector;
}

When I query the records from the data store I get this data structure back:

{
  "count": 3,
  "matches": [
    {
      "id": "uuid-2",
      "namespace": "site:ecb",
      "score": null
    },
    {
      "id": "uuid-3",
      "namespace": "site:ecb",
      "score": null
    },
    {
      "id": "uuid-1",
      "namespace": "site:ecb",
      "score": null
    }
  ]
}

{
  "count": 3,
  "matches": [
    {
      "id": "uuid-2",
      "namespace": "site:ecb",
      "score": null
    },
    {
      "id": "uuid-3",
      "namespace": "site:ecb",
      "score": null
    },
    {
      "id": "uuid-1",
      "namespace": "site:ecb",
      "score": null
    }
  ]
}

{
  "count": 3,
  "matches": [
    {
      "id": "uuid-2",
      "namespace": "site:ecb",
      "score": null
    },
    {
      "id": "uuid-3",
      "namespace": "site:ecb",
      "score": null
    },
    {
      "id": "uuid-1",
      "namespace": "site:ecb",
      "score": null
    }
  ]
}

{
  "count": 3,
  "matches": [
    {
      "id": "uuid-2",
      "namespace": "site:ecb",
      "score": null
    },
    {
      "id": "uuid-3",
      "namespace": "site:ecb",
      "score": null
    },
    {
      "id": "uuid-1",
      "namespace": "site:ecb",
      "score": null
    }
  ]
}

The supplied interfaces do NOT match what is being returned by the API calls. namespace is not listed as an optional field in

VectorizeMatch

VectorizeMatch

VectorizeMatch

VectorizeMatch

K

kingmesal•1/20/24, 6:07 PM

I will also +

this vectorize

As being able to do

>

>=

>=

>=

>=

<

<=

<=

<=

<= and boolean

true

true

true

true

false

false

is the only thing stopping me from moving forward with Vectorize ...

It would still be super convenient to also have an API:

  public queryById(
    id: string,
    options: VectorizeQueryOptions
  ): Promise<VectorizeMatches>;

  public queryById(
    id: string,
    options: VectorizeQueryOptions
  ): Promise<VectorizeMatches>;

  public queryById(
    id: string,
    options: VectorizeQueryOptions
  ): Promise<VectorizeMatches>;

  public queryById(
    id: string,
    options: VectorizeQueryOptions
  ): Promise<VectorizeMatches>;

I 100% know I can write this on my own, but it is one of the most used queries I have.

Ccfnathan Are you asking specifically if the namespace field is optional in the new format...

K

kingmesal•1/21/24, 7:17 PM

The tsconfig only has

"types": ["@cloudflare/workers-types"],

"types": ["@cloudflare/workers-types"],

"types": ["@cloudflare/workers-types"],

"types": ["@cloudflare/workers-types"],

I did see that notice, but this vecordId / id thing has been an issue for atleast 3 weeks (that is when I started building my use case w/ vectorize). I'll wait until Tuesday before coming back to this topic.

For the namespace thing, if I go browsing into the downloaded workers-types package -> experimental folder I see what you are referring to. I'm curious why the latest changes are still listed as experimental and not in a dated folder.... not sure how that is setup... but I can see the new api layout in the experimental folder.

Kkingmesal The tsconfig only has `"types": ["@cloudflare/workers-types"],` I did see that ...

D

DaniFoldi•1/21/24, 7:50 PM

Experimental always contains the newest types - including ones that end-users like us can't yet access, since the features behind them are experimental. I also recommend using the

2023-07-01

2023-07-01

2023-07-01

2023-07-01 entrypoint, as suggested above by Nathan, if your worker compatibility_date is set to something newer.

In general, the recommendation is to use the newest dated folder (so never experimental) that is older than your worker compat date. So if you have

compatibility_date = '2024-01-01'

compatibility_date = '2024-01-01'

compatibility_date = '2024-01-01'

compatibility_date = '2024-01-01'

you'd use

"types": ["@cloudflare/workers-types/2023-07-01"]

"types": ["@cloudflare/workers-types/2023-07-01"]

"types": ["@cloudflare/workers-types/2023-07-01"]

"types": ["@cloudflare/workers-types/2023-07-01"]. Not all changes requiring a compatibility flag/date update require a new type update, for example if they fix previously buggy behaviour or introduce a change that doesn't change types, just some runtime quirks, that's why there are fewer type entrypoints than entries in the changelog.

DDaniFoldi Experimental always contains the newest types - including ones that end-users li...

K

kingmesal•1/21/24, 7:53 PM

That is helpful information, thanks!

Given the new API updates landing this week... will there be a new compat date added so the data types match up ?

Kkingmesal That is helpful information, thanks! Given the new API updates landing this wee...

D

DaniFoldi•1/21/24, 7:57 PM

If I understood Vy's message correctly, the upcoming change will only affect the HTTP api, available at api.cloudflare.com/...

Compatibility dates and flags are only a concept within workers (http api has a different versioning mechanism), which the change will not affect in any way. I believe the heads-up was because they have no intentions of supporting the old api whatsoever after the change rolls out. Since Vectorize is in beta, this is completely normal, and still very nice of them MeowHeartCloudflare

to give a notification in advance.

Ddivby0 If I do the req via postman I get the html 502 error that explains that my brows...

D

divby0OP•1/22/24, 11:07 AM

Did this slip maybe? Not sure if it's really monday already wherever the cloudflare team works, just didn't want this to go unnoticed since it's impacting mine and also Sunil's usage (probably more people)

Ccfnathan The types shouldn't be experimental anymore - what I linked to in workerd should...

K

kingmesal•1/22/24, 2:57 PM

I have confirmed it is there on my end... i suspect perhaps my vscode reload window resolved the field references. Thanks!

Ddivby0 Did this slip maybe? Not sure if it's really monday already wherever the cloudfl...

Y

yevgen•1/22/24, 4:37 PM

Hi @divby0 , the team rolled out a potential fix and currently monitoring this.

Yyevgen Hi @divby0 , the team rolled out a potential fix and currently monitoring this.

D

divby0OP•1/23/24, 11:28 AM

Seems like my specific error at least has been resolved with that.

D

divby0OP•1/23/24, 11:30 AM

You should add that namespace identifiers used to be able to take integers directly, but now you have to

toString()

toString()

toString()

toString() them. Maybe that's something you want to add to your changelog

Cause the

/insert

/insert

/insert

/insert endpoint takes integers without warning and still succeeds, but

/query

/query

/query

/query then complains that the namespace has to be a string. (If you do hand in a string there, it will not match with the namespace integer you put in while doing

/insert

/insert

/insert

/insert)

D

divby0OP•1/23/24, 1:14 PM

can I somehow see how many vectors there are in a given index?

D

divby0OP•1/23/24, 1:14 PM

doesn't have to be API-able, I just need to check manually when I make some changes

D

divby0OP•1/23/24, 1:19 PM

also if I seperate / filter by namespace, the actually high-cost algos are cheaper because I don't query that many vectors right? Or is namespace filtered after the expensive calculations?

D

divby0OP•1/23/24, 2:54 PM

awesome

As long as you have it on the radar, perfect

L

loup•1/25/24, 8:05 AM

HEllo ! Do we have an idea when vectorize might get out of beta ?

Yyevgen Hi @divby0 , the team rolled out a potential fix and currently monitoring this.

D

divby0OP•1/25/24, 8:15 AM

I'm getting 502s again. Is any incident known or what's happening now again after it worked for a few days?

D

divby0OP•1/25/24, 8:26 AM

The 3 dimension index works as expected and my normal 1536 dimensions index has 502 :/

C

carrot sticks•1/25/24, 3:44 PM

This is such a cool service

C

carrot sticks•1/25/24, 4:06 PM

how silly will it be for me to build my website around this vectorize functionality?

i plan on using it to vectorize user profile data for profile matching, using this API will be the crucial microservice of the project. is there any information on when updates will come to this functionality? like paywalling it or limiting requests

C

carrot sticks•1/25/24, 4:13 PM

Thank you nathan, never saw that. Peanuts cost as usual

Ccfnathan Ah, sorry, our release yesterday undid the change we made: let me make the chang...

D

divby0OP•1/25/24, 4:29 PM

can you update here when you did deploy the change permanent? Or did you already (cause I am still not able to get a OK status code)

D

divby0OP•1/25/24, 4:44 PM

awesome works!

Ccfnathan This should be in place now - if you still see 502's let us know 🙂

D

divby0OP•1/25/24, 4:44 PM

Thanks you

Y

yevgen•2/1/24, 1:41 PM

Hi @Anders we've made a decision to lockdown any changes to our APIs until we ship multi-million vectors support per index. We will review future API changes after that.

W

Wang•2/6/24, 7:10 AM

Hi, Why can't I find the "vectoize" function in the menu bar? Thank you.

W

Wang•2/6/24, 7:10 AM

C

chientrm.com•2/8/24, 4:09 AM

I don't see

Vectorize

Vectorize

Vectorize

Vectorize too

Y

Yanni•2/8/24, 7:53 PM

Why is in this calculation the number of vectors added to the number of queries. Wouldn't it make more sense to multiply them?

T

Tarcísio•2/8/24, 7:54 PM

Holla

YYanni Why is in this calculation the number of vectors added to the number of queries....

Y

Yanni•2/8/24, 7:58 PM

does this 10000 only count for the first time (when you insert it in the vectorstore)? And every query after that against the vectorstore just costs the number of vector dimensions?

YYanni does this 10000 only count for the first time (when you insert it in the vectors...

V

Vy•2/9/24, 8:00 PM

yes, its following the formula in https://developers.cloudflare.com/vectorize/platform/pricing/#calculating-vector-dimensions with

(stored vectors + queried vectors) * dimensions

(stored vectors + queried vectors) * dimensions

(stored vectors + queried vectors) * dimensions

(stored vectors + queried vectors) * dimensions

Cloudflare Docs

Pricing · Vectorize

Vectorize bills based on:

VVy yes, its following the formula in https://developers.cloudflare.com/vectorize/pl...

Y

Yanni•2/10/24, 11:44 AM

Wouldnt it make sense to expicit mention this in the documentation. Since it is a little confusing

Y

Yanni•2/10/24, 11:47 AM

Finding the most similar vector requires calculating the cosinus. Which requires more computing power when more vectores are stored in the database. Yes there are ways to optimize i. But the first thing that comes to my mind when reading through documentation is that the number of queries is the times that 2 vectores got compared.

If I do the req via postman I get the html 502 error that explains that my browser and cloudflare fr

Similar Threads

Similar Threads

Similar Threads