[ https://issues.apache.org/jira/browse/IMPALA-11735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848916#comment-17848916 ]
ASF subversion and git services commented on IMPALA-11735: ---------------------------------------------------------- Commit 9672312015be959360795a8af0843fdf386b557c in impala's branch refs/heads/master from Sai Hemanth Gantasala [ https://gitbox.apache.org/repos/asf?p=impala.git;h=967231201 ] IMPALA-11735: Handle CREATE_TABLE event when the db is invisible to the impala server user It's possible that some dbs are invisible to Impala cluster due to authorization restrictions. However, the CREATE_TABLE events in such dbs will lead the event-processor into ERROR state. Event processor should ignore such CREAT_TABLE events when database is not found. note: This is an incorrect setup, where 'impala' super user is denied access on the metadata object database but given access to fetch events from notification log table of metastore. Testing: - Manually verified this on local cluster. - Added automated unit test to verify the same. Change-Id: I90275bb8c065fc5af61186901ac7e9839a68c43b Reviewed-on: http://gerrit.cloudera.org:8080/21188 Reviewed-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com> > Handle CREATE_TABLE event when the db is invisible to the impala server user > ---------------------------------------------------------------------------- > > Key: IMPALA-11735 > URL: https://issues.apache.org/jira/browse/IMPALA-11735 > Project: IMPALA > Issue Type: Bug > Reporter: Quanlong Huang > Assignee: Sai Hemanth Gantasala > Priority: Critical > > It's possible that some dbs are invisible to Impala cluster due to > authorization restrictions. However, the CREATE_TABLE events in such dbs will > lead the event-processor into ERROR state: > {noformat} > E1026 03:02:30.650302 116774 MetastoreEventsProcessor.java:684] Unexpected > exception received while processing event > Java exception follows: > org.apache.impala.catalog.events.MetastoreNotificationException: EventId: > 184240416 EventType: CREATE_TABLE Unable to process event > at > org.apache.impala.catalog.events.MetastoreEvents$CreateTableEvent.process(MetastoreEvents.java:735) > at > org.apache.impala.catalog.events.MetastoreEvents$MetastoreEvent.processIfEnabled(MetastoreEvents.java:345) > at > org.apache.impala.catalog.events.MetastoreEventsProcessor.processEvents(MetastoreEventsProcessor.java:772) > at > org.apache.impala.catalog.events.MetastoreEventsProcessor.processEvents(MetastoreEventsProcessor.java:670) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > E1026 03:02:30.650447 116774 MetastoreEventsProcessor.java:795] Notification > event is null > {noformat} > It should be handled (e.g. ignored) and reported to the admin (e.g. in logs). -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org