[CASSANDRA-1196] Invalid UTF-8 keys [for legacy OPP] should cause exceptions - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Low
Resolution: Fixed
Fix Version/s: 0.7 beta 1
Component/s: None
Labels:
None

Description

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

0001-Initial-fixes-to-utf-decoding.patch
30/Jun/10 15:24
4 kB
Nick Bailey
0002-Better-Unit-Testing.patch
30/Jun/10 21:06
1 kB
Nick Bailey

Issue Links

relates to

CASSANDRA-1232 UTF8Type.compare() is slow and dangerous

Resolved

Activity

People

Assignee:: Nick Bailey

Reporter:: Stu Hood

Authors:: Nick Bailey

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Dates

Created:: 16/Jun/10 16:38

Updated:: 16/Apr/19 09:33

Resolved:: 01/Jul/10 01:26