You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/07/12 14:05:02 UTC

[jira] [Assigned] (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 ]

Todd Farmer reassigned ARROW-16023:
-----------------------------------

    Assignee:     (was: David Li)

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [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
>            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.10#820010)