[
https://issues.apache.org/jira/browse/CASSANDRA-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576438#comment-13576438
]
Sylvain Lebresne commented on CASSANDRA-4795:
---------------------------------------------
bq. changing this in 1.2.1 probably was a bit unfair to people
If you mean "in a minor release", then I agree, mea culpa.
But on the principle, I disagree that we should allow people to shove random
metadata in the stategy options. Especially because that means not validating
correctly the actual strategy options (and no, warning in the log is not a good
enough because 1) application developer may not have easy access to the server
log and 2) asking people to check the server log when they do query to see if
they hadn't mispelled some option is a ridiculously bad user experience).
If application want to store data, they should create a column family and store
data in there. But to be clear, I'm open to discussing adding some new
application_metadata field to the column family metadata that would explicitely
be uninterpreted by Cassandra (not that I'm particularly thrilled by the idea,
but I'm at least open to it), but the strategy options is just not the right
place for that.
So I'm fine reverting this from 1.2 (in which case I'd still prefer keeping the
validation at least on the CQL3 side), not so much from trunk.
> replication, compaction, compression? options are not validated
> ---------------------------------------------------------------
>
> Key: CASSANDRA-4795
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4795
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Reporter: Brandon Williams
> Assignee: Dave Brosius
> Priority: Minor
> Fix For: 1.2.1
>
> Attachments: 4795.compaction_strategy.txt,
> 4795_compaction_strategy_v2.txt, 4795_compaction_strategy_v3.txt,
> 4795.replication_strategy.txt
>
>
> When creating a keyspace and specifying strategy options, you can pass any
> k/v pair you like.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
