Repository navigation
docs: add Redis ADBC integration guide - #21
Open
alberttwong wants to merge 1 commit into
Open
alberttwong wants to merge 1 commit into
alberttwong wants to merge 1 commit into
Conversation
Contributor
|
I'll take it! give me me just a little bit to get my 2.0 ducks in a row. Thank you! |
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
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.
Adds a Redis ADBC integration guide linked from the README. It covers native driver and manifest installation, Redis Search prerequisites, attached reads, a local DuckDB join, explicit remote SQL, and Arrow ingestion/autocommit writes.
The guide calls out that Redis does not provide multi-statement transactions, that failed autocommit writes can partially apply, and that existing HASH collections need the driver's copy/adoption workflow before appearing as SQL tables.
Validation: executed every SQL block against an isolated Redis 8.6.2 container with Search, DuckDB 1.5.6 and the current community
adbc_scanner, substituting the disposable server URI and an absolute driver library path. All results were fetched and example tables cleaned up. The Redis driver's existing DuckDB regression also passed (1 test), covering reads, joins, ingestion, writes, READ_ONLY, and transaction rejection.