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

Michael Semb Wever updated CASSANDRA-20693:
-------------------------------------------
    Description: 
Don't call `{{repository.setup(..)}}` to download binaries in {{conftest.py}} 
for upgrade variant 'current' versions, as those versions are explicit already.

When starting upgrade tests, adjust the jdk to an available jdk, if the current 
jdk is supported by the starting_version.

Assume different cluster types will have different meta.family, and for binary 
downloads set the cluster class before any call to `repository.setup(..)`, and 
call now instead `cluster.load_from_repository(..)` which delegates to the 
correct subclass download method.

Patch at 

  was:
Don't call `{{repository.setup(..)}}` to download binaries in {{conftest.py}} 
for upgrade variant 'current' versions, as those versions are explicit already.

When starting upgrade tests, adjust the jdk to an available jdk, if the current 
jdk is supported by the starting_version.

Assume different cluster types will have different meta.family, and for binary 
downloads set the cluster class before any call to `repository.setup(..)`, and 
call now instead `cluster.load_from_repository(..)` which delegates to the 
correct subclass download method.


> Python dtest listing to avoid downloading 'current' variant versions
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-20693
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20693
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Test/dtest/python
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>
> Don't call `{{repository.setup(..)}}` to download binaries in {{conftest.py}} 
> for upgrade variant 'current' versions, as those versions are explicit 
> already.
> When starting upgrade tests, adjust the jdk to an available jdk, if the 
> current jdk is supported by the starting_version.
> Assume different cluster types will have different meta.family, and for 
> binary downloads set the cluster class before any call to 
> `repository.setup(..)`, and call now instead 
> `cluster.load_from_repository(..)` which delegates to the correct subclass 
> download method.
> Patch at 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to