This is an automated email from the ASF dual-hosted git repository.
lidavidm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow.git
The following commit(s) were added to refs/heads/main by this push:
new 2cd5ad233f GH-49497: [FlightRPC] Add is_update field to
ActionCreatePreparedStatementResult (#49498)
2cd5ad233f is described below
commit 2cd5ad233fab33e693b4e764db0d45ca52e93ea0
Author: Pedro Matias <[email protected]>
AuthorDate: Tue Jun 9 04:48:26 2026 +0100
GH-49497: [FlightRPC] Add is_update field to
ActionCreatePreparedStatementResult (#49498)
### Rationale for this change
Multiple database driver APIs have functions that allow for executing
prepared statements that can be either result set generating queries or update
commands. Before this PR, there was no way for servers to indicate whether the
query should be executed with `CommandPreparedStatementUpdate` or
`CommandPreparedStatementQuery`.
### What changes are included in this PR?
The change in this PR introduces a new field set by the server after
creation of the prepared statement to indicate the proper network flow.
### Are these changes tested?
No, because these changes are best tested using a database driver but this
PR includes only changes to the proto definition.
### Are there any user-facing changes?
No.
* GitHub Issue: #49497
Authored-by: Pedro Matias <[email protected]>
Signed-off-by: David Li <[email protected]>
---
format/FlightSql.proto | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/format/FlightSql.proto b/format/FlightSql.proto
index 90e6e5baeb..ea55dcef5a 100644
--- a/format/FlightSql.proto
+++ b/format/FlightSql.proto
@@ -1550,6 +1550,11 @@ message ActionCreatePreparedStatementResult {
// If the query provided contained parameters, parameter_schema contains the
// schema of the expected parameters. It should be an IPC-encapsulated
Schema, as described in Schema.fbs.
bytes parameter_schema = 3;
+
+ // When set to true, the query should be executed with
CommandPreparedStatementUpdate,
+ // when set to false, the query should be executed with
CommandPreparedStatementQuery.
+ // If not set, the client can choose how to execute the query.
+ optional bool is_update = 4;
}
/*
