DanielCarter-stack commented on issue #10533:
URL: https://github.com/apache/seatunnel/issues/10533#issuecomment-3976451313

   <!-- code-pr-reviewer -->
   Thanks for proposing this documentation improvement. The analysis confirms 
the stated coverage gaps are accurate:
   
   **Key findings:**
   - `CheckpointCoordinator.java` (1174 lines) has ~2% Javadoc coverage
   - `TaskExecutionService.java` (1018 lines) has ~2.6% Javadoc coverage
   - `SupportResourceShare.java` / `MultiTableResourceManager.java` SPI methods 
lack complete documentation
   - State fields (`readyToCloseStartingTask`, `schemaChanging`) lack semantic 
explanations
   
   Evidence files:
   - 
`seatunnel-api/src/main/java/org/apache/seatunnel/api/sink/SupportResourceShare.java`
   - 
`seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/checkpoint/CheckpointCoordinator.java`
   - 
`seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/task/TaskExecutionService.java`
   
   This is a well-scoped documentation task. Sub-task 1 (SPI interfaces) is a 
good starting point as it directly helps connector implementers. Please follow 
the style examples in the issue description (what + when + thread-safety 
constraints).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to