You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/generative-apis/troubleshooting/fixing-common-issues.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,22 +124,22 @@ Below are common issues that you may encounter when using Generative APIs, their
124
124
## Embeddings vectors cannot be stored in database or used with a third-party library
125
125
126
126
### Cause
127
-
-The embedding model you are using generates vector representations of fixed dimensions number, which is too high for your database or third-party library.
127
+
The embedding model you are using generates vector representations with a fixed dimension number, which is too high for your database or third-party library.
128
128
- For example, the embedding model `bge-multilingual-gemma2` generates vector representations with `3584` dimensions. However, when storing vectors using PostgreSQL `pgvector` extensions, indexes (in `hnsw` or `ivvflat` formats) only support up to `2000` dimensions.
129
129
130
130
### Solution
131
131
- Use a vector store supporting higher dimensions number, such as [Qdrant](https://www.scaleway.com/en/docs/tutorials/deploying-qdrant-vectordb-kubernetes/).
132
-
- Do not use indexes for vectors or disable them from your thirdparty library. This may limit performance in vector similarity search for significant volumes.
133
-
- When using [Langchain PGVector method](https://python.langchain.com/docs/integrations/vectorstores/pgvector/), this method does not create index by default, and should not raise errors.
134
-
- When using [Mastra](https://mastra.ai/) library with `vectorStoreName: "pgvector"`, specify indexConfig type as `flat` to avoid creating any index on vector dimensions.
132
+
- Do not use indexes for vectors or disable them from your third-party library. This may limit performance in vector similarity search for significant volumes.
133
+
- When using [Langchain PGVector method](https://python.langchain.com/docs/integrations/vectorstores/pgvector/), this method does not create an index by default and should not raise errors.
134
+
- When using the [Mastra](https://mastra.ai/) library with `vectorStoreName: "pgvector"`, specify indexConfig type as `flat` to avoid creating any index on vector dimensions.
135
135
```typescript
136
136
awaitvectorStore.createIndex({
137
137
indexName: 'papers',
138
138
dimension: 3584,
139
139
indexConfig: {"type":"flat"},
140
140
});
141
141
```
142
-
- Use a model with a lower number of dimensions. Using [Managed Inference](https://console.scaleway.com/inference/deployments), you can deploy for instance `sentence-t5-xxl` model which represent vectors with `768` dimensions.
142
+
- Use a model with a lower number of dimensions. Using [Managed Inference](https://console.scaleway.com/inference/deployments), you can deploy for instance the`sentence-t5-xxl` model, which represents vectors with `768` dimensions.
143
143
144
144
## Best practices for optimizing model performance
0 commit comments