cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10338) Secondary index large values dtest failing on 3.0
Date Fri, 18 Sep 2015 14:24:04 GMT


Benjamin Lerer commented on CASSANDRA-10338:

{quote}If you mean non-LWT updates, they weren't affected (by 6237 or this patch).{quote}

It is true because we have some other check in {{addUpdates}}, which we can probably remove
in the future.
{{buildPartitionKeyNames}} is also used in {{CQLSSTableWriter}} and there I do not think that
we perfom any check but I did not look in details.


> Secondary index large values dtest failing on 3.0
> -------------------------------------------------
>                 Key: CASSANDRA-10338
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>             Fix For: 3.0.0 rc1
> {{secondary_index_test:TestSecondaryIndex.test_8280_validate_indexed_values}} has been
failing since build [#147|].
The most likely cause is CASSANDRA-6237 (though I haven't confirmed that). 
> The problem is that if an oversized value is provided, the validation for LWT statements
(both regular and in batches) is not performed up front, but when the {{Cql3CasRequest}} is
executed via {{StorageProxy}}. This causes a timeout, rather than an immediate validation
error & hence the test fails.

This message was sent by Atlassian JIRA

View raw message