[ https://issues.apache.org/jira/browse/CASSANDRA-15503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104349#comment-17104349 ]
Andres de la Peña commented on CASSANDRA-15503: ----------------------------------------------- Thanks for the review. Committed to 3.11 branch as [406a8596eb7ad18079df20121521b1c659063ef4|https://github.com/apache/cassandra/commit/406a8596eb7ad18079df20121521b1c659063ef4] and merged up to [trunk|https://github.com/apache/cassandra/commit/5f61e94ea5d25aae1eb96e74512e55edef1cef14]. Dtest changes committed as [10ff82bf779289da913b40c1058fd85bd748c986|https://github.com/apache/cassandra-dtest/commit/10ff82bf779289da913b40c1058fd85bd748c986]. > Slow query log indicates opposite LTE when GTE operator > ------------------------------------------------------- > > Key: CASSANDRA-15503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15503 > Project: Cassandra > Issue Type: Bug > Components: Observability/Logging > Reporter: Wallace Baggaley > Assignee: Andres de la Peña > Priority: Normal > Fix For: 3.11.7, 4.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Slow query log is indicating a '<=' when a ">=" operator was sent. This > appears to be a logging only issue, but it threw off development for a day > figuring this out. Please fix. > How to reproduce. Set slow query log timeout to 1 millisecond. > In cqlsh run > {noformat} > CREATE TABLE atable ( > .id text, > timestamp timestamp, > PRIMARY KEY ((id), timestamp) > ) WITH CLUSTERING ORDER BY (timestamp DESC); > insert into atable (id, timestamp) VALUES ( '1',1); > insert into atable (id, timestamp) VALUES ( '2',2); > insert into atable (id, timestamp) VALUES ( '3',3); > insert into atable (id, timestamp) VALUES ( '4',4); > insert into atable (id, timestamp) VALUES ( '5',5); > insert into atable (id, timestamp) VALUES ( '6',6); > insert into atable (id, timestamp) VALUES ( '7',7); > insert into atable (id, timestamp) VALUES ( '8',8); > insert into atable (id, timestamp) VALUES ( '9',9); > insert into atable (id, timestamp) VALUES ( '10',10); > insert into atable (id, timestamp) VALUES ( '11',11); > select * from atable where timestamp >= '1970-01-01 00:00:00.006+0000' allow > filtering; > {noformat} > In the logs it prints: > {noformat} > DEBUG 1 operations were slow in the last 5003 msecs: > <SELECT * FROM ks.atable WHERE timestamp <= 1970-01-01 00:00Z LIMIT 100>, > time 7 msec - slow timeout 1 msec > {noformat} > But the query works appropriately and returns > {noformat} > id | timestamp > ----+--------------------------------- > 6 | 1970-01-01 00:00:00.006000+0000 > 7 | 1970-01-01 00:00:00.007000+0000 > 9 | 1970-01-01 00:00:00.009000+0000 > 10 | 1970-01-01 00:00:00.010000+0000 > 8 | 1970-01-01 00:00:00.008000+0000 > 11 | 1970-01-01 00:00:00.011000+0000 > (6 rows) > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org