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

   ## Summary
   
   - route different static tokens to independent Doris clusters in one HTTP 
server process
   - support ordered SQL and FE HTTP candidate lists with startup and runtime 
failover
   - keep profile, trace, table-size, and monitoring requests on the 
authenticated token route
   - propagate endpoint lists to multiworker children and preserve token 
database configuration across persistence and management APIs
   - fail closed for process-global ADBC on token-bound clusters to prevent 
cross-cluster access
   
   ## Operational boundaries
   
   - each `hosts` / `fe_http_hosts` list must contain FE nodes from one Doris 
cluster
   - multi-instance routing is selected by a fixed static token; tool arguments 
cannot override the cluster
   - Doris-backed OAuth tries FE candidates during sign-in, but requires a new 
sign-in if its per-user pool is lost because raw passwords are not retained
   - large production deployments should still prefer a stable SQL gateway or 
load balancer
   
   ## Validation
   
   - `uv run pytest -q -W error`: 1132 passed, 69 skipped
   - coverage gates: protocol 89.94%, authentication 81.53%, core managers 
82.60%
   - `uv run ruff check .`
   - `uv run mypy doris_mcp_server`
   - `uv lock --check`
   - Bandit scan: no findings
   - clean Python 3.12 wheel install and runtime dependency smoke: passed
   - official MCP 2026-07-28 conformance: 25/25 applicable tests passed
   - real Doris integration on 192.168.31.63: 10 passed, 2 skipped because 
separate FE/BE HTTP addresses were not configured
   - true-driver FE failover smoke: unreachable first candidate skipped, real 
secondary selected, `SELECT 1` passed
   
   Closes #73


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