合并受阻
当前仓库存在以下 保护分支 :
| Protected Branch | Version | Release |
|---|---|---|
| * master | 3.5.0 | 4 |
| openEuler-20.03-LTS-SP4 | 3.2.0 | 2 |
| openEuler-22.03-LTS-SP1 | 3.2.2 | 1 |
| openEuler-22.03-LTS-SP3 | 3.2.2 | 1 |
| openEuler-22.03-LTS-SP4 | 3.2.2 | 2 |
| openEuler-24.03-LTS | 3.5.0 | 3 |
| openEuler-24.03-LTS-Next | 3.5.0 | 3 |
| openEuler-24.09 | 3.5.0 | 4 |
评论 /sync <branch1> <branch2> ... 可将当前 PR 修改同步到其它分支(创建同步 PR):
a) 如果当前 PR 是 Open 状态,同步操作将延迟到 PR 被合并时执行
b) 如果当前 PR 已经 Merged,将立即执行同步操作
注意:
- /sync 命令可以指定同步到多个分支,仅最后一个 /sync 命令生效
- 如果创建的同步 PR 不正确,可通过向同步 PR 的源分支提交轻量级 PR 完善,或使用 /close 命令关闭


门禁正在运行, 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决,可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/spark/126/console


x86_64架构构建及构建后检查:multiarch/src-openeuler/x86-64/spark/139/console


aarch64架构构建及构建后检查:multiarch/src-openeuler/aarch64/spark/123/console


| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :white_check_mark:SUCCESS | #126 | |
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_consistency | :white_check_mark:SUCCESS | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :white_check_mark:SUCCESS | #123 |
| check_install | :white_check_mark:SUCCESS | ||
| check_license | :x:FAILED | ||
| x86_64 | check_build | :white_check_mark:SUCCESS | #139 |
| check_install | :white_check_mark:SUCCESS | ||
| check_license | :x:FAILED | ||


如下为接口变更检查结果,目标分支为master,请PR提交者check差异信息
| Arch Name | Check Items | Rpm Name | Check Result | Build Details |
|---|---|---|---|---|
| compare_package(x86_64) | add_rpms | :white_check_mark:SUCCESS | #139 | |
| delete_rpms | :white_check_mark:SUCCESS | |||
| rpm_files | :white_check_mark:SUCCESS | |||
| rpm_jabi | :white_check_mark:SUCCESS | |||
| rpm_lib | :white_check_mark:SUCCESS | |||
| rpm_provides | :white_check_mark:SUCCESS | |||
| rpm_requires | :white_check_mark:SUCCESS | |||
| rpm_symbol | :white_check_mark:SUCCESS | |||
| compare_package(aarch64) | add_rpms | :white_check_mark:SUCCESS | #123 | |
| delete_rpms | :white_check_mark:SUCCESS | |||
| rpm_files | :white_check_mark:SUCCESS | |||
| rpm_jabi | :white_check_mark:SUCCESS | |||
| rpm_lib | :white_check_mark:SUCCESS | |||
| rpm_provides | :white_check_mark:SUCCESS | |||
| rpm_requires | :white_check_mark:SUCCESS | |||
| rpm_symbol | :white_check_mark:SUCCESS |


@zhangxingrong


门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报,您可以评论/ci_mistake 126进行误报标记,126表示本次构建号
也可带上误报的门禁检查项以及误报类型(ci、obs、infra),比如/ci_mistake 126 obs check_build check_install表示的是check_build和check_install存在误报,误报类型为obs
若想取消误报标记,可以评论/ci_unmistake 126取消
也可在评论后加上一段文字描述,但请另起一行


门禁正在运行, 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决,可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/spark/127/console


x86_64架构构建及构建后检查:multiarch/src-openeuler/x86-64/spark/140/console


aarch64架构构建及构建后检查:multiarch/src-openeuler/aarch64/spark/124/console


| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :white_check_mark:SUCCESS | #127 | |
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_consistency | :white_check_mark:SUCCESS | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :white_check_mark:SUCCESS | #124 |
| check_install | :white_check_mark:SUCCESS | ||
| check_license | :x:FAILED | ||
| x86_64 | check_build | :white_check_mark:SUCCESS | #140 |
| check_install | :white_check_mark:SUCCESS | ||
| check_license | :x:FAILED | ||


如下为接口变更检查结果,目标分支为master,请PR提交者check差异信息
| Arch Name | Check Items | Rpm Name | Check Result | Build Details |
|---|---|---|---|---|
| compare_package(x86_64) | add_rpms | :white_check_mark:SUCCESS | #140 | |
| delete_rpms | :white_check_mark:SUCCESS | |||
| rpm_files | :white_check_mark:SUCCESS | |||
| rpm_jabi | :white_check_mark:SUCCESS | |||
| rpm_lib | :white_check_mark:SUCCESS | |||
| rpm_provides | :white_check_mark:SUCCESS | |||
| rpm_requires | :white_check_mark:SUCCESS | |||
| rpm_symbol | :white_check_mark:SUCCESS | |||
| compare_package(aarch64) | add_rpms | :white_check_mark:SUCCESS | #124 | |
| delete_rpms | :white_check_mark:SUCCESS | |||
| rpm_files | :white_check_mark:SUCCESS | |||
| rpm_jabi | :white_check_mark:SUCCESS | |||
| rpm_lib | :white_check_mark:SUCCESS | |||
| rpm_provides | :white_check_mark:SUCCESS | |||
| rpm_requires | :white_check_mark:SUCCESS | |||
| rpm_symbol | :white_check_mark:SUCCESS |


@zhangxingrong


/check-cla


1.Fix correctness issue with persist using StorageLevel.NONE on Dataset
Support for InMememoryTableScanExec in AQE was added in #39624, but this patch contained a bug when a Dataset is persisted using
StorageLevel.NONE详情见链接的描述:
https://github.com/apache/spark/commit/6468f96ea42f6efe42033507c4e26600b751bfcc
2.CommandResultExec to override iterator methods to avoid triggering multiple jobs
After SPARK-35378 was changed, the execution of statements such as ‘show parititions test' became slower. The change point is that the execution process changes from ExecutedCommandEnec to CommandResultExec, but ExecutedCommandExec originally implemented the following method
override def executeToIterator(): Iterator[InternalRow] = sideEffectResult.iterator
CommandResultExec is not rewritten, so when the hasNext method is executed, a job process is created, resulting in increased time-consuming
详情见链接的描述:
https://github.com/apache/spark/commit/24f88b319c88bfe55e8b2b683193a85842bdad88
3.Cache Invalidation Issue with JDBC Table
Add an equals method to
JDBCOptionsthat considers two instances equal if theirJDBCOptions.parametersare the same.详情见链接的描述:
https://github.com/apache/spark/commit/81a7f8f184cd597208fcad72130354288a0c9f79
4.Fix flaky WholeStageCodegenSparkSubmitSuite
WholeStageCodegenSparkSubmitSuite is flaky because SHUFFLE_PARTITIONS(200) creates 200 reducers for one total core and improper stop progress causes executor launcher reties. The heavy load and reties might result in timeout test failures.
详情见链接的描述:
https://github.com/apache/spark/commit/6a5747d66e53ed0d934cdd9ca5c9bd9fde6868e6
5.Fix subquery execution failure with TakeOrderedAndProjectExec
This PR fixes a bug when there are subqueries in
TakeOrderedAndProjectExec. The executeCollect method does not wait for subqueries to finish and it can result in IllegalArgumentException when executing a simple query.详情见链接的描述:
https://github.com/apache/spark/commit/f47b63c6a62fb6f1fd894f64736847719af7a199