cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3570) barrier-of-entry: make ./bin/cassandra -f work out of the box by changing default cassandra.yaml
Date Wed, 07 Dec 2011 13:58:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164403#comment-13164403
] 

Eric Evans commented on CASSANDRA-3570:
---------------------------------------

bq. 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.

Yeah, fair enough.  Though if this is something that falls into the category of cant-be-guessed-so-recommend,
then an FHS-based recommendation is still the clear choice.  Maybe there should be some entries
adjacent to these, commented out, which include the corresponding recommended Windows paths.

Also, I just had one other thought.  Paths in {{cassandra.yaml}} are all expected to be absolute.
 The startup scripts are smart enough to work with relative paths when called from elsewhere,
but a relative path of db/ placed in {{cassandra.yaml}} will fail unless $PWD at startup is
the top-level directory.  I know this is meant to optimize for that case, but that's still
kind of dodgy.
                
> 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

        

Mime
View raw message