Skip to content

Commit

Permalink
clarify usage of the updated statement handle
Browse files Browse the repository at this point in the history
  • Loading branch information
erratic-pattern committed Mar 4, 2024
1 parent d4a30c1 commit b52d0b4
Showing 1 changed file with 10 additions and 4 deletions.
14 changes: 10 additions & 4 deletions format/FlightSql.proto
Original file line number Diff line number Diff line change
Expand Up @@ -1801,11 +1801,17 @@ message DoPutUpdateResult {
message DoPutPreparedStatementResult {
option (experimental) = true;

// (potentially updated) opaque handle for the prepared statement on the server.
// All subsequent requests for this prepared statement must use this new handle, if specified.
// Represents a (potentially updated) opaque handle for the prepared statement on the server.
// Because the handle could potentially be updated, any previous handles for this prepared
// statement should be considered invalid, and all subsequent requests for this prepared
// statement must use this new handle, if specified.
//
// The updated handle allows implementing query parameters with stateless services
// as described in https://github.com/apache/arrow/issues/37720
bytes prepared_statement_handle = 1;
// as described in https://github.com/apache/arrow/issues/37720.
// Previously this command did not return any updated handle, and that behavior should still be supported
// by clients. When the server does not provide any handle in this response, clients should contiue
// using the previous handle provided by `ActionCreatePreparedStatementResonse`.
optional bytes prepared_statement_handle = 1;
}

/*
Expand Down

0 comments on commit b52d0b4

Please sign in to comment.