You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/09/01 01:53:07 UTC

[jira] [Commented] (CASSANDRA-4497) Update CQL pseudo-maps to real maps

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

Jonathan Ellis commented on CASSANDRA-4497:
-------------------------------------------

How is it more complicated to document that replication_parameters is a map like any other, than replication_parameters has its own one-off syntax that only exists for historical reasons?  I don't buy it.

bq. Also, it looks like there isn't any way to change one option and leave the other intact (like "WITH replication['replication_factor'] = 2", which it seems like ought to be implied by the use of the map syntax

Agreed, if we can fix this easily we should.

bq. What's the main motivation

Two motivations:
- reduce the special case weirdnesses exposed to users, as above
- reduce special case weirdnesses in our internal implementation (which is also exposed to "power users" in the system KS).  so much more pleasant to "select replication_options from schema_keyspaces where keyspace_name = 'foo'" and get a Map back.
                
> Update CQL pseudo-maps to real maps
> -----------------------------------
>
>                 Key: CASSANDRA-4497
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4497
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>              Labels: cql3
>             Fix For: 1.2.0 beta 1
>
>         Attachments: CASSANDRA-4497.patch
>
>
> - compression_parameters
> - replication_parameters (combine strategy + options like we did compression)
> - anything else?

--
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