[
https://issues.apache.org/jira/browse/CASSANDRA-19697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855974#comment-17855974
]
Andres de la Peña commented on CASSANDRA-19697:
-----------------------------------------------
bq. Andres de la Peña will this test still be valid if reworked without
injecting the byteman failure?
I added that test 7 years ago, so I barely remember anything. From what I read,
it just makes sure that the column renames for the table and its MVs are sent
in a single update. For that, it simply kills the node after the first schema
update, so we would see inconsistencies if the column rename was split into
multiple mutations. I don't know how we could do that without an injection.
Maybe counting the number of schema merges, if there is some metric or log
entry, to verify that the rename only produces one?
> Test failure:
> materialized_views_test.py::TestMaterializedViews::test_rename_column_atomicity
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19697
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19697
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 5.0-rc, 5.x
>
> Attachments: shutdown_stuck.txt
>
>
> Breaking this out from CASSANDRA-19683. The byteman script fails to execute
> in 5.0/trunk after CASSANDRA-19534.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
