[ https://issues.apache.org/jira/browse/CASSANDRA-10603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Witschey updated CASSANDRA-10603: ------------------------------------- Issue Type: Sub-task (was: Bug) Parent: CASSANDRA-10166 > Fix CQL syntax errors in upgrade_through_versions_test > ------------------------------------------------------ > > Key: CASSANDRA-10603 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10603 > Project: Cassandra > Issue Type: Sub-task > Reporter: Jim Witschey > Assignee: Russ Hatch > > In the {{cassandra_upgrade_2.1_to_3.0_proto_v3}} upgrade tests on CassCI, > some of the tests are failing with the following error: > {code} > <ErrorMessage code=2000 [Syntax error in CQL query] message="line 1:13 no > viable alternative at character '_'"> > {code} > The tests that fail this way [(at least as of this > run)|http://cassci.datastax.com/view/Upgrades/job/cassandra_upgrade_2.1_to_3.0_proto_v3/10/testReport/] > are the following: > {code} > upgrade_through_versions_test.TestUpgrade_from_2_1_latest_tag_to_2_1_HEAD.parallel_upgrade_with_internode_ssl_test > upgrade_through_versions_test.TestUpgrade_from_2_1_latest_tag_to_2_1_HEAD.parallel_upgrade_test > upgrade_through_versions_test.TestUpgrade_from_2_1_latest_tag_to_2_1_HEAD.bootstrap_multidc_test > upgrade_through_versions_test.TestUpgrade_from_2_1_latest_tag_to_2_1_HEAD.bootstrap_test > upgrade_through_versions_test.TestUpgrade_from_2_1_latest_tag_to_cassandra_3_0_HEAD.bootstrap_multidc_test > upgrade_through_versions_test.TestUpgrade_from_2_1_latest_tag_to_cassandra_3_0_HEAD.bootstrap_test > upgrade_through_versions_test.TestUpgrade_from_2_1_latest_tag_to_cassandra_3_0_HEAD.parallel_upgrade_test > upgrade_through_versions_test.TestUpgrade_from_2_1_latest_tag_to_cassandra_3_0_HEAD.parallel_upgrade_with_internode_ssl_test > {code} > There may be other tests in other protocol upgrade jobs that fail this way, > but I haven't dug through yet to see. > Assigning to [~rhatch] since, afaik, you're the most likely person to > understand the problem. Feel free to reassign, of course. -- This message was sent by Atlassian JIRA (v6.3.4#6332)