cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (CASSANDRA-932) Use cfids instead of cfnames for major operations.
Date Fri, 21 May 2010 16:05:17 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Dusbabek reopened CASSANDRA-932:
-------------------------------------


> Use cfids instead of cfnames for major operations.
> --------------------------------------------------
>
>                 Key: CASSANDRA-932
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-932
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.7
>            Reporter: Gary Dusbabek
>            Assignee: Stu Hood
>             Fix For: 0.7
>
>         Attachments: 0001-Remove-redundant-cfNamesMap-in-Table.patch, 0002-Add-easy-reverse-lookup-from-id-cf.patch,
0003-Remove-name-field-from-ColumnFamily-and-clean-up-mem.patch, 0004-modify-unit-tests-to-use-CFM.getId-and-to-lookup-CFS.patch
>
>
> CF.id() should be used in place of CF.name() for looking up column families.  
> In pragmatic terms this means that:
> * maps that store CF or CFS should use id as the key.
> * CF.name() should be eliminated and replaced by a toString() that includes the cfid
and name.
> * other things I can't immediately think of.
> We might even go so far as to change the way we name the sstable files to use cfid instead
of name.  This would make renaming CFs a simpler (and quicker) operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message