[
https://issues.apache.org/jira/browse/IMPALA-12448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812589#comment-17812589
]
ASF subversion and git services commented on IMPALA-12448:
----------------------------------------------------------
Commit 00247c26e2a73d4ece4962be6fd5078843d938ae in impala's branch
refs/heads/master from ttttttz
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=00247c26e ]
IMPALA-12448: Avoid getting stuck when refreshing a non-existent partition
In some cases, we shouldn't wait for the catalog version of 'result'
because the table version has not changed after resetting metadata,
such as refreshing a non-existent partition. If not, the query may be
stuck for a long time. If the catalog version of 'result' is less
than or equal to 'oldestTopicUpdateToGc_', return the catalog version
of 'result' directly.
Tests:
* added e2e tests
Change-Id: Iace7cdadda300b03896f92415822266354421887
Reviewed-on: http://gerrit.cloudera.org:8080/20490
Reviewed-by: Quanlong Huang <huangquanl...@gmail.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> Refreshing a non-existent partition may be stuck for a long time
> -----------------------------------------------------------------
>
> Key: IMPALA-12448
> URL: https://issues.apache.org/jira/browse/IMPALA-12448
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 4.2.0
> Reporter: Zhi Tang
> Assignee: Zhi Tang
> Priority: Major
> Attachments: image-2023-09-14-11-23-55-517.png
>
>
> When sync_ddl is set to true, refreshing a non-existent partition may be
> stuck for a long time until the table has a new update log added to
> topicUpdateLog_.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
