docs: update ArcadeDB integration overview#423
Merged
bilgeyucel merged 1 commit intomainfrom Mar 25, 2026
Merged
Conversation
kacperlukawski
force-pushed
the
arcadedb-cleanup
branch
from
cfd63bf to
38c4304
Compare
bilgeyucel
approved these changes
Mar 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The description of this integration should be more accurate.
Most vector databases and search engines can store all of these together, and ArcadeDB seems to be not that much different, except for the SQL interface, but from Haystack perspective it does not matter that much. I totally get the fact they support different types of data, but I'm unsure if that's the best framing, as it makes ArcadeDB solving an non existent problem.
Related to deepset-ai/haystack-core-integrations#2907