We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When we call pd-ctl store , it shows the timestamps in 4 different ways, see below example:
pd-ctl store
{ "store": { ... "git_hash": "6c1424706f3d5885faa668233f34c9f178302f36", "start_timestamp": 1647365006, <========= 10 digits unix timestamp ... "last_heartbeat": 1647373317633963588, <========= 19 digits unix timestamp "state_name": "Up" }, "status": { .... "start_ts": "2022-03-15T17:23:26Z", <========= YYYY-MM-DDTHH:mm:ss "last_heartbeat_ts": "2022-03-15T19:41:57.633963588Z", <========= YYYY-MM-DDTHH:mm:ss:nnnnnnnnn ... } }
It's pretty hard to evaluate the difference between unix timestamps and the date time format. Please \ show the timestamps in a consistent way.
The text was updated successfully, but these errors were encountered:
Thanks for your feedback but considering the compatibility problems, we will try to make them consistent in API version 2.
Sorry, something went wrong.
ref tikv/rfcs#88
No branches or pull requests
When we call
pd-ctl store
, it shows the timestamps in 4 different ways, see below example:It's pretty hard to evaluate the difference between unix timestamps and the date time format. Please \ show the timestamps in a consistent way.
The text was updated successfully, but these errors were encountered: