[
https://issues.apache.org/jira/browse/CASSANDRA-18585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757980#comment-17757980
]
Andres de la Peña commented on CASSANDRA-18585:
-----------------------------------------------
Most of the failures are known:
* {{test_dead_sync_initiator}} in 3.0 and 3.11 is CASSANDRA-17702
* {{test_compactionstats}} in 3.0 and 3.11 looks like a timeout
* {{test_readrepair}} doesn't have a ticket but it is [on
Butler|https://ci-cassandra.apache.org/job/Cassandra-3.11/484/testReport/dtest-novnode.consistency_test/TestConsistency/test_readrepair/]
* {{test_multiple_concurrent_repairs}} in 3.11 doesn't have a ticket but seems
to be [on
Butler|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-3.11/failure/repair_tests.repair_test/TestRepair/test_multiple_concurrent_repairs]
* {{testReprepareMixedVersionWithoutReset}} in 3.11 is CASSANDRA-18021
* {{test_bootstrap_with_reset_bootstrap_state}} in 3.11 and 4.0 is
CASSANDRA-17086
* {{testFailingMessage}} in 4.0 is CASSANDRA-18366
* {{test_failing_manual_rebuild_index}} in 5.0 is CASSANDRA-18361
* {{runQueriesWithoutCollisions}} in 5.0 looks like and env issue (address
already in use)
* {{testServiceTopPartitionsSingleTable}} in trunk is CASSANDRA-17798
However, I haven't found related tickets nor previous Butler failures for:
*
[{{test_optional_outbound_tls}}|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2989/workflows/e38f3c21-b6a1-418a-b799-eebdb7a336f0/jobs/104883/tests]
in 4.0
*
[{{testLoggedPartitionsPerBatch}}|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2989/workflows/e38f3c21-b6a1-418a-b799-eebdb7a336f0/jobs/104894/tests]
in 4.0
*
[{{test_paxos_any}}|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2990/workflows/65d794ba-7449-4695-ba56-072bc9589926/jobs/105051/tests]
in 4.1
*
[{{test_move_forwards_between_and_cleanup}}|https://app.circleci.com/pipelines/github/instaclustr/cassandra/2993/workflows/80ac4db3-fc3d-4908-bc39-dfff6ab88871/jobs/105464/tests]
in trunk
> Alter Type does not validate changes like Create Type does
> ----------------------------------------------------------
>
> Key: CASSANDRA-18585
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18585
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: David Capwell
> Assignee: Roman Mushchinski
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Create Type attempts to block undesired field types, but this validation is
> not cared over to Alter Type Add Field; which allows you to add
> unexpected/desired types
> {code}
> Assertions.assertThatThrownBy(() -> createType("CREATE TYPE %s (f
> counter)")).hasRootCauseMessage("A user type cannot contain counters");
> String type = createType(KEYSPACE, "CREATE TYPE %s (a int)");
> schemaChange(String.format("ALTER TYPE %s.%s ADD f counter", KEYSPACE, type));
> UserType udt =
> Keyspace.open(KEYSPACE).getMetadata().types.get(UTF8Type.instance.decompose(type)).get();
> logger.warn("UDT: {}", udt);
> {code}
> {code}
> UDT:
> org.apache.cassandra.db.marshal.UserType(cql_test_keyspace,747970655f3031,61:org.apache.cassandra.db.marshal.Int32Type,66:org.apache.cassandra.db.marshal.CounterColumnType)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]