[
https://issues.apache.org/jira/browse/HIVE-28373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18061841#comment-18061841
]
yongzhi.shao commented on HIVE-28373:
-------------------------------------
[~dkuzmenko]
Hello,testTwoClientCommitSameVersion #291
{code}
assertThat(expectedException.get()).isNotNull();
{code}
Theoretically, when two clients attempt to commit the same version, one of them
is bound to throw an exception under normal circumstances; therefore, the code
at line 291 must catch an exception. I have verified all test code locally.
However, I am uncertain whether cross-testcase interference might occur—for
instance, if a residual corrupted catalog file from a previous testcase ends up
affecting the next one.
> Iceberg: Refactor the code of HadoopTableOptions
> ------------------------------------------------
>
> Key: HIVE-28373
> URL: https://issues.apache.org/jira/browse/HIVE-28373
> Project: Hive
> Issue Type: Improvement
> Components: Iceberg integration
> Affects Versions: 4.0.0
> Reporter: yongzhi.shao
> Assignee: yongzhi.shao
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> Since there are a lot of problems with hadoop_catalog, we submitted the
> following PR to the iceberg community:
> [core:Refactor the code of HadoopTableOptions by BsoBird · Pull Request
> #10623 · apache/iceberg
> (github.com)|https://github.com/apache/iceberg/pull/10623]
> With this PR, we can implement atomic operations based on hadoopcatalog.
> But this PR is not accepted by the iceberg community.And it seems that the
> iceberg community is trying to remove support for hadoopcatalog(only for
> testing).
> Since hive itself supports a number of features based on the hadoop_catalog
> table, can we merge this patch in hive?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
