Skip to content

Write blog post for 1.2.0 release #6889

Open

Description

@andygrove

What is the problem the feature request solves?

The Comet 1.2.0 release needs a blog post. The release process is to draft it in a shared document, agree on the content, and then open a PR against datafusion-site.

Release tracking: #6550. The 1.1.0 post is tracked in #6120.

Describe the potential solution

Draft the post from the summary below, then open the datafusion-site PR so it can go out with the 1.2.0 announcement.

The summary is a snapshot of main at 333bae8 (2026-10-23), refreshed from the 2026-10-12 snapshot at 019f3be. Counts, defaults and the list of open PRs will move before the release branch is cut, so refresh them then. Performance figures are quoted from the PR descriptions and were not re-measured, so re-verify any number before it goes in the post.

Additional context

What is new on main since 1.1.0

branch-1.1 was cut from main at 36ab57c (2026-09-25), so git log 1.1.0..main overcounts. After removing the commits that are also on branch-1.1 as backports (matched by PR number and by title), main has 336 new commits from 2026-09-26 to 2026-10-23, from 34 authors plus Dependabot: 123 fixes, 50 features, 42 performance changes, 32 docs changes, 37 test changes and 52 chore, refactor, CI and build changes. For scale, 1.1.0 contains 418 commits that 1.0.0 does not.

branch-1.1 has 18 commits after the 1.1.0 tag (backports for a 1.1.1 release). They are excluded from the count above, so anything listed below that is also among those backports is not new relative to the branch head.

1. Spark-exact floats and timezones. A systematic sweep instead of per-expression fixes.

2. Comet's in-memory cache stays opt-in. spark.comet.exec.inMemoryCache.enabled is off by default in 1.1.0 and in 1.2.0. During the 1.2 cycle #5634 enabled it by default on Spark 3.5+ and #6963 turned that off again before the release, because of three open wrong-results bugs (#6787, #6898, #6922) that default settings could reach. No released version had it on by default, so the post should describe the decision (we held it back for correctness), not a revert. The hardening that landed on main is still worth a mention: serializer and Kryo gating (#6360, #6537), EXPLAIN and SQL-tab fidelity (#6453, #6574, #6577), planner statistics (#6412), fused vector reads (#5859), the reader class generated once per executor (#6860) and an opt-in lz4 codec (#6859). Audit follow-ups are tracked in #6834.

3. Iceberg native writes and row-level operations.

4. Memory and spill.

5. More of the plan runs natively.

6. Performance.

7. Platform and project.

Not worth a headline: Spark 4.1 TIME type support through codegen dispatch (#4821). Spark keeps the type behind an internal flag, spark.sql.timeType.enabled, that defaults to off outside tests in 4.1.1, 4.1.3 and 4.2.0.

Changes since the 2026-10-12 snapshot

Open PRs worth watching before the cut (as of 2026-10-23)

Activity

  1. added this to the 1.2.0 milestone on Oct 12, 2026
  2. self-assigned this
    on Oct 12, 2026
  3. andygrove commented on Oct 23, 2026

    @andygrove
    MemberAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions