You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/12/10 09:51:00 UTC

[jira] [Updated] (HIVE-24516) Txnhandler onrename might ignore exceptions

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

ASF GitHub Bot updated HIVE-24516:
----------------------------------
    Labels: pull-request-available  (was: )

> Txnhandler onrename might ignore exceptions
> -------------------------------------------
>
>                 Key: HIVE-24516
>                 URL: https://issues.apache.org/jira/browse/HIVE-24516
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>            Reporter: Peter Varga
>            Assignee: Peter Varga
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This is a followup on HIVE-24193. Table not exists errors shouldn't be ignored in the first place.
> {code}
> } catch (SQLException e) {
>         LOG.debug("Going to rollback: " + callSig);
>         rollbackDBConn(dbConn);
>         checkRetryable(dbConn, e, callSig);
>         if (e.getMessage().contains("does not exist")) {
>           LOG.warn("Cannot perform " + callSig + " since metastore table does not exist");
>         } else {
>           throw new MetaException("Unable to " + callSig + ":" + StringUtils.stringifyException(e));
>         }
>       }
> {code}
> This error handling might have been put there for backard compatibility for missing acid metadata tables, but this is not needed anymore.



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