dongjoon-hyun opened a new pull request, #59877: URL: https://github.com/apache/spark/pull/59877
### What changes were proposed in this pull request? This PR aims to upgrade `commons-codec` from 1.22.1 to 1.23.0. - `pom.xml`: `commons-codec.version` 1.22.1 -> 1.23.0 - `dev/deps/spark-deps-hadoop-3-hive-2.3`: regenerated with `dev/test-dependencies.sh --replace-manifest` (only the `commons-codec` line changes) ### Why are the changes needed? To keep the dependency up to date with the latest stable release of Apache Commons Codec: - Release tag: https://github.com/apache/commons-codec/tree/rel/commons-codec-1.23.0 (tagged 2026-10-11) - Changes report: https://commons.apache.org/proper/commons-codec/changes.html (release date 2026-10-04) The release requires Java 8 or later, so it is compatible with Spark's Java 17+ baseline. No API is removed; only the `PhoneticEngine` and `BeiderMorseEncoder` constructors are deprecated in favor of builders. The release also contains behavior changes (e.g., `Hex` decoding accepts only ASCII hex digits, STRICT `Base32`/`Base64` decoding requires the canonical form, `Base58` input length limits, and `QuotedPrintableCodec` line-break handling). Spark's own usage is limited to: - `new Base32()` with the default decoding policy in `to_base32`/`from_base32` (`stringExpressions.scala`) - `StringUtils.newStringUtf8` in `ThriftHttpServlet` - `Hex` and `Base64` in benchmarks (`HexBenchmark`, `Base64Benchmark`) None of these code paths use the changed behaviors. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? - Verified the dependency manifest with `dev/test-dependencies.sh --replace-manifest` (the diff is the single `commons-codec` line). - `build/sbt core/compile` - `build/sbt 'catalyst/testOnly org.apache.spark.sql.catalyst.expressions.StringExpressionsSuite'` (73 tests passed, including `to_base32/from_base32`) - `build/sbt 'sql/testOnly org.apache.spark.sql.StringFunctionsSuite'` (86 tests passed, including `to_base32/from_base32`) ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Sonnet 5.5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
