style: Reformat comments and long lines in RetentionManagerTest for…

[iammuntazirali]

… improved readability.

Instructions:

1. The PR has to be tagged with at least one of the following labels (*):
   1. feature
   2. bugfix
   3. performance
   4. ui
   5. backward-incompat
   6. release-notes (**)
2. Remove these instructions before publishing the PR.

(*) Other labels to consider:

• testing
• dependencies
• docker
• kubernetes
• observability
• security
• code-style
• extension-point
• refactor
• cleanup

(**) Use release-notes label for scenarios like:

• New configuration options
• Deprecation of configurations
• Signature changes to public methods/interfaces
• New plugins added or old plugins removed

[Jackie-Jiang]

This is not the code style we use. Please configure your IDE with Pinot Style

[iammuntazirali]

“Got it — I’ll configure my IDE to follow the Pinot Style. Thanks for the heads-up.”

[Copilot]

Pull request overview

This PR reformats comments and long lines in RetentionManagerTest and related files to improve code readability by adhering to standard line length conventions.

Changes:

• Wrapped long comments across multiple lines to stay within line length limits
• Reformatted multi-line method calls and variable assignments for better readability
• Removed unnecessary blank lines for cleaner code structure

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
RetentionManagerTest.java	Reformatted comments and method calls throughout test file for improved readability
RetentionManager.java	Wrapped long comments and method signatures, added new overloaded method call for multi-topic handling
PinotHelixResourceManager.java	Added new overloaded method with documentation and null check for handling multi-topic stream configs

[Copilot]

A null check for llcName is added in the original getLastLLCCompletedSegments() method but this method was not previously checking for null. This changes the behavior of the existing method. The null check should only be in the new overloaded method to avoid altering the behavior of the existing API.

Suggested change

	if (llcName == null) {
	continue;
	}

[Copilot]

The method signature of manageRetentionForRealtimeTable changed from accepting String realtimeTableName to TableConfig tableConfig. While the new parameter is more flexible, this is a breaking change to the method signature. Consider deprecating the old signature if this is meant to be part of the public API, or document this as a breaking change.