This is an automated email from the ASF dual-hosted git repository.
apitrou pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow-site.git
The following commit(s) were added to refs/heads/master by this push:
new 4cca084 ARROW-11911: [FOLLOWUP] Clarify relationship between Arrow
and Protobuf in Flight
4cca084 is described below
commit 4cca08446115701812dbec56425a611406e0c668
Author: Wes McKinney <[email protected]>
AuthorDate: Wed Apr 21 16:45:45 2021 +0200
ARROW-11911: [FOLLOWUP] Clarify relationship between Arrow and Protobuf in
Flight
How the `FlightData` handling works in Flight implementations is a bit
outside the scope of a FAQ document like this, but this at least clarifies that
Flight does not serialize the data itself (only a binary blob is passed by
Flight) using Protobuf.
Closes #102 from wesm/ARROW-11911-followup and squashes the following
commits:
f88d43614 <Wes McKinney> Clarify protobuf relationship in Arrow Flight
Authored-by: Wes McKinney <[email protected]>
Signed-off-by: Antoine Pitrou <[email protected]>
---
faq.md | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/faq.md b/faq.md
index 146984b..946c221 100644
--- a/faq.md
+++ b/faq.md
@@ -229,12 +229,13 @@ generated C# code is not going to have the same
representation as one that has
been deserialized by protoc generated Java code. You would need to marshal
the data from one language to the other.
-Arrow avoids this but it comes at the cost of increased space. Protobuf can
-be a better choice for serializing certain kinds of data on the wire (like
-individual records or sparse data with many optional fields). Just like
-Parquet this means that Arrow and Protobuf complement each other well. For
-example, Arrow Flight uses gRPC and Protobuf to transmit data which is then
-deserialized into Arrow format for processing.
+Arrow avoids this but it comes at the cost of increased space.
+Protobuf can be a better choice for serializing certain kinds of data
+on the wire (like individual records or sparse data with many optional
+fields). Just like Parquet this means that Arrow and Protobuf
+complement each other well. For example, Arrow Flight uses gRPC and
+Protobuf to serialize its commands, while data is serialized using the
+binary Arrow IPC protocol.
#### **How does Arrow relate to Flatbuffers?**
