[
https://issues.apache.org/jira/browse/CASSANDRA-15502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162714#comment-17162714
]
Berenguer Blasi commented on CASSANDRA-15502:
---------------------------------------------
[~dcapwell], now that we have an easy way to test tools in unit tests as per
CASSANDRA-15583/CASSANDRA-15942 maybe we could fold this one in also. Most of
the sstable util tools (to call them sthg) do already get tested in circle ci
under j11 utests right?
I wonder if we could define an MVP for j11 tooling testing that would fit the
15583 effort...
> In Tree Tooling with Java 11
> ----------------------------
>
> Key: CASSANDRA-15502
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15502
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest, Test/fuzz, Tool/bulk load, Tool/cqlsh,
> Tool/diff, Tool/fql, Tool/nodetool, Tool/sstable, Tool/stress
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.0-beta
>
>
> This is to cover testing the various tools running on java 11.
> The scope of this testing is manual testing and not automated, different
> JIRAs should cover automation testing these tool.
> The tools in question are: nodetool, sstableloader, sstablescrub,
> sstableupgrade, sstableutil, sstableverify, fqltool, stress, auditlogviewer,
> compaction-stress, sstabledump, sstableexpiredblockers, sstablemetadata,
> sstableofflinerelevel, sstablesplit, and sstablerepairedset (many of these
> may be tested already in dtest)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
