You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nick Bailey (JIRA)" <ji...@apache.org> on 2010/06/30 17:25:53 UTC

[jira] Updated: (CASSANDRA-1196) Invalid UTF-8 data should cause exceptions

     [ https://issues.apache.org/jira/browse/CASSANDRA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Bailey updated CASSANDRA-1196:
-----------------------------------

    Attachment: 0001-Initial-fixes-to-utf-decoding.patch
                0002-Unit-test-for-UTF8-fixes.patch

Added a decode method to FBUtilities and changed partitioners to throw RuntimeExceptions on decoding failures.

> 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.