[jira] [Resolved] (IMPALA-4663) Systematically catch exceptions

["Tim Armstrong (Jira)" <ji...@apache.org>]

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

Tim Armstrong resolved IMPALA-4663.
-----------------------------------
    Resolution: Later

> Systematically catch exceptions
> -------------------------------
>
>                 Key: IMPALA-4663
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4663
>             Project: IMPALA
>          Issue Type: Task
>          Components: Backend
>    Affects Versions: Impala 2.8.0
>            Reporter: Jim Apple
>            Priority: Major
>
> IMPALA-4498 showed a case where catching exceptions could have provided a mroe graceful exit. Unfortunately, both Boost and the C++ standard library use exceptions for error handling while Impala uses things like Status.
> We should audit the code for places where uncaught exceptions may occur and wrap them with {{try ... catch}} when appropriate.
> It would be nice if there were some static analysis tooling to help with this, but I'm not sure any such thing exists at the moment. It may be that the best possible would be line-by-line (or method-by-method) audit, which could be very time-consuming.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)