[GitHub] [arrow-adbc] lidavidm opened a new issue, #507: python/adbc_driver_manager,go/adbc/driver/flightsql: improve error code mapping

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

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

   Based on this diagram:
   
   <details>
   
   ![image](https://user-images.githubusercontent.com/327919/224376382-5e02ed50-8734-4e96-b8df-0b2c4cece912.png)
   
   </details>
   
   In the Flight SQL driver:
   - gRPC RESOURCE_EXHAUSTED should map to ADBC INTERNAL
   - gRPC DATA_LOSS should map to ADBC IO 
   
   In the Python driver manager:
   - UNKNOWN should map to OperationalError ("errors that are related to the database’s operation and not necessarily under the control of the programmer")
   
   And we may want to add Flight codes for some of those gRPC codes. (And figure out how INVALID_DATA and INVALID_STATE should be generated via Flight.)


-- 
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-adbc] lidavidm closed issue #507: python/adbc_driver_manager: improve error code mapping

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

lidavidm closed issue #507: python/adbc_driver_manager: improve error code mapping
URL: https://github.com/apache/arrow-adbc/issues/507


-- 
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

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