[
https://issues.apache.org/jira/browse/CASSANDRA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750690#action_12750690
]
Lance Weber commented on CASSANDRA-416:
---------------------------------------
Until configuration management is rehauled, I'm just looking to make a things
easier for user-developers who are trying to stay somewhat current and who do
not want to incur a ton of update pain when checking out cass updates locally.
This is a pretty minor change that allows us to decouple local configuration
settings from the cass code base without having to diff cassandra.in.sh to see
if there are new settings being recommended. If we aren't supposed to be using
cassandra.in.sh then there should probably be documentation that effect.
> modify cassandra.in.sh to only set $CASSANDRA_CONF if it is not already set
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-416
> URL: https://issues.apache.org/jira/browse/CASSANDRA-416
> Project: Cassandra
> Issue Type: Improvement
> Environment: unix/linux
> Reporter: Lance Weber
> Priority: Trivial
> Fix For: 0.5
>
> Attachments: cass_conf-patch.txt
>
>
> modify cassandra.in.sh 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.
