[GitHub] [arrow] lidavidm opened a new issue, #34596: [C++][FlightRPC] Flight SQL: make it easier for servers to handle unrecognized messages

["lidavidm (via GitHub)" <gi...@apache.org>]

lidavidm opened a new issue, #34596:
URL: https://github.com/apache/arrow/issues/34596

   ### Describe the enhancement requested
   
   Particularly for DoGet, the implementor may want to use a completely custom Ticket value. But right now the Flight SQL server will error if you don't use a value it recognizes. Ideally it could pass this on to a user-defined handler that could respond.
   
   ### Component(s)
   
   C++, FlightRPC


-- 
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: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow] lidavidm commented on issue #34596: [C++][FlightRPC] Flight SQL: make it easier for servers to handle unrecognized messages

["lidavidm (via GitHub)" <gi...@apache.org>]

lidavidm commented on issue #34596:
URL: https://github.com/apache/arrow/issues/34596#issuecomment-1472728026

   Also, DoGet is declared final in FlightSqlServerBase so you're unable to fix this yourself


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org