[
https://issues.apache.org/jira/browse/CASSANDRA-10868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109028#comment-15109028
]
Russ Hatch commented on CASSANDRA-10868:
----------------------------------------
I'm not certain what guarantees can be made about the binaries running on jdk8,
but seems reasonable to me if that's not a problem. Alternatively I guess we
could to jdk switching similar to how it's done in
upgrade_through_versions_test.py if the first approach doesn't pan out. Not
sure how implementing this will look, but we should take care to not let
binaries be used as the upgraded-to (only uprgaded-from) version, unless we're
specifically looking to vet those binaries.
> Skip supercolumns upgrade tests on jdk8
> ---------------------------------------
>
> Key: CASSANDRA-10868
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10868
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jim Witschey
> Assignee: Jim Witschey
>
> The tests in the {{upgrade_supercolumns_test}} dtest module fail when we test
> on JDK8 because they attempt to upgrade from 2.0, which will not compile on
> JDK8:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/160/testReport/upgrade_supercolumns_test/
> [~rhatch] As we look at how we want to run upgrade tests in the future, we
> should consider this. In the meantime, I think the best way to deal with this
> might be to add something to the exclude files in {{conf/}}. That sound
> reasonable, or is there a better way to do this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
