[
https://issues.apache.org/jira/browse/CASSANDRA-20328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940394#comment-17940394
]
Stefan Miklosovic commented on CASSANDRA-20328:
-----------------------------------------------
Worth to say that the current patch just extracts sstableloader but driver
dependency is still present in server (even we do not depend on it anymore in
server). By the loading mechanism here (1), driver is currently not in
"tools/lib" but in "lib". When everything is extracted, then we just flip the
switch - we move the driver from "lib" to "tools/lib".
This might be done in theory already as CASSANDRA-20327 is done but it is not
part of this ticket, will be addressed in CASSANDRA-20329.
(1)
https://github.com/apache/cassandra/blob/c182c37ce1ccffc20720e517e9abe271295d9ecc/tools/bin/cassandra.in.sh#L54-L59
> 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
