clarify legacy behavior for DoPutPreparedResult protobuf message

apache · Mar 16, 2024 · 8ddc3c3 · 8ddc3c3
1 parent d4dd713
commit 8ddc3c3
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/format/FlightSql.proto b/format/FlightSql.proto
@@ -1800,8 +1800,8 @@ message DoPutUpdateResult {
 /* An *optional* response returned when `DoPut` is called with `CommandPreparedStatementQuery`.
  *
  * *Note on legacy behavior*: previous versions of the protocol did not return any result for
- * this command, and that behavior should still be supported by clients. See documentation
- * of individual fields for more details on expected client behavior in this case. 
+ * this command, and that behavior should still be supported by clients. In that case, the client
+ * can continue as though the fields in this message were not provided or set to sensible default values.
  */
 message DoPutPreparedStatementResult {
   option (experimental) = true;