Skip to content

Regenerate Spark 4.2.0 release notes#702

Closed
cloud-fan wants to merge 3 commits into
apache:asf-sitefrom
cloud-fan:wenchen/spark-release-4.2.0-notes
Closed

Regenerate Spark 4.2.0 release notes#702
cloud-fan wants to merge 3 commits into
apache:asf-sitefrom
cloud-fan:wenchen/spark-release-4.2.0-notes

Conversation

@cloud-fan

Copy link
Copy Markdown
Contributor

Rewrites the Spark 4.2.0 release-notes post, reconstructed from the v4.1.0..v4.2.0 commit range on branch-4.2 and public Apache JIRA metadata (issue type, fix/affected versions, priority, umbrella/Epic parents). The existing frontmatter is preserved; only the post body changes.

Highlights covered: geospatial types (GA), Change Data Capture + Auto CDC, Arrow-optimized Python UDFs on by default, the NEAREST BY ranking-join SPIP, DSv2 transaction management, SQL path-based name resolution, metric views, the modernized Web UI, and Java 25 support.

Note: only the Markdown source is changed here — the rendered site/releases/spark-release-4-2-0.html still needs regeneration via .dev/build-docs.sh (I could not build the docs-builder image in my environment). Happy to follow up with the built HTML, or a committer can regenerate it.

This pull request and its description were written by Isaac.

Rewrite the Spark 4.2.0 release-notes post, reconstructed from the
v4.1.0..v4.2.0 commit range on branch-4.2 and public Apache JIRA
metadata. Preserves the existing frontmatter; only the body changes.

Co-authored-by: Isaac
@cloud-fan cloud-fan force-pushed the wenchen/spark-release-4.2.0-notes branch from 201f3f8 to 2271629 Compare July 15, 2026 13:40
@nchammas

Copy link
Copy Markdown
Contributor

Ah nice, this addresses my question about the release notes to the dev list.

And looking at the release notes folder, it looks like the dashes version of the URL is the usual format, and 4.1.0 and 4.1.1 are the exception to the rule.

@cloud-fan

Copy link
Copy Markdown
Contributor Author

@nchammas A useful and safe improvement is to let the github action generate the html files and push the commit to the PR branch. Is that doable? I've asked @huaxingao to help regenerate the html files due to my local env issues.

@nchammas

Copy link
Copy Markdown
Contributor

Yes, very doable. I avoided doing that so that PR diffs don't get polluted with noise from the HTML, which would also make review more annoying. But if we prefer to have the HTML pushed to PRs vs. asf-site, we can do that. Let me know if that's what you'd like to do on #699.

@cloud-fan

Copy link
Copy Markdown
Contributor Author

I avoided doing that so that PR diffs don't get polluted with noise from the HTML

It's already the case today, so making html autogen is already a net win.

@nchammas

Copy link
Copy Markdown
Contributor

True, the HTML auto-gen alone is still a net win. I definitely prefer the more ambitious goal of keeping HTML diffs out of PRs (and thus separated from source commits in asf-site's future history), but I'm fine with whatever committers would like to do.

* This will become a table of contents (this text will be scraped).
{:toc}

### Highlights

@nchammas nchammas Jul 15, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Random question but: Do we want to make this "highlights" section a convention for MAJOR and MINOR releases going forward? i.e. Any release matching *.*.0.

We could add a simple linter for it and catch when a release is about to go out without this section. The linter could also ensure that the version in the release URL matches A-B-C and not A.B.C.. Happy to add that.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Good idea. Let's do this as a follow-up so it doesn't block the release notes. Feel free to open a PR for it.

@huaxingao huaxingao requested a review from viirya July 15, 2026 18:24
@huaxingao huaxingao closed this in 08a69eb Jul 15, 2026
@huaxingao

Copy link
Copy Markdown
Contributor

Merging this PR. Let's follow up if there are more comments.

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.

4 participants