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 22:35:12 GMT


Pavel Yaskevich commented on CASSANDRA-4795:

bq. But fundamentally creating a last_seen_versions table with cfname (ksname?) is simply
not that onerous and is the Right Thing To Do.

For that specific case it's actually not worth it because it's always a single version as
there is no reason to keep older version around, so creating separate CF for one row with
empty value is overkill as specially as it's even not read that often and query wouldn't be
as convenient as it was with describe keyspace for that single piece of data.

bq. -1 from me, I get that change is painful for people who are abusing schema right now but
we really shouldn't be encouraging this.

It's usually one/two attributes that go there so I think it's pretty convenient to store it
that way instead of dealing with separate CF/querying, but I'm welcome to new ideas
> 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: 0001-Reallow-unexpected-strategy-options-for-thrift.txt, 0002-Reallow-unexpected-strategy-options-for-thrift.txt,
0003-Adds-application_metadata-field-to-ks-metadata.txt, 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

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