You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "David Li (Jira)" <ji...@apache.org> on 2022/03/24 20:11:00 UTC

[jira] [Updated] (ARROW-16023) [FlightRPC][Python] Differentiate between intentional and unintentional errors in server RPC handlers

     [ https://issues.apache.org/jira/browse/ARROW-16023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Li updated ARROW-16023:
-----------------------------
    Summary: [FlightRPC][Python] Differentiate between intentional and unintentional errors in server RPC handlers  (was: [FlightRPC][Python] Differentiate between intentional and unintentional errors in C++/Python APIs)

> [FlightRPC][Python] Differentiate between intentional and unintentional errors in server RPC handlers
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-16023
>                 URL: https://issues.apache.org/jira/browse/ARROW-16023
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: FlightRPC, Python
>            Reporter: David Li
>            Assignee: David Li
>            Priority: Major
>
> Right now, in Python, to signal an error to the client, you raise an exception. But some exceptions are unintentional, and for development/monitoring purposes, it would be good to log them. There's no way to differentiate between the two.
> ARROW-15909 tries to log some exceptions and filter out ones that would just be noise, but a better long-term solution would be to mimic gRPC/Java and provide an error callback to explicitly signal that we want to raise an error.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)