[
https://issues.apache.org/jira/browse/CASSANDRA-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua McKenzie updated CASSANDRA-7398:
---------------------------------------
Attachment: 7398_v9.txt
Attaching a simple v9 that checks the provided cassandra.config value and gives
a more informative error based on whether or not the user has provided a string
that conforms to the URI spec.
As I've stated previously, I feel pretty strongly that this isn't a place where
we need to add a lot of complexity (logic + unit tests) around trying to figure
out what the user actually intended to provide. Far simpler (and cleaner) to
just educate them on the fact that they need to provide a URI as that param and
exit.
> Missing flexibility to have file://<server>/<etc> vs. file:/// when loading
> config file cassandra.yaml
> ------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7398
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7398
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Cassandra 2.1.0-rc1-SNAPSHOT, Win 7
> Reporter: Marco Tulio Avila Cerón
> Assignee: Marco Tulio Avila Cerón
> Priority: Minor
> Labels: lhf, patch
> Fix For: 2.1.1
>
> Attachments: 7398_v9.txt, CASSANDRA-7398_prefix_v2.patch,
> CASSANDRA-7398_prefix_v3.patch, CASSANDRA-7398_prefix_v4.patch,
> trunk-7398_v5.txt, trunk-7398_v6.txt, trunk-7398_v7.txt, trunk-7398_v8.txt,
> trunk-7398_v8_impl.txt, trunk-7398_v8_test.txt
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The parameter in the VM options -Dcassandra.config= needs file:///
> Allow the user to have optional "file:///" when loading the config file from
> the filesystem
--
This message was sent by Atlassian JIRA
(v6.2#6252)
