[
https://issues.apache.org/jira/browse/CASSANDRA-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259428#comment-14259428
]
Mike Adamson commented on CASSANDRA-8534:
-----------------------------------------
If the configURL fails to load as a URL then the code attempts to load the
configuration as a resource which does not need the file:// prefix. This code
must work because the default launch scripts do not add the cassandra.config
system property and they successfully find a cassandra.yaml from the classpath.
> The default configuration URL does not have the required file:// prefix and
> throws an exception if cassandra.config is not set.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8534
> Project: Cassandra
> Issue Type: Bug
> Components: Config, Core
> Environment: Any
> Reporter: Andrew Trimble
> Fix For: 2.1.3
>
> Attachments: error.txt
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> In the class org.apache.cassandra.config.YamlConfigurationLoader, the
> DEFAULT_CONFIGURATION is set to "cassandra.yaml". This is improperly
> formatted as it does not contain the prefix "file://". If this value is used,
> a ConfigurationException is thrown (see line 73 of the same class).
> A solution is to set the cassandra.config system property, but this does not
> solve the underlying problem. A vanilla Cassandra installation will throw
> this error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
