cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10657) Re-enable/improve value skipping
Date Fri, 22 Jan 2016 19:36:40 GMT


Philip Thompson commented on CASSANDRA-10657:

This broke alter_rf_and_run_read_repair_test, the test for CASSANDRA-10655. As this is a follow-up
to 10655, is the new behavior expected?

Failure is [here|]
Potentially [now] invalid assumption from test
# Alter so RF=n but don't repair, then execute a query which selects only a subset of the
columns. Run this at
        # CL ALL on one of the nodes which doesn't currently have the data, triggering a read
repair. Although we're
        # only selecting a single column, the expectation is that the entire row is read on
each replica to construct
        # the digest responses as well as the full data reads for repair. So we expect that
after the read repair, all
        # replicas will have the entire row

> Re-enable/improve value skipping
> --------------------------------
>                 Key: CASSANDRA-10657
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 3.4
> This is a followup to CASSANDRA-10655, to re-enable the optimization of skipping values
for the columns that are not requested by users in a CQL query. See CASSANDRA-10655 for why
it was disabled, the goal here is to re-enable it minus the bugs.

This message was sent by Atlassian JIRA

View raw message