There are two pieces of configuration required to use the Upstash vector client: an REST token and REST URL. These values can be passed using environment variables or in code through a configuration object. Find your configuration values in the console dashboard at https://console.upstash.com/.
The environment variables used to configure the client are the following. You can follow this guide to retrieve credentials.
When these environment variables are set, the client constructor does not require any additional arguments.
If you prefer to pass configuration in code, the constructor accepts a config object containing the url
and token
values. This
could be useful if your application needs to interact with multiple projects, each with a different configuration.
The Vector SDK supports defining your metadata type at the index level for complete type-safety.
Passing a metadata type at the index level will provide strong type safety for the metadata coming back from or required for the following commands:
query
upsert
fetch
range
In some cases, you might not want to define a metadata type at the index level. In this case, you can either override the index level type definition for a specific command, or pass a metadata type to specific commands instead.
The passing of a strong metadata type is possible for each of the four index operations listed above, we use upsert as an example.
There are two pieces of configuration required to use the Upstash vector client: an REST token and REST URL. These values can be passed using environment variables or in code through a configuration object. Find your configuration values in the console dashboard at https://console.upstash.com/.
The environment variables used to configure the client are the following. You can follow this guide to retrieve credentials.
When these environment variables are set, the client constructor does not require any additional arguments.
If you prefer to pass configuration in code, the constructor accepts a config object containing the url
and token
values. This
could be useful if your application needs to interact with multiple projects, each with a different configuration.
The Vector SDK supports defining your metadata type at the index level for complete type-safety.
Passing a metadata type at the index level will provide strong type safety for the metadata coming back from or required for the following commands:
query
upsert
fetch
range
In some cases, you might not want to define a metadata type at the index level. In this case, you can either override the index level type definition for a specific command, or pass a metadata type to specific commands instead.
The passing of a strong metadata type is possible for each of the four index operations listed above, we use upsert as an example.