cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10193) Downgrade Row.columns() to Collection<ColumnDefinition>
Date Fri, 28 Aug 2015 07:51:45 GMT

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

Benedict updated CASSANDRA-10193:
---------------------------------
    Priority: Major  (was: Minor)

> Downgrade Row.columns() to Collection<ColumnDefinition>
> -------------------------------------------------------
>
>                 Key: CASSANDRA-10193
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10193
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>             Fix For: 3.0.0 rc1
>
>
> There's not really a lot of reason to store a Columns instance in each row. Retaining
it introduces extra costs on every row merge, in both consumed CPU time and heap. 
> While working on CASSANDRA-10045 it became apparent this would be very easy to remove,
however to avoid scope creep I have filed this as a follow up ticket.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message