Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Postgres VectorStore: TypeORMVectorStore issue with NULL characters and doesn't allow configuring content column name #3362

Closed
JJK801 opened this issue Oct 15, 2024 · 1 comment · Fixed by #3367

Comments

@JJK801
Copy link
Contributor

JJK801 commented Oct 15, 2024

Describe the bug
As Flowise Postgres VectorStore node uses TypeORMVectorStore, it doesn't deals with 0x00 characters from documents, leading to au postgres insert error.

It also enforce content column name to be pageContent (while PGVectorStore default is text, but allows to change it)

To Reproduce
Steps to reproduce the behavior:

  1. Create a chatflow with Postgres as a vector store
  2. try to load this document: https://sonoff.tech/wp-content/uploads/2021/03/%E8%AF%B4%E6%98%8E%E4%B9%A6-DUALR3-V1.0-20210305.pdf
  3. PG doesn't insert due to error

Expected behavior

  • Use PGVectorStore instead of TypeORMVectorStore (maybe make it configurable ?)
  • Add additional configurations for customizing columns names
@JJK801
Copy link
Contributor Author

JJK801 commented Oct 15, 2024

i can make a PR if needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant