cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3570) barrier-of-entry: make ./bin/cassandra -f work out of the box by changing default cassandra.yaml
Date Tue, 06 Dec 2011 02:27:40 GMT


Jonathan Ellis commented on CASSANDRA-3570:

As the only? committer not using a Unix-based primary workstation, I suppose it falls to me
to point out that /var/* is not a cross-platform standard either.
> barrier-of-entry: make ./bin/cassandra -f work out of the box by changing default cassandra.yaml
> ------------------------------------------------------------------------------------------------
>                 Key: CASSANDRA-3570
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>            Priority: Trivial
>         Attachments: CASSANDRA_3570-dbpath.txt
> This is probably going to be controversial. But how about the attached simple patch to
just have ./db exist, and then have Cassandra configured to use that by default? This makes
it a lot easier for people to just run Cassandra out of the working copy, whether you are
a developer or a user who wants to apply a patch when being assisted by a Cassandra developer.
> A real deployment with packaging should properly override these paths anyway, and the
default /var/lib stuff is pretty useless. Even if you are root on the machine, who it is much
cleaner to just run self-contained.
> Yes, I am aware that you can over-ride the configuration but honestly, that's just painful.
Especially when switching between various versions of Cassandra.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message