[
https://issues.apache.org/jira/browse/CASSANDRA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883955#action_12883955
]
Stu Hood commented on CASSANDRA-1196:
-------------------------------------
Looks good! For your testcase, JUnit 4 supports "expected exception"
annotations, like:
{co...@test(expected=IOException.class){code}
We can clean up UTF8Type, and use this decode method in CASSANDRA-1232.
> Invalid UTF-8 data should cause exceptions
> ------------------------------------------
>
> Key: CASSANDRA-1196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1196
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stu Hood
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.7
>
> Attachments: 0001-Initial-fixes-to-utf-decoding.patch,
> 0002-Unit-test-for-UTF8-fixes.patch
>
>
> Our current method for decoding UTF-8 data in OrderPreservingPartitioner and
> CollatingOrderPreservingPartitioner will silently decode invalid UTF-8 data.
> This may also be a problem UTF8Type.
> Instead, we should probably throw an exception, since bad UTF-8 data means
> either user error or corruption.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
