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
A blank screen is shown when I try to open a PostgreSQL vector store in the Directory Tab. This vector store is a PostgreSQL server version 17 and uses the pgvector extension for vector capabilities.
Set up
I'm testing with the latest tag from ghcr.io/opendatadiscovery/odd-platform image (version: 0.27.5) running in a Kubernetes cluster.
Steps to Reproduce
Steps to reproduce the behavior:
Configure a collector to collect data from a PostgreSQL vector database using pgvector
Open Directory tab
Select Postgresql
Select the data source created by the collector
Expected behavior
To directory tab to open correctly.
Screenshots
This is what is shown in the browser console when I try to open the data source in the Directory tab:
Further investigation shown that this error occurs because the function get called cannot found the key VECTOR_STORE and returns undefined, which causes the error. The following image shows the correct return for another key:
And the next image shows the return for the key VECTOR_STORE:
The text was updated successfully, but these errors were encountered:
Describe the bug
A blank screen is shown when I try to open a PostgreSQL vector store in the Directory Tab. This vector store is a PostgreSQL server version 17 and uses the
pgvector
extension for vector capabilities.Set up
I'm testing with the
latest
tag fromghcr.io/opendatadiscovery/odd-platform
image (version: 0.27.5) running in a Kubernetes cluster.Steps to Reproduce
Steps to reproduce the behavior:
pgvector
Expected behavior
To directory tab to open correctly.
Screenshots
This is what is shown in the browser console when I try to open the data source in the Directory tab:
Further investigation shown that this error occurs because the function
get
called cannot found the keyVECTOR_STORE
and returnsundefined
, which causes the error. The following image shows the correct return for another key:And the next image shows the return for the key
VECTOR_STORE
:The text was updated successfully, but these errors were encountered: