[
https://issues.apache.org/jira/browse/PARQUET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108910#comment-15108910
]
Aliaksei Sandryhaila commented on PARQUET-440:
----------------------------------------------
+1 for keeping exceptions. They provide a standard interface for applications
that use parquet-cpp; with status objects, the apps would need to understand
these objects, and that's not good OOD.
> 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)
