[
https://issues.apache.org/jira/browse/ARROW-17199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Li updated ARROW-17199:
-----------------------------
Description:
There are a number of small bugs in the Java Flight SQL example (e.g. binding
parameters to the wrong index, not handling null parameter values, not properly
reporting errors, things throwing SQLException that should use Arrow/general
Java exceptions) that should be fixed.
Also, CommandPreparedStatementQuery is implemented wrong in both C++ and Java
servers: only the last parameter value will be bound/executed when executing a
prepared statement that returns a result set. But this contradicts the spec,
which states "All of the bound parameter sets will be executed as a single
atomic execution". The server(s) need to cache the uploaded Arrow data and
execute using all input rows.
was:
There are a number of small bugs in the Java Flight SQL example (e.g. binding
parameters to the wrong index, not handling null parameter values, not properly
reporting errors) that should be fixed.
Also, CommandPreparedStatementQuery is implemented wrong in both C++ and Java
servers: only the last parameter value will be bound/executed when executing a
prepared statement that returns a result set. But this contradicts the spec,
which states "All of the bound parameter sets will be executed as a single
atomic execution". The server(s) need to cache the uploaded Arrow data and
execute using all input rows.
> [FlightRPC][C++][Java] Fix example Flight SQL servers
> -----------------------------------------------------
>
> Key: ARROW-17199
> URL: https://issues.apache.org/jira/browse/ARROW-17199
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, FlightRPC, Java
> Reporter: David Li
> Assignee: David Li
> Priority: Major
>
> There are a number of small bugs in the Java Flight SQL example (e.g. binding
> parameters to the wrong index, not handling null parameter values, not
> properly reporting errors, things throwing SQLException that should use
> Arrow/general Java exceptions) that should be fixed.
> Also, CommandPreparedStatementQuery is implemented wrong in both C++ and Java
> servers: only the last parameter value will be bound/executed when executing
> a prepared statement that returns a result set. But this contradicts the
> spec, which states "All of the bound parameter sets will be executed as a
> single atomic execution". The server(s) need to cache the uploaded Arrow data
> and execute using all input rows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
