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

Stefan Miklosovic edited comment on CASSANDRA-17002 at 3/15/22, 6:44 PM:
-------------------------------------------------------------------------

thanks [~yifanc] for explaining these X's more specifically, I was thinking 
this was already settled between you and [~frankgh]. I dont have any problem 
with including them, of course. That will actually simplify the code even more.


was (Author: smiklosovic):
thanks [~yifanc] to explain these X's more specifically, I was thinking this 
was already settled between you and [~frankgh]. I dont have any problem with 
including them, of course. That will actually simplify the code even more.

> Gossipinfo should be available through a Virtual Table
> ------------------------------------------------------
>
>                 Key: CASSANDRA-17002
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17002
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Feature/Virtual Tables
>            Reporter: Dinesh Joshi
>            Assignee: Francisco Guerrero
>            Priority: Normal
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> The {{nodetool}} utility provides a utility to print out the {{gossipinfo}} 
> for the cluster. The output is then printed out as text to stdout and 
> consumed by operators and tools built around {{nodetool gossipinfo}}.
> With the introduction of virtual tables in Cassandra, the {{gossipinfo}} 
> virtual table can help operators and the tools built around {{gossipinfo}} to 
> consume the gossip information more easily by providing a tabular output of 
> the data, which can be easily queried by different clients.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to