[
https://issues.apache.org/jira/browse/PARQUET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108898#comment-15108898
]
Wes McKinney commented on PARQUET-440:
--------------------------------------
I did a little bit of digging, and at least from a Python perspective there's a
fairly straightforward way to catch and translate C++ exceptions raised out of
a thirdparty library, but it is strictly more difficult. Most of my
interactions with libparquet are going to be in C++ anyway, so these exceptions
likely won't bubble up to the Python side very often. I am fine with either
decision if it's for the overall benefit of parquet-cpp internally.
> Error handling: C++ exceptions or Status
> ----------------------------------------
>
> Key: PARQUET-440
> URL: https://issues.apache.org/jira/browse/PARQUET-440
> Project: Parquet
> Issue Type: New Feature
> Components: parquet-cpp
> Reporter: Wes McKinney
>
> This library currently throws C++ exceptions. I would very much prefer to use
> Google's convention of using Status objects to communicate errors and force
> explicit action to be taken on the part of the developer if an error occurs
> in a particular function call. It will also make it much easier to
> incorporate libparquet into other libraries that do not use C++ exceptions,
> and also to provide an ANSI C API wrapper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
