AntiTopQuark opened a new issue, #65849:
URL: https://github.com/apache/doris/issues/65849

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Description
   
   TSO status was only available through the HTTP API, so SQL clients could not 
query the current global TSO and its physical and logical components. Add a 
read-only SHOW TSO STATUS command that forwards to the master FE, returns the 
existing four status fields, and reports disabled or uncalibrated TSO state 
explicitly.
   
   ### Use case
   
   Operations personnel use SQL clients to inspect the TSO time window, 
physical time, and logical counter:
   ```sql
   mysql> show tso status;
   
+--------------------------+--------------------+---------------------------+-----------------------------+
   | window_end_physical_time | current_tso        | current_tso_physical_time 
| current_tso_logical_counter |
   
+--------------------------+--------------------+---------------------------+-----------------------------+
   |            1784623449944 | 467828328443412480 |             1784623445295 
|                           0 |
   
+--------------------------+--------------------+---------------------------+-----------------------------+
   1 row in set (0.01 sec)
   ```
   
   ### Related issues
   
   #65265 
   #65418 
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


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