cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4775) Counters 2.0
Date Fri, 30 Nov 2012 19:40:00 GMT

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

Jonathan Ellis updated CASSANDRA-4775:
--------------------------------------

          Description: 
The existing partitioned counters remain a source of frustration for most users almost two
years after being introduced.  The remaining problems are inherent in the design, not something
that can be fixed given enough time/eyeballs.

Ideally a solution would give us
- similar performance
- less special cases in the code
- potential for a retry mechanism


  was:Orphaned from CASSANDRA-2495. Jonathan suggest that to achieve a healthy retry mechanism
for counter CFs, the backend of counters will require refactoring.

    Affects Version/s:     (was: 1.1.5)
        Fix Version/s: 1.3
           Issue Type: New Feature  (was: Improvement)
              Summary: Counters 2.0  (was: Refactor counters backend so that they can accomodate
a healthy retry mechanism)
    
> Counters 2.0
> ------------
>
>                 Key: CASSANDRA-4775
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4775
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Arya Goudarzi
>              Labels: counters
>             Fix For: 1.3
>
>
> The existing partitioned counters remain a source of frustration for most users almost
two years after being introduced.  The remaining problems are inherent in the design, not
something that can be fixed given enough time/eyeballs.
> Ideally a solution would give us
> - similar performance
> - less special cases in the code
> - potential for a retry mechanism

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

Mime
View raw message