You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2016/07/12 03:23:10 UTC
[jira] [Resolved] (PARQUET-662) [C++] ParquetException must be
explicitly exported in dynamic libraries
[ https://issues.apache.org/jira/browse/PARQUET-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney resolved PARQUET-662.
----------------------------------
Resolution: Fixed
Fix Version/s: cpp-0.1
Issue resolved by pull request 139
[https://github.com/apache/parquet-cpp/pull/139]
> [C++] ParquetException must be explicitly exported in dynamic libraries
> -----------------------------------------------------------------------
>
> Key: PARQUET-662
> URL: https://issues.apache.org/jira/browse/PARQUET-662
> Project: Parquet
> Issue Type: Bug
> Components: parquet-cpp
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Fix For: cpp-0.1
>
>
> This arose in ARROW-237. Because {{parquet::ParquetException}} is header-only, depending on the compiler, 3rd-party libraries may not be able to throw and/or catch exceptions that are recognized as such by all parties (for example, if 3rd-party implements {{parquet::MemoryAllocator}} and needs to throw an exception, it may not be recognized). On gcc this is current working but on LLVM / OS X it is not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)