Register ADBC extension#507
Open
adsharma wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Another way to do ADBC: https://duckdb.org/community_extensions/extensions/adbc_scanner |
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
1 participant
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.
This will allow us to query more columnar data sources that speak ADBC
More info about adbc-drivers.
Runtime testing status:
Invalid Input Error: Attempting to execute an unsuccessful or closed pending query result
That points to a DuckDB ADBC direct-driver lifetime/manager expectation, not a compile issue. DuckDB’s docs describe using the ADBC driver-manager-style setup with driver and entrypoint options, while the direct initialized vtable rejects those options. Source: https://duckdb.org/docs/current/clients/adbc.html