cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13219) Cassandra.yaml now unicode instead of ascii after 13090
Date Tue, 14 Feb 2017 21:05:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866667#comment-15866667
] 

Jason Brown commented on CASSANDRA-13219:
-----------------------------------------

+1. I checked it out via hexdump and in the original I can see the utf-encoded value, and
with the new patch i see the ascii values.

> Cassandra.yaml now unicode instead of ascii after 13090
> -------------------------------------------------------
>
>                 Key: CASSANDRA-13219
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13219
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Philip Thompson
>            Assignee: Ariel Weisberg
>            Priority: Minor
>             Fix For: 2.2.9, 3.0.11, 3.11.0, 4.0
>
>         Attachments: utf8-to-ascii_yaml.patch
>
>
> After CASSANDRA-13090, which was commit 5725e2c422d21d8efe5ae3bc4389842939553650, cassandra.yaml
now has unicode characters, specifically [0xe2|http://utf8-chartable.de/unicode-utf8-table.pl?start=8320&number=128&names=2&utf8=0x].
Previously, it was only ascii.
> This is an admittedly minor change, but it is breaking. It affects (at least) a subset
of python yaml parsing tools (which is a large number of tools that use C*).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message