[
https://issues.apache.org/jira/browse/CASSANDRA-14956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757569#comment-16757569
]
Joseph Lynch edited comment on CASSANDRA-14956 at 1/31/19 6:22 PM:
-------------------------------------------------------------------
[~beobal] I think that the merge up to trunk broke trunk test runs (e.g.
[7d138e20|https://circleci.com/gh/jolynch/cassandra/415]). I think it has to do
with re-using the data directory from {{cassandra-murmur.yaml}}, debugging it
now but do you think we need a separate ticket for fixing that test or I can
just submit a fixup patch here?
Confirmed it's a pollution issue with the {{EmbeddedCassandraService}} by
running two tests that both use it:
{noformat}
$ cat testlist.txt
org/apache/cassandra/audit/AuditLoggerTest.java
org/apache/cassandra/cql3/PagingTest.java
$ ant testclasslist -Dtest.classlistfile=$(pwd)/testlist.txt
...
[junit-timeout] Testsuite: org.apache.cassandra.cql3.PagingTest
[junit-timeout] Testsuite: org.apache.cassandra.cql3.PagingTest Tests run: 0,
Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 5.241 sec
[junit-timeout]
[junit-timeout] Testcase: org.apache.cassandra.cql3.PagingTest: Caused an ERROR
[junit-timeout] Unable to gossip with any peers
[junit-timeout] java.lang.RuntimeException: Unable to gossip with any peers
[junit-timeout] at
org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1546)
[junit-timeout] at
org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:553)
[junit-timeout] at
org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:841)
[junit-timeout] at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:699)
[junit-timeout] at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:650)
[junit-timeout] at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:379)
[junit-timeout] at
org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:501)
[junit-timeout] at
org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
[junit-timeout] at
org.apache.cassandra.cql3.PagingTest.setup(PagingTest.java:63)
[junit-timeout]
[junit-timeout]
[junit-timeout] Testcase: org.apache.cassandra.cql3.PagingTest: Caused an ERROR
[junit-timeout] null
[junit-timeout] java.lang.NullPointerException
[junit-timeout] at
org.apache.cassandra.cql3.PagingTest.tearDown(PagingTest.java:81)
[junit-timeout]
[junit-timeout]
...
{noformat}
was (Author: jolynch):
[~beobal] I think that the merge up to trunk broke trunk test runs (e.g.
[7d138e20|https://circleci.com/gh/jolynch/cassandra/415]). I think it has to do
with re-using the data directory from {{cassandra-murmur.yaml}}, debugging it
now but do you think we need a separate ticket for fixing that test or I can
just submit a fixup patch here?
> Paged Range Slice queries with DISTINCT can drop rows from results
> ------------------------------------------------------------------
>
> Key: CASSANDRA-14956
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14956
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Major
> Fix For: 2.1.21, 2.2.14
>
>
> If we have a partition where the first CQL row is fully deleted (possibly via
> TTLs), and that partition happens to fall on the page boundary of a paged
> range query which is using SELECT DISTINCT, the next live partition *after*
> it is omitted from the result set. This is due to over fetching of the pages
> and a bug in trimming those pages where overlap occurs.
> This does not affect 3.0+.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
