You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@orc.apache.org by "Deepak Majeti (JIRA)" <ji...@apache.org> on 2017/11/07 20:16:01 UTC

[jira] [Updated] (ORC-196) [C++] Rename ParseError to OrcException and use it in both read and write paths

     [ https://issues.apache.org/jira/browse/ORC-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Deepak Majeti updated ORC-196:
------------------------------
    Summary: [C++] Rename ParseError to OrcException and use it in both read and write paths  (was: [C++] Rename ParseError to OrcError and use it in both read and write paths)

> [C++] Rename ParseError to OrcException and use it in both read and write paths
> -------------------------------------------------------------------------------
>
>                 Key: ORC-196
>                 URL: https://issues.apache.org/jira/browse/ORC-196
>             Project: ORC
>          Issue Type: Bug
>          Components: C++
>            Reporter: Deepak Majeti
>            Assignee: Deepak Majeti
>
> The current ParseError exception type used in the read-path does not fit well in the write-path. The scope of this JIRA is to rename this to OrcException and use it throughout the C++ code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)