[ https://issues.apache.org/jira/browse/CASSANDRA-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566969#comment-17566969 ]
Michael Semb Wever commented on CASSANDRA-17753: ------------------------------------------------ bq. Often it's useful to run a soak test across an upgrade (sometimes from snapshot to release) and having a stable field to check across both kinds of upgrades is easier to use. But then we are leaking a dev concern into releases user facing… I'm on the fence, am interested in hearing what others think… > 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: 50m > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org