[
https://issues.apache.org/jira/browse/IMPALA-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharathkrishna Guruvayoor Murali updated IMPALA-8426:
-----------------------------------------------------
Priority: Minor (was: Major)
> Logging error in DROP_TABLE event processing.
> ---------------------------------------------
>
> Key: IMPALA-8426
> URL: https://issues.apache.org/jira/browse/IMPALA-8426
> Project: IMPALA
> Issue Type: Bug
> Reporter: Bharathkrishna Guruvayoor Murali
> Assignee: Bharathkrishna Guruvayoor Murali
> Priority: Minor
>
> We have the following logging code in DROP_TABLE process() method, here
> always the first condition is triggered and the second will never be matched.
> So we should switch the order of the conditions.
> {code:java}
> if (!tblMatched.getRef()) {
> LOG.warn(debugString("Table %s was not removed from "
> + "catalog since the creation time of the table did not match", tblName_));
> } else if (!tblWasFound.getRef()) {
> debugLog("Table {} was not removed since it did not exist in catalog.",
> tblName_);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
