You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@arrow.apache.org by li...@apache.org on 2024/06/28 08:26:15 UTC
(arrow) branch main updated: MINOR: [Docs] Update alignment to center for ADBC documentation (#43081)
This is an automated email from the ASF dual-hosted git repository.
lidavidm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow.git
The following commit(s) were added to refs/heads/main by this push:
new a42df4baf0 MINOR: [Docs] Update alignment to center for ADBC documentation (#43081)
a42df4baf0 is described below
commit a42df4baf09f9b4d168c5ad5139003ed7bdf2246
Author: Hyunseok Seo <hs...@gmail.com>
AuthorDate: Fri Jun 28 17:26:09 2024 +0900
MINOR: [Docs] Update alignment to center for ADBC documentation (#43081)
### Rationale for this change
Update alignment to center in specification for ADBC
### What changes are included in this PR?
Update alignment to some content.
### Are these changes tested?
Yes. I have verified the changes by building the documentation.
### Are there any user-facing changes?
Yes. the updated documentation will be visible to users.
Authored-by: Hyunseok Seo <hs...@gmail.com>
Signed-off-by: David Li <li...@gmail.com>
---
docs/source/format/ADBC.rst | 38 +++++++++++++++++++-------------------
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/docs/source/format/ADBC.rst b/docs/source/format/ADBC.rst
index 41aa08ddbf..c11bba8f8c 100644
--- a/docs/source/format/ADBC.rst
+++ b/docs/source/format/ADBC.rst
@@ -188,25 +188,25 @@ bypass this wrapper.
.. figure:: ./ADBCQuadrants.svg
- ADBC, JDBC, and ODBC are database-agnostic. They define the
- API that the application uses, but not how that API is implemented,
- instead deferring to drivers to fulfill requests using the protocol
- of their choice. JDBC and (generally) ODBC offer results in a
- row-oriented format, while ADBC offers columnar Arrow data.
-
- Protocols/libraries like libpq (Postgres) and TDS (SQL Server) are
- database-specific and row-oriented. Multiple databases may
- implement the same protocol to try to reuse each other's work,
- e.g. several databases implement the Postgres wire protocol to
- benefit from its driver implementations. But the protocol itself
- was not designed with multiple databases in mind, nor are the
- protocols generally meant to be used directly by applications.
-
- Some database-specific protocols are Arrow-native, like those of
- BigQuery and ClickHouse. Flight SQL additionally is meant to be
- database-agnostic, but it defines both the client-facing API and
- the underlying protocol, so it's hard for applications to use it as
- the API for databases that don't already implement Flight SQL.
+ADBC, JDBC, and ODBC are database-agnostic. They define the
+API that the application uses, but not how that API is implemented,
+instead deferring to drivers to fulfill requests using the protocol
+of their choice. JDBC and (generally) ODBC offer results in a
+row-oriented format, while ADBC offers columnar Arrow data.
+
+Protocols/libraries like libpq (Postgres) and TDS (SQL Server) are
+database-specific and row-oriented. Multiple databases may
+implement the same protocol to try to reuse each other's work,
+e.g. several databases implement the Postgres wire protocol to
+benefit from its driver implementations. But the protocol itself
+was not designed with multiple databases in mind, nor are the
+protocols generally meant to be used directly by applications.
+
+Some database-specific protocols are Arrow-native, like those of
+BigQuery and ClickHouse. Flight SQL additionally is meant to be
+database-agnostic, but it defines both the client-facing API and
+the underlying protocol, so it's hard for applications to use it as
+the API for databases that don't already implement Flight SQL.
Existing database client APIs
-----------------------------