Skip to content
New issue

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

add revision to kv get trace output #767

Merged
merged 1 commit into from
Apr 28, 2023

Conversation

maxarndt
Copy link
Contributor

This PR adds the sequence number of a message to the output of nats kv get <bucket> <key> --trace

The timestamp of the message was already present but I missed the sequence number.
I'm aware that the history command shows this information but for me this is the right place as well for this information.

@@ -492,7 +492,7 @@ func (c *kvCommand) getAction(_ *fisk.ParseContext) error {
return nil
}

fmt.Printf("%s > %s created @ %s\n", res.Bucket(), res.Key(), res.Created().Format(time.RFC822))
fmt.Printf("%s > %s seq %d created @ %s\n", res.Bucket(), res.Key(), res.Revision(), res.Created().Format(time.RFC822))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets call it revision: %d instead, revision is the word people using the APIs would recognise.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done :-)

@maxarndt maxarndt force-pushed the add-seqno-to-kv-get-trace branch from 8362f63 to 1601020 Compare April 28, 2023 14:35
@maxarndt maxarndt changed the title add seqno to kv get trace output add revision to kv get trace output Apr 28, 2023
rename seq to revision in trace output
@maxarndt maxarndt force-pushed the add-seqno-to-kv-get-trace branch from 1601020 to c5f9a53 Compare April 28, 2023 14:37
@ripienaar ripienaar merged commit 416b700 into nats-io:main Apr 28, 2023
@ripienaar
Copy link
Collaborator

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants