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 (Created) (JIRA)" <ji...@apache.org> on 2011/11/29 19:39:40 UTC
[jira] [Created] (CASSANDRA-3541) Support timeuuid column names
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
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
[jira] [Updated] (CASSANDRA-3541) Support timeuuid column names
Posted by "Pavel Yaskevich (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich updated CASSANDRA-3541:
---------------------------------------
Attachment: CASSANDRA-3541-proper-type-paser-error-handling.patch
> 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.6
>
> Attachments: CASSANDRA-3541-proper-type-paser-error-handling.patch, 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
[jira] [Commented] (CASSANDRA-3541) Support timeuuid column names
Posted by "Brandon Williams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160126#comment-13160126 ]
Brandon Williams commented on CASSANDRA-3541:
---------------------------------------------
When you pass an invalid comparator, it throws a traceback instead of just saying it's invalid. Also, it's case-sensitive which is slightly annoying but I can live with that. Out of curiosity, why both UTF-8 and Ascii?
> 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
[jira] [Commented] (CASSANDRA-3541) Support timeuuid column names
Posted by "Pavel Yaskevich (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3541) Support timeuuid column names
Posted by "Brandon Williams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160269#comment-13160269 ]
Brandon Williams commented on CASSANDRA-3541:
---------------------------------------------
+1
> 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.6
>
> Attachments: CASSANDRA-3541-proper-type-paser-error-handling.patch, 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
[jira] [Updated] (CASSANDRA-3541) Support timeuuid column names
Posted by "Pavel Yaskevich (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich updated CASSANDRA-3541:
---------------------------------------
Attachment: CASSANDRA-3541.patch
option -U (--comparator) added which currently supports only {TimeUUID, Ascii, UTF8}Type.
> 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
[jira] [Commented] (CASSANDRA-3541) Support timeuuid column names
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164543#comment-13164543 ]
Hudson commented on CASSANDRA-3541:
-----------------------------------
Integrated in Cassandra #1243 (See [https://builds.apache.org/job/Cassandra/1243/])
Update to support TimeUUIDType (CASSANDRA-3541)
Patch by eevans; reviewed by Pavel Yaskevich for CASSANDRA-2268
eevans : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1211522
Files :
* /cassandra/trunk/tools/stress/src/org/apache/cassandra/stress/operations/CqlInserter.java
> 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.6
>
> Attachments: CASSANDRA-3541-proper-type-paser-error-handling.patch, 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