FreeOnePlus opened a new pull request, #196: URL: https://github.com/apache/doris-mcp-server/pull/196
## Summary - replace the synthetic Query Profile probe ID with an owned, bounded profiled query - resolve the generated Query ID through the Doris trace endpoint and verify the actual profile endpoint - discard the stateful probe connection and URL-escape the returned Query ID - update the changelog and regression coverage ## Root cause On Doris 4.0.5, `/rest/v2/manager/query/query_info` returned HTTP 200 with `code=500` for the synthetic all-zero Query ID even though the same account could create and read its own Query Profile. The capability detector therefore hid a working feature as `PROFILE_API_INVALID_RESPONSE`. ## Safety and reliability - executes only a read-only `SELECT 1 AS capability_probe` - bounds the result to one row and 1 KiB - marks the session-state connection unhealthy so profiling settings cannot leak into the pool - retries the bounded trace lookup before reporting degraded availability - verifies the same profile endpoint used by the runtime ## Validation - real Doris 4.0.5 probe: synthetic `query_info` returned `code=500`; owned trace and profile requests both returned `code=0` - focused capability and query-runtime suite: 221 passed - full suite: 1776 passed, 83 skipped - `mypy doris_mcp_server` - `ruff 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]
