Skip to content

chore: remove stale Akka-era references from Scaladoc and a log message - #3584

Merged
He-Pin merged 2 commits into
apache:mainfrom
pjfanning:scaladoc-stale-refs
Oct 9, 2026
Merged

He-Pin merged 2 commits into
apache:mainfrom
pjfanning:scaladoc-stale-refs

Conversation

@pjfanning

Copy link
Copy Markdown
Member

Motivation

Some Scaladoc and one log message still refer to Akka-era details that are misleading for Pekko users. These were left out of #3583 because they are in source files.

Modification

  • RemoveInternalClusterShardingData: drop the -2.3 flag (for data written by Akka 2.3.x) from the usage example and description, and no longer mention auto-down as a cause of corrupt data. The flag handling in main is unchanged.
  • Cluster: the auto-down warning now says auto-down is not supported in Pekko, instead of "auto-down has been removed in Akka 2.6.0".
  • Sink.collection Scaladoc: refer to the collection Factory instead of CanBuildFrom.

Result

Scaladoc and the warning match Pekko.

Tests

  • Not run - Scaladoc and log message text only (no test asserts the warning text)

References

Refs #3583

Motivation:
Some Scaladoc and one log message still refer to Akka-era details
that are misleading for Pekko users.

Modification:
- RemoveInternalClusterShardingData: drop the -2.3 flag (for data
  written by Akka 2.3.x) from the usage example and description, and
  no longer mention auto-down as a cause of corrupt data
- Cluster: the auto-down warning says auto-down is not supported in
  Pekko instead of "removed in Akka 2.6.0"
- Sink.collection Scaladoc: refer to the collection `Factory` instead
  of `CanBuildFrom`

Result:
Scaladoc and the warning match Pekko.

Tests:
- Not run - Scaladoc and log message text only

References:
Refs apache#3583
@pjfanning pjfanning added this to the 2.0.0-M5 milestone Oct 8, 2026

@He-Pin He-Pin left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

The auto-down log message change and the Factory fix both look right to me, and I checked that nothing in the repo asserts the old warning text.

* java -classpath <jar files, including pekko-cluster-sharding>
* org.apache.pekko.cluster.sharding.RemoveInternalClusterShardingData
* -2.3 entityType1 entityType2 entityType3
* entityType1 entityType2 entityType3

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

The -2.3 flag is still live: args(0) == "-2.3" at line 77, and remove2dot3Data is a parameter of the public remove method and of the public class constructor. docs/src/main/paradox/typed/cluster-sharding.md:851 also still advertises -2.3. Deleting this paragraph removes the only in-source explanation of the flag and makes the Scaladoc example disagree with both the code and the published docs. Could you keep the paragraph (dropping it from the example is fine), or move the flag removal into a separate PR that also updates the code, the docs and the MiMa filters?

@He-Pin

He-Pin commented Oct 9, 2026

Copy link
Copy Markdown
Member

Pushed fe4bacf to restore the -2.3 paragraph: the flag is still parsed (args(0) == "-2.3") and remove2dot3Data is a parameter of the public remove API, so removing it should be one deliberate change across code, Scaladoc, docs and MiMa rather than a docs-only deletion. The auto-down message and the Factory fixes are good as they are. Will merge once CI is green.

@He-Pin He-Pin left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

lgtm

@He-Pin
He-Pin merged commit d2d52f3 into apache:main Oct 9, 2026
10 checks passed
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