[
https://issues.apache.org/jira/browse/IMPALA-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384392#comment-17384392
]
ASF subversion and git services commented on IMPALA-10502:
----------------------------------------------------------
Commit 565d0bfa1d12df583ab6d2725ac6ecf2644cd50d in impala's branch
refs/heads/master from Vihang Karajgaonkar
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=565d0bf ]
IMPALA-10502: Fetch events in batches (Addendum)
The earlier change for IMPALA-10502 passes in a batch size
of -1 to fetch all the events from a given event id during a
DDL execution. While this works when HMS backing database is
postgres, it doesn't work well when the HMS backend
is a MySQL database due to HIVE-20226. This change works around the hive
bug to fetch the events in batches of 1000 instead of fetching all the events
in one RPC during the DDL execution.
Testing:
1. Added a unit test for the new changes introduced.
2. Ran the previously failing tests on MySQL HMS backend.
Change-Id: I34bb8984aeb91b37439f77722746f638d8774478
Reviewed-on: http://gerrit.cloudera.org:8080/17698
Reviewed-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Zoltan Borok-Nagy <[email protected]>
Tested-by: Zoltan Borok-Nagy <[email protected]>
> delayed 'Invalidated objects in cache' cause 'Table already exists'
> -------------------------------------------------------------------
>
> Key: IMPALA-10502
> URL: https://issues.apache.org/jira/browse/IMPALA-10502
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog, Clients, Frontend
> Affects Versions: Impala 3.4.0
> Reporter: Adriano
> Assignee: Vihang Karajgaonkar
> Priority: Critical
> Fix For: Impala 4.1
>
>
> In fast paced environment where the interval between the step 1 and 2 is # <
> 100ms (a simplified pipeline looks like):
> 0- catalog 'on demand' in use and disableHmsSync (enabled or disabled: no
> difference)
> 1- open session to coord A -> DROP TABLE X -> close session
> 2- open session to coord A -> CREATE TABLE X-> close session
> Results: the step -2- can fail with table already exist.
> During the internal investigation was discovered that IMPALA-9913 will
> regress the issue in almost all scenarios.
> However considering that the investigation are internally ongoing it is nice
> to have the event tracked also here.
> Once we are sure that IMPALA-9913 fix these events we can close this as
> duplicate, in alternative carry on the investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
