[IMPALA-9052] Events processor goes into error state if there are events on blacklisted db or table

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 3.4.0
• Epic Color: ghx-label-6
• Assignee: Vihang Karajgaonkar
• Reporter: Vihang Karajgaonkar
• Created: 15/Oct/19 22:43
• Updated: 16/Dec/19 23:27
• Resolved: 04/Nov/19 23:15

Description

IMPALA-8797 introduces a configuration to blacklist certain databases and tables so that Catalog never loads them. However, if there are new events generated on such database or tables, the Events Processor tries to process them. This causes events processor to go into error state (eg. when adding a table in a blacklisted db). Also, it nullifies the purpose of the configuration if Events processor is able to add/remove/refresh the tables on such database or tables.

Issue Links

• causes: IMPALA-9257 Events processor last synced event does not advance if all the events are filtered out
• is related to: IMPALA-8797 Blacklist "sys" and "information_schema" databases from Hive