From 86f4789ab26d9048a8be6263354745a37bd9131d Mon Sep 17 00:00:00 2001
From: David Li <li.davidm96@gmail.com>
Date: Tue, 9 Apr 2019 14:08:17 -0400
Subject: [PATCH] Add application metadata field to FlightData message

---
 format/Flight.proto | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/format/Flight.proto b/format/Flight.proto
index 7f0488b86c39a..f82a7e524503b 100644
--- a/format/Flight.proto
+++ b/format/Flight.proto
@@ -77,7 +77,7 @@ service FlightService {
    * number. In the latter, the service might implement a 'seal' action that
    * can be applied to a descriptor once all streams are uploaded.
    */
-  rpc DoPut(stream FlightData) returns (PutResult) {}
+  rpc DoPut(stream FlightData) returns (stream PutResult) {}
 
   /*
    * Flight services can support an arbitrary number of simple actions in
@@ -285,6 +285,11 @@ message FlightData {
    */
   bytes data_header = 2;
 
+  /*
+   * Application-defined metadata.
+   */
+  bytes data_app_metadata = 3;
+
   /*
    * The actual batch of Arrow data. Preferably handled with minimal-copies
    * coming last in the definition to help with sidecar patterns (it is
@@ -295,7 +300,8 @@ message FlightData {
 }
 
 /**
- * The response message (currently empty) associated with the submission of a
- * DoPut.
+ * The response message associated with the submission of a DoPut.
  */
-message PutResult {}
+message PutResult {
+  bytes data_app_metadata = 1;
+}