Skip to content

[SPARK-52944][CORE][TESTS][FOLLOWUP] Avoid hard-coding the checksum algorithm name #51675

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

LuciferYang
Copy link
Contributor

@LuciferYang LuciferYang commented Jul 26, 2025

What changes were proposed in this pull request?

This PR retrieves the shuffle checksum algorithm name via conf.get(SHUFFLE_CHECKSUM_ALGORITHM) to eliminate hard-coding.

Why are the changes needed?

Address #51654 (comment)

Does this PR introduce any user-facing change?

No

How was this patch tested?

  • Pass Github Actions

Was this patch authored or co-authored using generative AI tooling?

No

@github-actions github-actions bot added the CORE label Jul 26, 2025
@@ -70,7 +70,8 @@ class SortShuffleSuite extends ShuffleSuite with BeforeAndAfterAll {
// Ensure that the shuffle actually created files that will need to be cleaned up
val filesCreatedByShuffle = getAllFiles -- filesBeforeShuffle
filesCreatedByShuffle.map(_.getName) should be(
Set("shuffle_0_0_0.data", "shuffle_0_0_0.checksum.ADLER32", "shuffle_0_0_0.index"))
Set("shuffle_0_0_0.data", s"shuffle_0_0_0.checksum.${conf.get(SHUFFLE_CHECKSUM_ALGORITHM)}",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dongjoon-hyun dongjoon-hyun changed the title [SPARK-52944][CORE][TESTS] Avoid hard-coding the checksum algorithm name [SPARK-52944][CORE][TESTS][FOLLOWUP] Avoid hard-coding the checksum algorithm name Jul 27, 2025
Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM. Thank you so much, @LuciferYang .

cc @peter-toth

@LuciferYang
Copy link
Contributor Author

Thanks @dongjoon-hyun

@LuciferYang
Copy link
Contributor Author

After verification, I will also backport this PR to branch-4.0 to maintain consistency.

LuciferYang added a commit to LuciferYang/spark that referenced this pull request Jul 27, 2025
…lgorithm name

### What changes were proposed in this pull request?
This PR retrieves the shuffle checksum algorithm name via `conf.get(SHUFFLE_CHECKSUM_ALGORITHM)` to eliminate hard-coding.

### Why are the changes needed?
Address apache#51654 (comment)

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
- Pass Github Actions

### Was this patch authored or co-authored using generative AI tooling?
No

Closes apache#51675 from LuciferYang/SPARK-52944-FOLLOWUP.

Authored-by: yangjie01 <yangjie01@baidu.com>
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
LuciferYang added a commit to LuciferYang/spark that referenced this pull request Jul 27, 2025
…lgorithm name

### What changes were proposed in this pull request?
This PR retrieves the shuffle checksum algorithm name via `conf.get(SHUFFLE_CHECKSUM_ALGORITHM)` to eliminate hard-coding.

### Why are the changes needed?
Address apache#51654 (comment)

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
- Pass Github Actions

### Was this patch authored or co-authored using generative AI tooling?
No

Closes apache#51675 from LuciferYang/SPARK-52944-FOLLOWUP.

Authored-by: yangjie01 <yangjie01@baidu.com>
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
LuciferYang added a commit that referenced this pull request Jul 27, 2025
…lgorithm name

### What changes were proposed in this pull request?
This PR retrieves the shuffle checksum algorithm name via `conf.get(SHUFFLE_CHECKSUM_ALGORITHM)` to eliminate hard-coding.

### Why are the changes needed?
Address #51654 (comment)

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
- Pass Github Actions

### Was this patch authored or co-authored using generative AI tooling?
No

Closes #51675 from LuciferYang/SPARK-52944-FOLLOWUP.

Authored-by: yangjie01 <yangjie01@baidu.com>
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
(cherry picked from commit afd595a)
Signed-off-by: yangjie01 <yangjie01@baidu.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants