cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Webb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4448) CQL3: allow to define a per-cf default consistency level
Date Fri, 06 Dec 2013 05:33:40 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840997#comment-13840997
] 

David Webb commented on CASSANDRA-4448:
---------------------------------------

Here is a schema from DSE 3.1.3 / C* 1.2.6.6 that includes them. This is just to let you know
that I think they did sneak in there for a while.  Some tools like the Pentaho Cassandra connector
were depending on their existence, and it appears the were removed somewhere between 1.2.8
and 1.2.10.  I cannot tell for sure.  Thanks for shedding light on the situation and we will
proceed as if they will not exists ever again. :) The connector will be updated soon.  Thanks
Jonathan.

{code}
[cqlsh 3.1.2 | Cassandra 1.2.6.6 | CQL spec 3.0.0 | Thrift protocol 19.36.0]
Use HELP for help.
cqlsh> use system
   ... ;
cqlsh:system> describe table schema_columnfamilies;

CREATE TABLE schema_columnfamilies (
  keyspace_name text,
  columnfamily_name text,
  bloom_filter_fp_chance double,
  caching text,
  column_aliases text,
  comment text,
  compaction_strategy_class text,
  compaction_strategy_options text,
  comparator text,
  compression_parameters text,
  default_read_consistency text,
  default_validator text,
  default_write_consistency text,
  gc_grace_seconds int,
  id int,
  key_alias text,
  key_aliases text,
  key_validator text,
  local_read_repair_chance double,
  max_compaction_threshold int,
  min_compaction_threshold int,
  populate_io_cache_on_flush boolean,
  read_repair_chance double,
  replicate_on_write boolean,
  subcomparator text,
  type text,
  value_alias text,
  PRIMARY KEY (keyspace_name, columnfamily_name)
) WITH
  bloom_filter_fp_chance=0.010000 AND
  caching='KEYS_ONLY' AND
  comment='ColumnFamily definitions' AND
  dclocal_read_repair_chance=0.000000 AND
  gc_grace_seconds=8640 AND
  read_repair_chance=0.000000 AND
  replicate_on_write='true' AND
  populate_io_cache_on_flush='false' AND
  compaction={'class': 'SizeTieredCompactionStrategy'} AND
  compression={'sstable_compression': 'SnappyCompressor'};
{code}

> CQL3: allow to define a per-cf default consistency level
> --------------------------------------------------------
>
>                 Key: CASSANDRA-4448
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4448
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>              Labels: cql3
>             Fix For: 1.2.0 beta 1
>
>         Attachments: 4448.txt
>
>
> One of the goal of CQL3 is that client library should not have to parse queries to provide
a good experience. In particular, that means such client (that don't want to parse queries)
won't be able to allow the user to define a specific default read/write consistency level
per-CF, forcing user to specific the consistency level with every query, which is not very
user friendly.
> This ticket suggests the addition of per-cf default read/write consitency level. Typically
the syntax would be:
> {noformat}
> CREATE TABLE foo (...)
> WITH DEFAULT_READ_CONSISTENCY = QUORUM
>  AND DEFAULT_WRITE_CONSISTENCY = QUORUM
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message