[
https://issues.apache.org/jira/browse/CASSANDRA-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875656#comment-14875656
]
Sam Tunnicliffe commented on CASSANDRA-10338:
---------------------------------------------
bq.The patch will work for the LWT statements but will miss the other ones.
If you mean non-LWT updates, they weren't affected (by 6237 or this patch). In
fact the dtest covers both variants, and it passed with the original patch.
That said, putting the check back where it came from is a better solution
anyway, so I've force-pushed an update which does just that.
> Secondary index large values dtest failing on 3.0
> -------------------------------------------------
>
> Key: CASSANDRA-10338
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10338
> 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|http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/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
(v6.3.4#6332)
