You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Benjamin Kietzman (JIRA)" <ji...@apache.org> on 2018/12/17 13:44:00 UTC

[jira] [Comment Edited] (ARROW-4036) [C++] Make status codes pluggable

    [ https://issues.apache.org/jira/browse/ARROW-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722983#comment-16722983 ] 

Benjamin Kietzman edited comment on ARROW-4036 at 12/17/18 1:43 PM:
--------------------------------------------------------------------

I like that. In that case would it still be useful to define StatusCodes? We could define subclasses for each error condition

To avoid copy construction/virtual destructor calls when a status is copied, we could by make ErrorState ref counted


was (Author: bkietz):
I like that. In that case would it still be useful to define StatusCodes? We could define subclasses for each error condition

> [C++] Make status codes pluggable
> ---------------------------------
>
>                 Key: ARROW-4036
>                 URL: https://issues.apache.org/jira/browse/ARROW-4036
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>    Affects Versions: 0.11.1
>            Reporter: Antoine Pitrou
>            Priority: Major
>
> Currently we're defining all Status codes in the Arrow base library, even those pertaining to sub-libraries such as arrow_python, plasma, gandiva, etc. We should try to devise some kind of simple registry system to avoid centralizing those.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)