Skip to content

Adding Teradata VectorStore support in DocumentStore#5159

Merged
HenryHengZJ merged 11 commits intoFlowiseAI:mainfrom
sshekhar1:Teradata_DocumentStore
Oct 28, 2025
Merged

Adding Teradata VectorStore support in DocumentStore#5159
HenryHengZJ merged 11 commits intoFlowiseAI:mainfrom
sshekhar1:Teradata_DocumentStore

Conversation

@sshekhar1
Copy link
Copy Markdown
Contributor

@sshekhar1 sshekhar1 commented Sep 1, 2025 •
edited
Loading

Below are the screenshots for the working demo:

  • Selecting Vector Store Provider under Upsert Chunks option:
image
  • Using Teradata Vector Store under Upsert Chunks option in Document Store:
image
  • Upsert successful into Teradata Vector Store:
image
  • Test Retrieval on Teradata Vector Store:
image
  • Teradata Vector Store node under ChatFlow:
image_721

@HenryHengZJ
Copy link
Copy Markdown
Contributor

HenryHengZJ commented Sep 5, 2025

are there any screenshots for working demo or recordings?

@sshekhar1 sshekhar1 force-pushed the Teradata_DocumentStore branch from 6729347 to 79620b4 Compare September 8, 2025 07:09
@sshekhar1
Copy link
Copy Markdown
Contributor Author

sshekhar1 commented Sep 8, 2025

are there any screenshots for working demo or recordings?

@HenryHengZJ I have added the screenshots in the Pull Request Description as suggested. Thanks !

@HenryHengZJ
Copy link
Copy Markdown
Contributor

HenryHengZJ commented Sep 9, 2025

can you do pnpm lint-fix?

@sshekhar1
Copy link
Copy Markdown
Contributor Author

sshekhar1 commented Sep 10, 2025

Output for pnpm lint-fix:

$ pnpm lint-fix

> [email protected] lint-fix C:\Users\ss186247\OneDrive - Teradata Corporation\Documents\FlowiseAI\flowise_repo_build\Flowise
> pnpm lint --fix


> [email protected] lint C:\Users\ss186247\OneDrive - Teradata Corporation\Documents\FlowiseAI\flowise_repo_build\Flowise
> eslint "**/*.{js,jsx,ts,tsx,json,md}" "--fix"

@sshekhar1
Copy link
Copy Markdown
Contributor Author

sshekhar1 commented Sep 29, 2025

@HenryHengZJ can you please help review the changes and let me know if any additional changes needed ?

HenryHengZJ
HenryHengZJ reviewed Sep 30, 2025
View reviewed changes
packages/components/credentials/TeradataVectorStoreApi.credential.ts
constructor() {
this.label = 'Teradata Vector Store API Credentials'
this.name = 'teradataVectorStoreApiCredentials'
this.version = 1.0
Copy link
Copy Markdown
Contributor

@HenryHengZJ HenryHengZJ Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we add description on how to get these credentials? as if user is new to teradata

Copy link
Copy Markdown
Contributor

@HenryHengZJ HenryHengZJ Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or perhaps we can create a docs page on https://github.com/FlowiseAI/FlowiseDocs and link to that

Copy link
Copy Markdown
Contributor Author

@sshekhar1 sshekhar1 Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The credentials related info is same as that mentioned in the below pull request:
#5002

@HenryHengZJ
Copy link
Copy Markdown
Contributor

HenryHengZJ commented Oct 28, 2025

thank you!

@HenryHengZJ HenryHengZJ merged commit ac565b8 into FlowiseAI:main Oct 28, 2025
2 checks passed
@HenryHengZJ
Copy link
Copy Markdown
Contributor

HenryHengZJ commented Nov 6, 2025

this is exactly what I was worrying about:
image

Seems like teradatasql does not support arm64 build, hence the error when building Docker image

@sshekhar1
Copy link
Copy Markdown
Contributor Author

sshekhar1 commented Nov 7, 2025

this is exactly what I was worrying about: image

Seems like teradatasql does not support arm64 build, hence the error when building Docker image

@HenryHengZJ The error doesn't seem to suggest that teradatasql doesn't support arm64 build. It seems to be related to missing build dependencies in the Docker container. The error CMake does not seem to be available indicates the container lacks the tools needed to compile native modules from source. It may require installing missing tools/dependencies for successful compilation.

The possible solution to this could be to use multi-stage build, where in "Build Stage" the build tools/dependencies can be installed for native module compilation and in "Production Stage" compiled node_modules can be copied from builder stage. Could you please check if this helps ?

@sshekhar1
Copy link
Copy Markdown
Contributor Author

sshekhar1 commented Nov 19, 2025 •
edited
Loading

@HenryHengZJ Hope you are doing fine. Did you get a chance to look into the build issue resolution somehow ? Please check my last comment and let me know if it can help fix build issue or am I missing something here.

@diego-fernandes
Copy link
Copy Markdown

diego-fernandes commented Nov 30, 2025

Hi! I tested this PR locally and found a solution for the arm64 build error.

  • Add koffi to pnpm onlyBuiltDependencies in package.json for native bindings support
  • Add cmake to Dockerfile apk installs to enable building koffi
    If helpful, I can open a new PR that builds on this or push these changes somewhere

diego-fernandes pushed a commit to diego-fernandes/Flowise that referenced this pull request Nov 30, 2025
Merge PR FlowiseAI#5159 from upstream
8fb1a55
@github-actions github-actions bot mentioned this pull request Jan 5, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@HenryHengZJ HenryHengZJ HenryHengZJ approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@sshekhar1 @HenryHengZJ @diego-fernandes