[
https://issues.apache.org/jira/browse/CASSANDRA-20328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Tolbert updated CASSANDRA-20328:
-------------------------------------
Test and Documentation Plan:
See attached for test results [^CASSANDRA-20328-test_results.html] (a few
recent flakes that I've seen in other test runs that don't look related)
* Verified redhat and debian builds in docker
* CCM changes required to copy tools/bin/cassandra.in.sh to the created node
directory for each ccm node
was:
See attached for test results [^CASSANDRA-20328-test_results.html]
* Verified redhat and debian builds in docker
* CCM changes required to copy tools/bin/cassandra.in.sh to the created node
directory for each ccm node
> Migrate sstableloader code to its own tools directory
> -----------------------------------------------------
>
> Key: CASSANDRA-20328
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20328
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Tool/sstable
> Reporter: Andy Tolbert
> Assignee: Andy Tolbert
> Priority: Normal
> Labels: pull-request-available
> Fix For: 5.x
>
> Attachments: CASSANDRA-20328-test_results.html
>
> Time Spent: 9.5h
> Remaining Estimate: 0h
>
> Akin to fqltool and stress, we should move sstableloader to its own tools
> directory. This is needed to decouple the java driver as a dependency from
> server code ([CASSANDRA-20326]).
> For backwards compatibility reasons, we should retain {{bin/sstableloader}}.
--
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
