feat: add IBM Db2 Vector Store (ibm-haystack)

[priyanshu-krishnan1]

Related Issues

• fixes #issue-number

Proposed Changes:

How did you test it?

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ priyanshu-krishnan1
❌ Dhruv Chaturvedi

---

Dhruv Chaturvedi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pypi/​ibm-db@​3.2.9

View full report

[sjrl]

Hey @priyanshu-krishnan1 thanks for the opening PR! Apologies for closing that was a misclick. Its looking good so far, I have some high-level comments:

• I noticed that there is an empty retrievers folder. Is that intended? If there are no retrievers yet it would be great to remove that for now.
• Could you use the mixin tests for testing document store. You can check out how they are used in other integrations in this repo like the PGVector doc store https://github.com/deepset-ai/haystack-core-integrations/blob/main/integrations/pgvector/tests/test_document_store.py#L34
• After talking with @julian-risch we agreed that the integration should be called ibm-db-haystack and the module level folder should go from ibm to ibm_db. I'd recommend either regenerating the scaffold using the scaffold script using the new name or checking other integrations with a dash in their name like google-genai-haystack
• Please add an entry to the labeler file in alphabetical order https://github.com/deepset-ai/haystack-core-integrations/blob/main/.github/labeler.yml
• I noticed we are missing workflow file to run the CI. Please check out examples for other doc stores in .github/workflows/
• Please also update the ci coverage file https://github.com/deepset-ai/haystack-core-integrations/blob/main/.github/workflows/CI_coverage_comment.yml

[priyanshu-krishnan1]

Hi @sjrl, Thank you for the detailed review and feedback.
I will address all the points in next commits on this PR:

• Currently working on retriever and will add retriever logic into scaffolded folder of component/retrievers.
• Refactor the document store tests to use the shared mixin test approach, following the PGVector integration as a reference.
• Rename the integration to ibm-db-haystack and update the module structure from ibm to ibm_db as recommendations from @julian-risch
• Add the appropriate entry to .github/labeler.yml in alphabetical order.
• Add the required CI workflow files based on the existing document store integrations.
• Update CI_coverage_comment.yml accordingly.

Thanks again for the guidance.

[sjrl]

Hi @priyanshu-krishnan1, just flagging this early so it can be addressed before the PR progresses further.

One of the commits in this PR appears not to be linked to a GitHub user, which is causing the CLA checks to fail:

6ddfa5f

The failing CLA check is here:

#3458 (comment)

It looks like this commit may belong to Dhruv Chaturvedi. Could you please check with them and ask them to sign the CLA as well? Alternatively, if that commit is not needed or was included by mistake, please remove it from the PR history so the CLA check can pass.

[priyanshu-krishnan1]

Hi @sjrl, we have completed the development for Phase 1 of the IBM Db2 Vector Store. The implementation is now ready for your review. We'd appreciate your feedback and any suggestions for improvements.

[sjrl]

Hey @priyanshu-krishnan1 great to hear! I should be able to give this another review soon. In the mean time could you look at this comment I left #3458 (comment)

It has to do with resolving the CLA agreement check.

[sjrl]

Hi @priyanshu-krishnan1 , the last force-push didn't fix the CLA issue and pulled in several unrelated commits (dependabot, a Chroma fix, a changelog bump), which is what spammed the coverage-report comments. The CLA is still failing because of commit 6ddfa5f ("Add IBM integration label and config"), which is authored by Dhruv Chaturvedi under an email that isn't linked to a GitHub account.

The branch history is tangled from old main merges, so the simplest path forward is to start clean: branch off the latest main, copy over just your integrations/ibm_db/ work plus the config changes (labeler, CI coverage, workflow, README), commit it as a single commit authored by you, and open a fresh PR. That drops all the unrelated commits and the bad-author commit in one go, and the CLA check should pass.

Let me know if you have any questions!

[priyanshu-krishnan1]

Hi @sjrl, as per your recommendation, we've created a new PR: #3518.
Please review the new PR and share your feedback or any suggestions for improvement.
Thanks!

[priyanshu-krishnan1]

closing this PR, development have been moved to this new PR as per recommendation
#3518