cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-373) storage-conf.xml reformatting
Date Wed, 19 Aug 2009 21:57:14 GMT

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

Eric Evans updated CASSANDRA-373:
---------------------------------

    Attachment: v3-0001-CASSANDRA-373-re-format-factor-conf-storage-conf.xml.txt

> storage-conf.xml reformatting
> -----------------------------
>
>                 Key: CASSANDRA-373
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-373
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>         Attachments: v1-0001-CASSANDRA-373-re-format-factor-conf-storage-conf.xml.txt,
v2-0001-CASSANDRA-373-re-format-factor-conf-storage-conf.xml.txt, v3-0001-CASSANDRA-373-re-format-factor-conf-storage-conf.xml.txt
>
>
> Our sample config (conf/storage-conf.xml) is the canonical source of configuration documentation.
As such readability should be a priority, and it should serve as the best possible basis for
customization.
> I propose the following:
> 1. Wherever possible, lines should wrap at 75 chars. The file will be edited post-installation
by operational personnel, who are often confined to standard 80 character terminals.
> 2. Indention of 2 spaces to make maximum use of horizontal real estate.
> 3. More distinctive multi-line comments.
> 4. Path locations that conform to the FHS.
> Patch to follow...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message