cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3541) Support timeuuid column names
Date Wed, 30 Nov 2011 16:43:40 GMT

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

Pavel Yaskevich commented on CASSANDRA-3541:
--------------------------------------------

Ok, i will catch RE exception and just print error message. About types - if we are going
to support many types in the future, I just thought that it might be a good idea to include
utf8 now too...
                
> Support timeuuid column names
> -----------------------------
>
>                 Key: CASSANDRA-3541
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3541
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 1.0.5
>
>         Attachments: CASSANDRA-3541.patch
>
>
> Real-world Cassandra applications often use "wide rows" to denormalize queries into.
 Most often, this means they do a lot of appending to existing rows, with few overwrites.
 An easy way to add this to Stress would be to allow specifying timeuuid column names (which
will be inherently sequential, or nearly so).  For forwards-compatibility, we could add a
--comparator option that only supports the existing Ascii type and the proposed UUID type,
to start with.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message