impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimitris Tsirogiannis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-5318) Impala does not always generated fully qualified table names in audit events
Date Mon, 15 May 2017 16:58:04 GMT

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

Dimitris Tsirogiannis resolved IMPALA-5318.
-------------------------------------------
    Resolution: Fixed

Change-Id: Icd63f7e4accc7fda9719e13059fa8d432981618a
Reviewed-on: http://gerrit.cloudera.org:8080/6879
Reviewed-by: Alex Behm <alex.behm@cloudera.com>
Tested-by: Impala Public Jenkins
---
M fe/src/main/java/org/apache/impala/analysis/DropTableOrViewStmt.java
M fe/src/main/java/org/apache/impala/analysis/TableDef.java
M fe/src/test/java/org/apache/impala/analysis/AuditingTest.java
3 files changed, 16 insertions(+), 3 deletions(-)

Approvals:
  Impala Public Jenkins: Verified
  Alex Behm: Looks good to me, approved


> Impala does not always generated fully qualified table names in audit events
> ----------------------------------------------------------------------------
>
>                 Key: IMPALA-5318
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5318
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>            Reporter: Dimitris Tsirogiannis
>            Assignee: Dimitris Tsirogiannis
>
> Impala sometimes will generate an entry in the audit log that doesn't contain fully qualified
table names, thereby breaking Navigator as it always expects fully qualified names. 
> To reproduce: 
> {code}
> hive> create table foo (a int, b date) stored as avro; <--- table that can't be
loaded in Impala and results in a TableLoadingException
> impala> invalidate table foo;
> impala> drop table foo;
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message