[
https://issues.apache.org/jira/browse/CASSANDRA-17210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466597#comment-17466597
]
Rens Groothuijsen commented on CASSANDRA-17210:
-----------------------------------------------
It does appear the bulk loader doesn't make use of the port parameter, though
as a workaround you can specify "-d <host>:<port>" instead of "-d <host>" as
the address, and it will work as expected.
> Not able to override default transport port in cassandra 4.0
> ------------------------------------------------------------
>
> Key: CASSANDRA-17210
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17210
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
> Reporter: NISHANT GUPTA
> Priority: Normal
> Fix For: 4.0.x
>
>
> Bulk Loader is not honouring "-p" option given on the command line of the
> sstableloader.
> The command line used is:
> ~/apache-cassandra-4.0.1/bin/sstableloader -d 10.14.20.148 -cph 1 -idct 0 -p
> 9942 -ssp 7011 -sp 7010 --verbose ~/cassandra4_experiment/nishant/employee/
>
> but the call is still going to /10.14.20.148:9042. We are just passing the
> host information to the Cluster.Builder in NativeSSTableLoaderClient.java:
> Cluster.Builder builder =
> Cluster.builder().addContactPointsWithPorts(hosts).allowBetaProtocolVersion();
> Looks like default port is getting picked inside
> com.datastax.driver.core.cluster.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
