[jira] [Updated] (CASSANDRA-15334) Restore java-driver back to upstream code, using new implementation for dynamic port discovery

2019-09-23 Thread mck (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mck updated CASSANDRA-15334:

Resolution: Duplicate
Status: Resolved  (was: Open)

[~sumanth.pasupuleti] has done the work, ready for review, for this ticket 
already in CASSANDRA-14655. 

Specifically, for this concern raised in this issue, [~andrew.tolbert] mentions 
the problem 
[here|https://issues.apache.org/jira/browse/CASSANDRA-14655?focusedCommentId=16678661=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16678661].

> Restore java-driver back to upstream code, using new implementation for 
> dynamic port discovery
> --
>
> Key: CASSANDRA-15334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15334
> Project: Cassandra
>  Issue Type: Task
>  Components: Dependencies
>Reporter: mck
>Assignee: mck
>Priority: Normal
> Fix For: 4.0-alpha
>
>
>  In Cassandra multiple ports per node was implemented in 
> [CASSANDRA-7544|https://issues.apache.org/jira/browse/CASSANDRA-7544] and in 
> the java-driver implemented under 
> [JAVA-1388|https://datastax-oss.atlassian.net/browse/JAVA-1388]. What's 
> currently included in {{lib/cassandra-driver-core-3.4.0-shaded.jar}} is a 
> custom build of code that is not found in any of the github repo's code 
> (branches or tags). It was built off a [forked 
> branch|https://github.com/datastax/java-driver/pull/931] that was never 
> accepted into the driver. It was implemented instead by the java-driver team 
> in [way|https://github.com/datastax/java-driver/pull/1065]. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-15334) Restore java-driver back to upstream code, using new implementation for dynamic port discovery

2019-09-22 Thread mck (Jira) 


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mck updated CASSANDRA-15334:

Change Category: Operability
 Complexity: Normal
  Fix Version/s: 4.0-alpha
 Status: Open  (was: Triage Needed)

> Restore java-driver back to upstream code, using new implementation for 
> dynamic port discovery
> --
>
> Key: CASSANDRA-15334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15334
> Project: Cassandra
>  Issue Type: Task
>  Components: Dependencies
>Reporter: mck
>Assignee: mck
>Priority: Normal
> Fix For: 4.0-alpha
>
>
>  In Cassandra multiple ports per node was implemented in 
> [CASSANDRA-7544|https://issues.apache.org/jira/browse/CASSANDRA-7544] and in 
> the java-driver implemented under 
> [JAVA-1388|https://datastax-oss.atlassian.net/browse/JAVA-1388]. What's 
> currently included in {{lib/cassandra-driver-core-3.4.0-shaded.jar}} is a 
> custom build of code that is not found in any of the github repo's code 
> (branches or tags). It was built off a [forked 
> branch|https://github.com/datastax/java-driver/pull/931] that was never 
> accepted into the driver. It was implemented instead by the java-driver team 
> in [way|https://github.com/datastax/java-driver/pull/1065]. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org