xiangfu0 opened a new pull request, #19965:
URL: https://github.com/apache/pinot/pull/19965

   Brokers need an authenticated view of installed OFFLINE replicas before 
native query dispatch can be wired. This adds tenant-scoped discovery and 
complete per-table routing snapshots, retaining published segments with no 
installed replicas so incomplete coverage cannot silently omit data.
   
   Stacked on #19964. All PRs remain draft.
   
   - Validate exact current server, assignment, content and durable 
installation identities. Only explicitly approved endpoints with the required 
advertised query capability are selectable.
   - Hydrate immutable broker routing images on a bounded connection separate 
from membership heartbeats, invalidate them on failures, and construct 
per-server query contexts that preserve one original deadline.
   - Allow validated routing-policy changes and revocation through the normal 
controller REST API with live tables.
   
   Helix/ZK remains the default. Native query listeners remain disabled. This 
adds routing observations and identity construction; authenticated query 
admission, normal planning/dispatch, qualified clocks and response-delivery 
fencing are still required before serving activation.
   
   Validation: 58 focused TestNG tests passed across query contexts, server 
participants, catalog projections, real mTLS/Ratis transport, broker 
routing/concurrency, controller validation and normal starters. The starter 
test covers uploaded and minion-generated content, missing replicas, server 
replacement, controller restart and REST policy revocation without ZooKeeper. 
Affected-module formatting, Checkstyle and license checks passed; compiler 
warning flags produced no warnings on added lines. Hosted CI is separate from 
these local results.
   


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