cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10162) Test regression for cqlsh_tests.TestCqlsh.test_describe
Date Thu, 27 Aug 2015 07:09:46 GMT

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

Sylvain Lebresne commented on CASSANDRA-10162:
----------------------------------------------

Well, that's because the dtest was [wrongly changed to match the buggy output|https://github.com/riptano/cassandra-dtest/commit/a029745f0ebd69122694f5182915c11c30aaf2a2]
while that ticket was being reviewed/committed. I've reverted that change to dtest so we should
be good as soon as cassci picks that up.

> Test regression for  cqlsh_tests.TestCqlsh.test_describe
> --------------------------------------------------------
>
>                 Key: CASSANDRA-10162
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10162
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 3.0 beta 2
>
>
> The regression is due to the commit db782362aaf25214a94c393b20cdbade829c5291 from CASSANDRA-6717,
the one that switched to using frozen sets and maps in schema tables.
> The problem is that after this patch, the maps and sets are not sorted anymore, which
confuse the test in question. Now, we document that maps and sets are sorted, and that should
be true for frozen ones too so it's a legit bug imo, not a problem of the test.



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

Mime
View raw message