Weizisheng created IMPALA-11939:
-----------------------------------
Summary: Catalogd can't process hms event once creating table
contains extra whitespace
Key: IMPALA-11939
URL: https://issues.apache.org/jira/browse/IMPALA-11939
Project: IMPALA
Issue Type: Bug
Components: Catalog
Affects Versions: Impala 3.4.0
Reporter: Weizisheng
Enable Automatic Invalidation/Refresh of Metadata by configuring
hms_event_polling_interval_s.
After creating the table from beeline like: create table `
bi_xxxxxx`.`table_xxxxxx` (...), Catalogd can never process any hms event.
I0222 11:10:19.478662 7554 MetastoreEventsProcessor.java:482] Received 1
events. Start event id : 1524439
I0222 11:10:19.478921 7554 MetastoreEvents.java:233] Total number of events
received: 1 Total number of events filtered out: 0
E0222 11:10:19.479373 7554 MetastoreEventsProcessor.java:527] Unexpected
exception received while processing event
Java exception follows:
org.apache.impala.catalog.events.MetastoreNotificationException: EventId:
1524440 EventType: CREATE_TABLE Unable to add table while processing for table
bi_xxxxxx.table_xxxxxx because the database doesn't exist. This could be due to
a previous error while processing CREATE_DATABASE event for the database
bi_xxxxxx
at
org.apache.impala.catalog.events.MetastoreEvents$CreateTableEvent.process(MetastoreEvents.java:691)
at
org.apache.impala.catalog.events.MetastoreEvents$MetastoreEvent.processIfEnabled(MetastoreEvents.java:311)
at
org.apache.impala.catalog.events.MetastoreEventsProcessor.processEvents(MetastoreEventsProcessor.java:615)
at
org.apache.impala.catalog.events.MetastoreEventsProcessor.processEvents(MetastoreEventsProcessor.java:513)
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)
Caused by: org.apache.impala.catalog.CatalogException: Db bi_xxxxxx does not
exist
at
org.apache.impala.catalog.CatalogServiceCatalog.addTableIfNotExists(CatalogServiceCatalog.java:1741)
at
org.apache.impala.catalog.events.MetastoreEvents$CreateTableEvent.process(MetastoreEvents.java:682)
... 10 more
E0222 11:10:19.479483 7554 MetastoreEventsProcessor.java:637] Notification
event is nullW0222 11:10:22.479734 7554 MetastoreEventsProcessor.java:506]
Event processing is skipped since status is ERROR. Last synced event id is
1524439
...
I0222 11:10:36.083668 13444 CatalogServiceCatalog.java:2142] Invalidating table
metadata: bi_xxxxxx.table_xxxxxx2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
