[
https://issues.apache.org/jira/browse/CASSANDRA-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162292#comment-13162292
]
Eric Evans commented on CASSANDRA-3570:
---------------------------------------
bq. 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.
Just playing Devil's advocate here, but is this really optimizing for the
new/first-time users, or for someone who does a lot of ad hoc testing?
> barrier-of-entry: make ./bin/cassandra -f work out of the box by changing
> default cassandra.yaml
> ------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-3570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3570
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
