nsivabalan opened a new pull request, #20385: URL: https://github.com/apache/hudi/pull/20385
### Describe the issue this Pull Request addresses Follow-up to #20151. The `hudi-table-health` skill tells the agent to read `HoodieTableHealthChecker`'s exit code as `0` healthy, `1` unhealthy, `2` could not run. The tool actually returns: | Code | Meaning | |---|---| | `0` | every check healthy or skipped | | `2` | the tool itself could not run: bad arguments or an unreadable table | | `3` | at least one check `UNHEALTHY` | | `4` | no check unhealthy, but at least one could not run | and deliberately never returns `1`, so that a JVM start-up failure (missing class, bad classpath) cannot be mistaken for a verdict about the table. An agent following the old text reads the most common result, `3`, as an undocumented code. Observed while running the checker against a table with a savepoint pinning archival: exit `3`, two `UNHEALTHY` checks. ### Summary and Changelog One paragraph in `hudi-ai-operator/skills/hudi-table-health/SKILL.md`: the exit-code table now matches `EXIT_HEALTHY` / `EXIT_ERROR` / `EXIT_UNHEALTHY` / `EXIT_CHECK_ERRORED` in `HoodieTableHealthChecker.java`, explains why `1` is reserved, and says what to read on each code. ### Impact Documentation only. No code, no configs, no behaviour change. ### Risk Level none ### Documentation Update Self-contained. ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable -- 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]
