Skip to content

GH-5527: Improve scan mode logging - #5530

Open
seanxuu wants to merge 1 commit into
spring-projects:mainfrom
seanxuu:GH-5527
Open

GH-5527: Improve scan mode logging#5530
seanxuu wants to merge 1 commit into
spring-projects:mainfrom
seanxuu:GH-5527

Conversation

@seanxuu

@seanxuu seanxuu commented Sep 9, 2026

Copy link
Copy Markdown

Fixes #5527

What changed

  • Avoid logging expected skip/scan transaction rollbacks at ERROR level.
  • Describe the non-retryable skipped-item transition without calling it retry exhaustion or attaching an exception stack trace.
  • Add a regression test covering the expected scan-mode log output.

Validation

  • ./mvnw -pl spring-batch-core spring-javaformat:validate
  • Focused scan-mode tests were attempted with JDK 21, but the current NullAway configuration requires JDK 22+; JDK 26 instead fails in Error Prone before tests due to an upstream source-position compatibility error.

@seanxuu
spring-projectsGH-5527: Improve scan mode logging
f73a7e7 
Avoid reporting expected skip and scan transitions as retry exhaustion or chunk failures.

Closes spring-projects#5527

Signed-off-by: Sean <seanxu@connect.hku.hk>
@seanxuu seanxuu mentioned this pull request Sep 9, 2026
Open
@seanxuu
seanxuu marked this pull request as ready for review September 9, 2026 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Misleading INFO and ERROR logs when a skipped write enters scan mode without retries

1 participant

@seanxuu