nsivabalan opened a new pull request, #20223:
URL: https://github.com/apache/hudi/pull/20223
### Describe the issue this Pull Request addresses
There are two audiences for the agent-facing tooling in this repo, and they
want different things:
1. people who **deploy, operate and manage** Hudi tables — sizing them,
keeping table services
healthy, working out why a write failed, deciding whether a config change
is worth making;
2. people who **consume data** from Hudi tables — querying them, exploring
the catalog, asking
questions in natural language.
`hudi-agent-gateway` serves the second audience: it is a Trino-backed
service with guarded SQL
tools, an MCP endpoint and a chat UI. The Hudi Architect skill serves the
first — it is a
design-time advisor that turns workload requirements into a table
architecture and an architecture
decision record. It lives under the gateway only because that was the first
place a skill existed.
That is worth separating before more operator-facing tooling arrives, so
each directory has one
audience and a reader can tell at a glance which is which.
### Summary and Changelog
Moves `hudi-agent-gateway/skills/hudi-architect/` to
`hudi-ai-operator/skills/hudi-architect/`.
No content change beyond path references. The skill, its reference files,
its Flink capability
baseline and its three validation scripts are byte-identical; only install
instructions and script
usage strings name the new location.
The gateway CI workflow keeps running the Architect validators. Its job has
`working-directory: hudi-agent-gateway`, so the scripts are now reached by
relative path out of
that directory, and the workflow's `paths:` filter gains
`hudi-ai-operator/**` so edits to the
skill still trigger validation. Both validators were run from the new
location to confirm:
`validate_config_keys.py` checks 130 keys across 11 markdown files against
1419 resolved from
source, and `validate_flink_capabilities.py --verify-source` validates the
pinned Flink baseline.
`hudi-ai-operator/` is new and currently holds this one skill.
Operator-facing tooling in flight —
table health checks, layout analysis, root-cause analysis, configuration
lookup and optimization
advice — is proposed under the same directory in separate pull requests, so
this move is the first
step rather than a one-off.
### Impact
A directory move plus a CI path update. No Java, no configs, no storage
format change, no behaviour
change. Anyone who installed the skill by copying from the old path should
copy from the new one;
the README and runbook say so.
### Risk Level
low
The only functional surface is the CI workflow. Both validator invocations
were executed from the
new path and pass, and the `paths:` filter was widened rather than narrowed,
so the workflow still
fires for every change that previously triggered it.
### Documentation Update
The skill's own README and runbook carry the new install path. No website
change needed.
### 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]
