[
https://issues.apache.org/jira/browse/CASSANDRA-15962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268136#comment-17268136
]
Jacek Lewandowski commented on CASSANDRA-15962:
-----------------------------------------------
[~blerer] - could you also review PR against trunk
(https://github.com/apache/cassandra/pull/784) - as mentioned above there is
one extra change in comparison to 3.x PR
(https://github.com/apache/cassandra/pull/784/files#diff-24bf23a6435f78db7cf54aaf773f97c6355653443746a4750bec1cd01c0d4eddR329)
> Digest for some queries is different depending whether the data are retrieved
> from sstable or memtable
> ------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15962
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
> Attachments: DigestTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Not sure into which category should I assign this ticket.
>
> Basically when reading using certain column filters, the digest is different
> depending whether we read from sstable and memtable. This happens on
> {{trunk}} and {{cassandra-3.11}} branches. However it works properly on
> {{cassandra-3.0}} branch.
>
> I'm attaching a simple test for trunk to demonstrate what I mean.
>
> Please verify my test and my conclusions
>
--
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
