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

Alexey Zotov updated CASSANDRA-5165:
------------------------------------

    Description: 
Some misprints in cassandra-topology.properties file can be painful for 
debugging. For example extra symbols at the end of line like a space. So 
difference between "DC1:RACK1" and "DC1:RACK1 " couldn't be detected using 
nodetool ring command.

I think that symbols like a space shouldn't be allowed in DC/RACK names.  So I 
suggest to trim them.

The patch has been attached.


  was:
Some misprints in cassandra-topology.properties file can be painful for 
debugging. For example extra symbols at the end of line like a space. So 
difference between "DC1:RACK1" and "DC1:RACK1 " couldn't be detected using 
nodetool ring command.

I think that symbols like a space shouldn't be allowed in DC/RACK names.  So I 
suggest to trim them.

The patch has been attached.


    
> Need to trim DC and RACK names in cassandra-topology.properties file
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-5165
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5165
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.6
>         Environment: cassandra-1.1.6 (DataStax distribution).
>            Reporter: Alexey Zotov
>            Assignee: Alexey Zotov
>            Priority: Minor
>         Attachments: cassandra-1.2-5165_trim_spaces.txt
>
>
> Some misprints in cassandra-topology.properties file can be painful for 
> debugging. For example extra symbols at the end of line like a space. So 
> difference between "DC1:RACK1" and "DC1:RACK1 " couldn't be detected using 
> nodetool ring command.
> I think that symbols like a space shouldn't be allowed in DC/RACK names.  So 
> I suggest to trim them.
> The patch has been attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to