cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Greene (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-373) storage-conf.xml reformatting
Date Wed, 19 Aug 2009 21:51:15 GMT


Michael Greene commented on CASSANDRA-373:

There are a few errors in the CommitLog area that Eric and I discussed on IRC that will need
to be fixed (including the legal values Bill mentions).

The path locations are just examples -- we have to choose something to default to, and the
best thing to default to would be a common standard.  Users are still, of course, able to
specify whatever writable paths they desire.

> storage-conf.xml reformatting
> -----------------------------
>                 Key: CASSANDRA-373
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>         Attachments: v1-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
> 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.

View raw message