FreeOnePlus opened a new pull request, #198:
URL: https://github.com/apache/doris-mcp-server/pull/198

   ## Summary
   - split resource-growth availability into full, audit-only, and 
partition-only evidence variants
   - keep the Child callable in degraded mode when either recorded source 
remains readable
   - add a dedicated partition-history capability probe and fail closed when 
evidence is missing
   - refresh the generated tool registry and changelog
   
   ## Root cause
   `doris_cluster.analyze_resource_growth` was globally gated by the Audit Log 
probe. On the tested Doris 4.0.5 route, the service account cannot read 
`internal.__internal_schema.audit_log`, but it can read 
`information_schema.partitions` and execute the storage-growth aggregation. The 
Server therefore hid a working `storage` selector together with the unavailable 
audit-backed selectors.
   
   ## Availability behavior
   - both Audit Log and partition history readable: 
`all_recorded_resource_history`
   - only Audit Log readable: `audit_resource_history`, degraded and callable
   - only partition history readable: `partition_creation_history`, degraded 
and callable
   - missing or unsupported evidence: fail closed
   
   ## Validation
   - real Doris 4.0.5 service account: Audit Log permission denied; partition 
probe readable
   - real 30-day storage-growth aggregation: succeeded
   - focused capability, registry, matrix, and manifest suites: 175 passed
   - full suite: 1782 passed, 83 skipped
   - `mypy doris_mcp_server`
   - `ruff check .`
   - `python generate_tool_catalog.py --check`
   - `git diff --check`
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to