[
https://issues.apache.org/jira/browse/CASSANDRA-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072221#comment-17072221
]
David Capwell commented on CASSANDRA-15406:
-------------------------------------------
bq. David Capwell where do we stand with this? I was reading your pull request
for 15399 and do I understand it right that one is postponed indefinitely? (at
least until 4.0 is out)
Yes, since the repair work are improvements and new features, its best they are
not in 4.0.0 as 4.0.0 is is under freeze right now. I want early feedback on
the tables so different tools could provide feedback or feature requests, but
still should not go into 4.0.0.
bq. I would like to work on this but I am not sure if there is some reasonable
probability it will eventually and actually end up being merged before 4.0 is
out.
Best to ask on the dev mailing list.
bq. Could you elaborate more about what parts of this code would be similar
with your issue which ended up postponed so we would not duplicate things?
I left a comment
https://issues.apache.org/jira/browse/CASSANDRA-15399?focusedCommentId=17072219&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17072219
that shows what part of the code. How I understand this JIRA is not that they
conflict, but that this JIRA benefits 15399; I may be wrong in this
understanding.
bq. query it via JMX or is it true that virtual tables would work too?
The trend is to kill off JMX in favor of virtual tables. I have not looked at
your code, but many prefer virtual tables over JMX.
> Add command to show the progress of data streaming and index build
> -------------------------------------------------------------------
>
> Key: CASSANDRA-15406
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15406
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Streaming, Legacy/Streaming and Messaging,
> Tool/nodetool
> Reporter: maxwellguo
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0, 4.x
>
>
> I found that we should supply a command to show the progress of streaming
> when we do the operation of bootstrap/move/decommission/removenode. For when
> do data streaming , noboday knows which steps there program are in , so I
> think a command to show the joing/leaving node's is needed .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
