You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Bharathkrishna Guruvayoor Murali (JIRA)" <ji...@apache.org> on 2019/04/16 21:01:00 UTC
[jira] [Created] (IMPALA-8426) Logging error in DROP_TABLE event
processing.
Bharathkrishna Guruvayoor Murali created IMPALA-8426:
--------------------------------------------------------
Summary: 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
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-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org