[
https://issues.apache.org/jira/browse/IMPALA-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805754#comment-17805754
]
ASF subversion and git services commented on IMPALA-10502:
----------------------------------------------------------
Commit 32b29ff36fb3e05fd620a6714de88805052d0117 in impala's branch
refs/heads/master from Venu Reddy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=32b29ff36 ]
IMPALA-12356: Fix first ALTER_PARTITION event from Hive could be
treated as self event
Self event check for add partition event is done only for the
transactional tables with IMPALA-10502 (commit id: 7f7a631). But
during addition of new partition(with insert statement), catalog
service id and version number are added to partition params of the
parition irrespective of whether the table is transactional or not.
Thus the version number is added to partition's inFlightEvents_ and
remained in it until the next alter partition event from hive. Thus
led to detection of the alter partition event as self event.
This commit ensures the catalog service id and version number are not
added to partition params if the partition is added to a
non-transactional table.
Also fixed another bug in reload event. Reload event self check
fails due to the above fix as it expects catalog service id and
version number in the partition params. Fixed to use last refreshed
event id to skip the self reload events.
Testing:
- Manually tested in cluster and added testcases
Change-Id: I23c2affa3fe32c0b3843bff5e4c0018dce9060d3
Reviewed-on: http://gerrit.cloudera.org:8080/20486
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[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.0
>
>
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
