[ 
https://issues.apache.org/jira/browse/CASSANDRA-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110930#comment-15110930
 ] 

Philip Thompson commented on CASSANDRA-10933:
---------------------------------------------

Looks like you're right.

> index_summary_upgrade_test.py failing
> -------------------------------------
>
>                 Key: CASSANDRA-10933
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10933
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Philip Thompson
>              Labels: dtest
>         Attachments: node1.log
>
>
> index_summary_upgrade_test.py is failing on HEAD for cassandra-3.0. The test 
> upgrades from 2.1.3 to 3.0, and checks the following behavior
> {code}
> # on startup, it should detect that the old-format sstable had its
> # index summary downsampled (forcing it to be rebuilt)
> node.watch_log_for("Detected erroneously downsampled index summary")
> {code}
> However, this is not happening. The node's log is attached. It is quite 
> possible that the "fix" here is that we only want to test upgrading from 
> 2.1.3 to 2.1.LATEST, but that's not for me to decide. I can easily implement 
> that, if that happens to be the case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to