You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2022/10/18 20:58:00 UTC

[jira] [Commented] (CASSANDRA-17753) Include GitSHA in nodetool version output

    [ https://issues.apache.org/jira/browse/CASSANDRA-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17619787#comment-17619787 ] 

Stefan Miklosovic commented on CASSANDRA-17753:
-----------------------------------------------

hi [~aratnofsky] , if you dont mind I might take a look. Could you brief me about where we are ? I guess pretty close? 

> Include GitSHA in nodetool version output
> -----------------------------------------
>
>                 Key: CASSANDRA-17753
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17753
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tool/nodetool
>            Reporter: Abe Ratnofsky
>            Assignee: Abe Ratnofsky
>            Priority: Normal
>             Fix For: 4.x
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> It can be useful to see specifically which Git SHA a running instance of Cassandra was built with, especially when running clusters in development for soak testing.
>  
> I have a patch ready for this, and am preparing it now.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org