cisaacson opened a new issue, #6967:
URL: https://github.com/apache/arrow-rs/issues/6967
**Which part is this question about**
Flight SQL Server client interaction when the client calls `execute_query`
**Describe your question**
We have a flight sql server implementation that is properly returning an
error from `get_flight_info_statement`:
```rust
let my_struct = MyStruct::create(&sql, ctx).await
.map_err(|e| {
log::error!("Error creating MyStruct: e: {}", e);
status!("Error creating MyStruct: e: ", e) // An error is
happening here, returns immediately
})?;
```
The error from the server is returned immediately.
On the client side we are calling:
```rust
let flight_info = self.inner.execute(sql.to_string(), None).await //
This call hangs
.map_err(|e| {
log::error!("execute error: {}", e.to_string());
anyhow!("execute error: {}", e.to_string())
})?;
```
This hangs and them we get a timeout error:
```
execute error: Ipc error: Status { code: Cancelled, message: "Timeout
expired", source: Some(tonic::transport::Error(Transport, TimeoutExpired(()))) }
```
This is getting into the `inner.execute` fn, `inner` is the
`FlightSqlServiceClient<Channel>`.
We have other types of errors that return fine, any ideas on why this would
occur?
Any help appreciated.
**Additional context**
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
