[
https://issues.apache.org/jira/browse/CASSANDRA-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866577#comment-15866577
]
Jeremiah Jordan edited comment on CASSANDRA-13219 at 2/14/17 8:39 PM:
----------------------------------------------------------------------
+1 fix LGTM
{code}
$ pcregrep --color='auto' -n '[^\x00-\x7F]' conf/cassandra.yaml
964:# On bare metal, the floor for packet processing throughput is high enough
that many applications won���t notice, but in
966:# surprisingly low compared to the throughput of task processing that is
possible inside a VM. It���s not that bare metal
967:# doesn���t benefit from coalescing messages, it���s that the number of
packets a bare metal network interface can process
$ git apply ~/Downloads/utf8-to-ascii_yaml.patch
$ pcregrep --color='auto' -n '[^\x00-\x7F]' conf/cassandra.yaml
$
{code}
was (Author: jjordan):
+1 fix LGTM
> 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)
