- C# 43.9%
- C++ 20%
- Go 7.3%
- Java 6.7%
- Rust 5.4%
- Other 16.6%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
decc3da8aaCopilot review on https://github.com/apache/arrow-adbc/pull/4939#discussion_r4344728019 found an edge case in the C++ driver manager when strings that are too long to be valid operating-system-specific file paths are used. The current implementation uses the variant of `std::filesystem::exists` that throws and we weren't catching those. This PR converts those uses to `bool exists( const std::filesystem::path& p, std::error_code& ec ) noexcept;` and either ignores the error or handles it an enhances the driver manager error. This PR was detected with Copilot and I drove Opus 5.5 around. The changes were tested in CI, see comments in the PR thread. |
||
| .github | ||
| c | ||
| ci | ||
| csharp | ||
| dev | ||
| docs | ||
| glib | ||
| go | ||
| java | ||
| javascript | ||
| python | ||
| r | ||
| ruby | ||
| rust | ||
| testing@25d16511e8 | ||
| .asf.yaml | ||
| .clang-format | ||
| .clang-tidy | ||
| .cmake-format | ||
| .codespell-dictionary | ||
| .codespell-ignore | ||
| .codespellrc | ||
| .env | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .golangci.toml | ||
| .pre-commit-config.yaml | ||
| AGENTS.md | ||
| CHANGELOG.md | ||
| compose.yaml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| pyrightconfig.json | ||
| README.md | ||
| ruff.toml | ||
ADBC: Arrow Database Connectivity
ADBC is an API standard (version 1.0.0) for database access libraries ("drivers") in C, Go, and Java that uses Arrow for result sets and query parameters. Instead of writing code to convert to and from Arrow data for each individual database, applications can build against the ADBC APIs, and link against drivers that implement the standard. Additionally, a JDBC/ODBC-style driver manager is provided. This also implements the ADBC APIs, but dynamically loads drivers and dispatches calls to them.
Like JDBC/ODBC, the goal is to provide a generic API for multiple databases. ADBC, however, is focused on bulk columnar data retrieval and ingestion through an Arrow-based API rather than attempting to replace JDBC/ODBC in all use cases. Hence, ADBC is complementary to those existing standards.
Like Arrow Flight SQL, ADBC is an Arrow-based way to work with databases. However, Flight SQL is a protocol defining a wire format and network transport as opposed to an API specification. Flight SQL requires a database to specifically implement support for it, while ADBC is a client API specification for wrapping existing database protocols which could be Arrow-native or not. Together, ADBC and Flight SQL offer a fully Arrow-native solution for clients and database vendors.
For more about ADBC, see the introductory blog post.
Status
ADBC versions the API standard and the implementing libraries separately.
The API standard (version 1.0.0) is considered stable, but enhancements may be made.
Libraries are under development. For more details, see the documentation, or read the changelog.
Installation
Please see the documentation.
Documentation
The core API definitions can be read in adbc.h.
User documentation can be found at https://arrow.apache.org/adbc
Development and Contributing
For detailed instructions on how to build the various ADBC libraries, see CONTRIBUTING.md.