cassandra-commits mailing list archives

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


Ariel Weisberg commented on CASSANDRA-13219:

This merged forward cleanly, but just to make sure it compiles I had cassci run the unit tests
and dtests for 2.2, 3.0, and 3.11.

The dtests failed when I started them initially:
[artifact:dependencies] Transferring 4K from central
[artifact:dependencies] Downloading: commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.pom
from repository apache at

Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Aborted by  : False
Logical operation result is FALSE
It's not clear why but I restarted one of them and that is running and seems happy.

I'll wait for the one to pass and if that is good enough for review I'll commit.

> Cassandra.yaml now unicode instead of ascii after 13090
> -------------------------------------------------------
>                 Key: CASSANDRA-13219
>                 URL:
>             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|].
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

View raw message