Skip to content

[SPARK-60628][BUILD] Upgrade lz4-java to 1.12.1 - #59870

Closed
dongjoon-hyun wants to merge 1 commit into
apache:masterfrom
dongjoon-hyun:SPARK-60628
Closed

dongjoon-hyun wants to merge 1 commit into
apache:masterfrom
dongjoon-hyun:SPARK-60628

Conversation

@dongjoon-hyun

Copy link
Copy Markdown
Member

What changes were proposed in this pull request?

This PR aims to upgrade at.yawk.lz4:lz4-java to 1.12.1.

Why are the changes needed?

To bring the security fix of v1.12.1, which was released as a security release for GHSA-48mj-8f7c-7qfm (severity: low, availability impact only).

Note that Apache Spark's LZ4CompressionCodec and Statistics read streams via LZ4BlockInputStream, which is one of the code paths fixed by GHSA-48mj-8f7c-7qfm.

Full Changelog: yawkat/lz4-java@v1.12.0...v1.12.1

Does this PR introduce any user-facing change?

No. There is no behavior change for valid LZ4 streams.

How was this patch tested?

  • Regenerated the dependency manifest with dev/test-dependencies.sh --replace-manifest; the only diff is the lz4-java line.
  • build/sbt core/compile
  • build/sbt 'core/testOnly org.apache.spark.io.CompressionCodecSuite org.apache.spark.shuffle.sort.UnsafeShuffleWriterSuite org.apache.spark.FileSuite org.apache.spark.deploy.history.EventLogFileWritersSuite' (87 tests passed)
  • Pass the CIs.

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

Generated-by: Claude Sonnet 5.5

@dongjoon-hyun dongjoon-hyun changed the title [SPARK-60628][BUILD] Upgrade lz4-java to 1.12.1 [SPARK-60628][BUILD] Upgrade lz4-java to 1.12.1 Oct 28, 2026
@dongjoon-hyun

Copy link
Copy Markdown
Member Author

Thank you, @HyukjinKwon !

@dongjoon-hyun

Copy link
Copy Markdown
Member Author

Merge Summary:

Posted by merge_spark_pr.py

@dongjoon-hyun
dongjoon-hyun deleted the SPARK-60628 branch October 28, 2026 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants