@@ -33,13 +33,13 @@ than for data science.
3333### Arrow-native
3434
3535Ballista uses the Apache Arrow memory format during query execution, and Apache Arrow IPC format on disk for
36- shuffle files and for exchanging data between executors. Queries can be submitted using the Arrow Flight SQL API
37- and the Arrow Flight SQL JDBC Driver .
36+ shuffle files and for exchanging data between executors. Queries can be submitted from Rust and Python clients
37+ or the Ballista CLI .
3838
3939### Language Agnostic
4040
4141Although most of the implementation code is written in Rust, the scheduler and executor APIs are based on open
42- standards, including protocol buffers, gRPC, Apache Arrow IPC, and Apache Arrow Flight SQL .
42+ standards, including protocol buffers, gRPC, Apache Arrow IPC, and Apache Arrow Flight.
4343
4444This language agnostic approach will allow Ballista to eventually support UDFs in languages other than Rust,
4545including Wasm.
@@ -72,7 +72,6 @@ between the executor(s) and the scheduler for fetching tasks and reporting task
7272The scheduler provides the following interfaces:
7373
7474- gRPC service for submitting and managing jobs
75- - Flight SQL API
7675- REST API for monitoring jobs
7776
7877Jobs are submitted to the scheduler's gRPC service from a client context, either in the form of a logical query
@@ -96,8 +95,6 @@ There are multiple clients available for submitting jobs to a Ballista cluster:
9695 context with support for SQL and DataFrame operations.
9796- The [ ballista crate] ( https://crates.io/crates/ballista ) provides a native Rust session context with support for
9897 SQL and DataFrame operations.
99- - The [ Flight SQL JDBC driver] ( https://arrow.apache.org/docs/java/flight_sql_jdbc_driver.html ) can be used from
100- popular SQL tools to execute SQL queries against a cluster.
10198
10299## Distributed Query Scheduling
103100
0 commit comments