cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1196) Invalid UTF-8 keys [for legacy OPP] should cause exceptions
Date Thu, 01 Jul 2010 01:27:52 GMT


Jonathan Ellis commented on CASSANDRA-1196:

committed, w/ util decode changed to throw CharacterCodingException (which is a subclass of
IOException, re-throwing as the latter loses information rather than adding it) and using

> Invalid UTF-8 keys [for legacy OPP] should cause exceptions
> -----------------------------------------------------------
>                 Key: CASSANDRA-1196
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7
>            Reporter: Stu Hood
>            Assignee: Nick Bailey
>            Priority: Minor
>             Fix For: 0.7
>         Attachments: 0001-Initial-fixes-to-utf-decoding.patch, 0002-Better-Unit-Testing.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.

View raw message