cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4795) replication, compaction, compression? options are not validated
Date Tue, 12 Feb 2013 07:43:13 GMT


Pavel Yaskevich commented on CASSANDRA-4795:

bq. If you mean "in a minor release", then I agree, mea culpa.

That's exactly what I mean.

bq. 1) application developer may not have easy access to the server log 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 the original intention was to protect people from mistypes then maybe we need to put more
work and throw exception only if typed in is similar to what it should be, like git does e.g.
"option rplicatian_factor is not recognized maybe you mean 'replication_factor'?" ? Requiring
those options to be typed in by the user especially with such a long names that we have already
is a "ridiculously bad user experience", especially when those names/options change frequently
between releases.

bq. 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 in the case of Titan when they just want to save one 'last seen version' attribute, creating
a separate column family or even having that per-cf doesn't make any sense but it's pretty
convenient to keep it in the keypsace strategy options (without have any other alternatives)
because it's not updated or even read that often.
> replication, compaction, compression? options are not validated
> ---------------------------------------------------------------
>                 Key: CASSANDRA-4795
>                 URL:
>             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,
> When creating a keyspace and specifying strategy options, you can pass any k/v pair you

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:

View raw message