cloud-fan opened a new pull request, #59493: URL: https://github.com/apache/spark/pull/59493
### What changes were proposed in this pull request? Same change as #59492 for `branch-4.x`: change the version of `spark.streaming.raw.maxBlockSizeBytes` from `4.4.0` to `3.5.10`. `spark.streaming.raw.maxBlockSizeBytes` was added by "[MINOR] Improve resilence on raw socket stream and steer people towards higher level streaming APIs" and backported to every release line, but each branch annotated it with its own next release: | Branch | Current | After | | --- | --- | --- | | `master` | 5.0.0 | 3.5.10 | | `branch-4.x` | 4.4.0 | 3.5.10 | | `branch-4.3` | 4.3.1 | 3.5.10 | | `branch-4.2` | 4.2.1 | 3.5.10 | | `branch-4.1` | 4.1.4 | 3.5.10 | | `branch-4.0` | 4.0.5 | 3.5.10 | | `branch-3.5` | 3.5.10 | (already correct) | Because the current value differs on every branch, a cherry-pick would conflict, so each branch gets its own PR. ### Why are the changes needed? A config's version should be the same on every branch: the earliest release line that ships it, as with other backported configs (for example, `spark.sql.chunkBase64String.enabled` is `3.5.2` on `master`, `branch-4.0`, and `branch-3.5`). For this config that is 3.5.10. On `branch-4.3`, `4.3.1` is also wrong on its own terms, since the commit is already in `v4.3.0-rc2`. ### Does this PR introduce _any_ user-facing change? No functional change. The "since version" reported for the config (e.g. in the generated configuration docs) changes from 4.4.0 to 3.5.10. ### How was this patch tested? Annotation-only change; no new tests. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 5.5) This pull request and its description were written by Isaac. -- 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]
