You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2017/02/14 20:00:44 UTC

[jira] [Updated] (CASSANDRA-13219) Cassandra.yaml now unicode instead of ascii after 13090

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

Philip Thompson updated CASSANDRA-13219:
----------------------------------------
    Summary: Cassandra.yaml now unicode instead of ascii after 13090  (was: Cassandra.yaml now unicode instead of ascii after )

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