Caideyipi opened a new pull request, #19302:
URL: https://github.com/apache/iotdb/pull/19302

   ## Summary
   Add `queues_bound_on_dns` to `SHOW SUBSCRIPTIONS DETAILS`. The column lists 
DataNode IDs that reported all currently matching local DataRegion queues bound 
for the topic and consumer group.
   
   ## Semantics and limits
   Each DataNode evaluates its local subscription metadata and Region topology 
independently. ConfigNode includes an ID only for a successful response from a 
currently registered DataNode and the requested data model. An unavailable 
node, an unsuccessful response, or an older node that does not return this 
optional field is omitted.
   
   This is a point-in-time diagnostic, not a cluster-wide write barrier. 
DataNodes are sampled independently, and Region or subscription topology can 
change after a sample or while ConfigNode aggregates responses. A later-created 
Region is not covered by an earlier result. No distributed lock is used. If a 
DataNode currently has no matching local DataRegion, its empty set of matching 
queues satisfies the all-queues-bound check.
   
   ## Example
   ```sql
   SHOW SUBSCRIPTIONS DETAILS ON "topic-1";
   ```
   
   The relevant columns can look like this:
   
   | TopicName | ConsumerGroupName | DataNodeId | queues_bound_on_dns |
   | --- | --- | ---: | --- |
   | topic-1 | group-1 | 3 | [3, 4] |
   | topic-1 | group-1 | 4 | [3, 4] |
   
   `[3, 4]` means those DataNodes independently reported all matching local 
queues bound when sampled.
   
   ## Validation
   - Scoped Spotless command exited 0.
   - `git show --check` passed.
   - Maven tests were not run.


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

Reply via email to