[
https://issues.apache.org/jira/browse/CASSGO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046719#comment-18046719
]
João Reis commented on CASSGO-72:
---------------------------------
So far it looks like this has been fixed in 2.0.0 but in CASSGO-96 there's
discussions about changing this behavior so we need to make sure there is no
regression on AWS keyspaces
> Add support for aws keyspaces peering
> -------------------------------------
>
> Key: CASSGO-72
> URL: https://issues.apache.org/jira/browse/CASSGO-72
> Project: Apache Cassandra Go driver
> Issue Type: Improvement
> Components: Core
> Reporter: João Reis
> Priority: Normal
> Fix For: 2.x
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> AWS Keyspaces with peering enabled returns 127.0.0.1 on system.local and then
> returns the same host id in system.peers with the valid IP address. The
> driver needs to ignore the local host in this scenario.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]