[jira] [Commented] (IMPALA-2423) Concurrent operations on the same partitioned table may cause stale partition metadata

["David Knupp (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640884#comment-16640884 ] 

David Knupp commented on IMPALA-2423:
-------------------------------------

[~vukercegovac] -- I think I have a test that will semi-reliably produce this error.


> Concurrent operations on the same partitioned table may cause stale partition metadata
> --------------------------------------------------------------------------------------
>
>                 Key: IMPALA-2423
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2423
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>    Affects Versions: Impala 2.2.4, Impala 2.3.0
>            Reporter: Dimitris Tsirogiannis
>            Priority: Major
>              Labels: catalog-server
>
> The following operations, when being executed concurrently on the same partitioned table, may cause stale partition metadata. 
> {code}
> Query: insert OVERWRITE part_table partition (id='1') SELECT * from table where id = 1;
> Inserted 4205565 row(s) in 8.50s
> Query: alter TABLE part_table PARTITION (id='1') SET tblproperties('numRows'='3604700', 'STATS_GENERATED_VIA_STATS_TASK' ='true')
> ERROR: AnalysisException: Partition spec does not exist: (id='1').
> {code}
> The operations are executed on the same impalad node and every INSERT, ALTER TABLE sequence is targeting a different partition. The problem appears with 10-20 concurrent operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org