[
https://issues.apache.org/jira/browse/IMPALA-11324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543033#comment-17543033
]
Riza Suminto commented on IMPALA-11324:
---------------------------------------
Rather than PK conflict, I think we can change the test to cause column
constraint violation instead. That way it won't be affected by
kudu_ignore_conflicts flag.
> TestRPCTimeout::test_reportexecstatus_retries broken
> ----------------------------------------------------
>
> Key: IMPALA-11324
> URL: https://issues.apache.org/jira/browse/IMPALA-11324
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.2.0
> Reporter: Wenzhe Zhou
> Assignee: Riza Suminto
> Priority: Major
> Labels: broken-build
>
> custom_cluster/test_rpc_timeout.py::TestRPCTimeout::test_reportexecstatus_retries
> was broken in nightly build.
> Recent merged patch https://gerrit.cloudera.org/#/c/18536/ changed default
> behavior for Kudu to ignore conflicts and return different error messages for
> duplicated keys.
> To fix it, set kudu_ignore_conflicts as false for the test case.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
