cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-416) modify to only set $CASSANDRA_CONF if it is not already set
Date Wed, 02 Sep 2009 21:29:32 GMT


Eric Evans commented on CASSANDRA-416:

Could you elaborate a little about the problem you're trying to solve here?

The reason I ask: is meant as a sort of configuration for the startup script (bin/cassandra),
and it's pretty much a given that any serious use will require you to edit it or create your
own (though the defaults in bin/ are meant to be close enough that they should
work for a first-test).

Even when running from an SVN checkout, you can run a customized version of
(for example to use an alternate CASSANDRA_CONF) by doing something like...

CASSANDRA_INCLUDE=~/ bin/cassandra -f

You could even omit CASSANDRA_CONF entirely from your CASSANDRA_INCLUDE and pass it along
in the environment separately.

So, to summarize, I'm thinking that a) this shouldn't be needed, and that b) it might give
people the impression that we're expecting them to use an unaltered CASSANDRA_INCLUDE and
to set CASSANDRA_CONF, which isn't currently the case. 

Also, all of this would similarly apply to CLASSPATH and JVM_OPTS.

> modify to only set $CASSANDRA_CONF if it is not already set
> ---------------------------------------------------------------------------
>                 Key: CASSANDRA-416
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>         Environment: unix/linux
>            Reporter: Lance Weber
>            Priority: Trivial
>             Fix For: 0.5
>         Attachments: cass_conf-patch.txt
> modify to only set $CASSANDRA_CONF if it is not already set

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message