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

Stefania commented on CASSANDRA-10753:
--------------------------------------

bq. I guess we should be safe to update to the released 3.0.0 tag.

OK. There was a little bit of work to do because {{ColumnMetadata}} no longer 
has a property called {{index}}. I still have some cqlshlib IO errors on trunk 
that I haven't had time to investigate. I will resume mid next week.

bq. That's strange, it shouldn't take that long with such a small amount of 
data even on HDDs IMO. Maybe it's a ccm problem? CASSANDRA-8816 reported 
slowness on keyspace drop on Windows, so maybe you could run those tests and 
check if they're failing in your machine? Is it possible to enable tracing on 
drop keyspace statements? It would may be nice see what's making it so slow.

It's not a ccm problem because I am not using it; I'm using a simple 
{{cassandra -f}}. I cannot reproduce the failures of CASSANDRA-8816. From what 
I could see so far, the driver notifications were sent after several flush 
operations. I will add more trace messages and investigate next week. For now 
I've left the time-out to 20 seconds on all branches.

CI resubmitted on 2.2, 3.0 and trunk.


> Fix completion problems breaking clqshlib tests
> -----------------------------------------------
>
>                 Key: CASSANDRA-10753
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10753
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 3.0.x
>
>
> The recent changes in the python driver APIs have caused some completion 
> problems as indicated by 2 of these failing tests:
> http://cassci.datastax.com/job/trunk_cqlshlib/579/testReport/
> The third failing test, {{test_timestamp_output}}, has been failing for some 
> time due to uncertainty on what to do regarding timezone conversion but it 
> too can be changed to reflect the fact that we convert the timestamp to UTC.
> Finally, {{max_window_size_seconds}} was recently added to the compaction 
> properties and this caused 2 more tests to fail. It cannot be seen on Jenkins 
> because of the relative import problem introduced by CASSANDRA-9304. 



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

Reply via email to