cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (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 Mon, 05 Dec 2011 06:15:39 GMT


Peter Schuller commented on CASSANDRA-3570:

I didn't know about test-run, no. Thanks! I've had some scripts that re-configure and switch
around data directories and such that have facilitated switching between versions. But, they
were always hacky.

If you're saying people are actually using the default then maybe it's worth keeping. I'm
just not seeing who is using it. If you're the developer or user patching manually in the
working copy, ./db seems convenient. If you're packaging, you're gonna configure it properly
anyway. If you're deploying a non-packaged version, aren't you then also making an active
choice as to where you'll put the database?

Anyways, I'm not too fussed. It doesn't affect me all that much. I just remember a couple
of times introducing people and it being an annoyance that the very first experience requires
you to change settings you don't know anything about, before being able to run it.

Maybe this is different for the binary distribution; honestly I've never even used it :)

Anyway, if there's no +1 soon I'll just WONTFIX this one.

> 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