You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Johan Oskarsson (JIRA)" <ji...@apache.org> on 2009/03/31 12:21:50 UTC

[jira] Created: (CASSANDRA-27) Add jira components

Add jira components
-------------------

                 Key: CASSANDRA-27
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
             Project: Cassandra
          Issue Type: Task
            Reporter: Johan Oskarsson


To make it easier to navigate the tickets we should create components in jira.


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


Re: [jira] Commented: (CASSANDRA-27) Add jira components

Posted by Sandeep Tata <sa...@gmail.com>.
> And a lot of our issues have to do with making cassandra suck less to run, such as "Log runtime stats for analysis by ops," "HashingStrategy does not default to RANDOM," and a bunch of resolved ones.  I can't think of a good name for that category...

"Miscellaneous" :-)

[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731590#action_12731590 ] 

Eric Evans commented on CASSANDRA-27:
-------------------------------------

+1 tools, core, docs + site categories

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702476#action_12702476 ] 

Jonathan Ellis commented on CASSANDRA-27:
-----------------------------------------

As I said in IRC, I'm not in a hurry to categorize since I think a poor set of categories is worse than none.

Sandeep's suggestion is a good start but my feeling is out of our slightly over 100 issues we have 90 for category 1, 10 for category 4, and a handful for the others.

What I think would be useful of a histogram of svn log -v by file; that would be more useful than trying to come up with categories on an ad-hoc basis.

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731547#action_12731547 ] 

Michael Greene commented on CASSANDRA-27:
-----------------------------------------

Tools, Core, Documentation & Site

These three make sense to me.  As Evan notes, there are usually very few issues in the queue.  As Cassandra grows, I could see Tools or Core splitting as other people have them above.  It'd be nice to just be done with this issue and if we ever have a specific problem with the organization in the future, make a new one.

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704825#action_12704825 ] 

Jonathan Ellis commented on CASSANDRA-27:
-----------------------------------------

I tried out something along the lines of that histogram: http://spyced.blogspot.com/2009/04/automatic-project-structure-inference.html

Here's my stab at categories, partly based on that:

1. project infrastructure
2. storage layer (sstable, memtable, sequencefile, etc.)
3. client api
4. read logic
5. ring management (partitioner, dht, gms, etc.)
6. tools
7. other


> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731593#action_12731593 ] 

Michael Greene commented on CASSANDRA-27:
-----------------------------------------

Let's do it! Here's the breakdown at the moment, from what I can tell.
Tools - 234, 252, 289, 292
Docs & Site - 231
Core - everything else outstanding.

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Sandeep Tata (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704918#action_12704918 ] 

Sandeep Tata commented on CASSANDRA-27:
---------------------------------------

+1 to adding a separate docs component.

Could we expand "read logic" to include "read/write logic" ? (I know there is a lot more logic around reads than writes right now, but I'm guessing you meant read/write logic)




> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731559#action_12731559 ] 

Jonathan Ellis commented on CASSANDRA-27:
-----------------------------------------

+1 tools, core, docs + site categories

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731126#action_12731126 ] 

Eric Evans commented on CASSANDRA-27:
-------------------------------------

4 months later and thus far we've never had much more than 50 issues outstanding at any one time, and to the best of my knowledge, there haven't been any reporting use cases that would have benefited from the proposed components.

I'm almost inclined to say that we should continue for the foreseeable future without any components, and close this ticket.

However, I will propose the following components instead:

 - documentaton
 - tools (cli, nodeprobe, etc)
 - infrastructure (start scripts, build.xml, etc)
 - site/wiki
 - storage/core (basically, everything else)

I believe this list (or one like it) is short enough, and simple enough, that it can be properly used without becoming onerous, and that it sufficiently categorizes things to make it easy for contributors to drill in on something that interests them.




> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704917#action_12704917 ] 

Johan Oskarsson commented on CASSANDRA-27:
------------------------------------------

Looks good to me, perhaps add a docs component?

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Sandeep Tata (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694892#action_12694892 ] 

Sandeep Tata commented on CASSANDRA-27:
---------------------------------------

Here's a list of components that makes sense to me:

1. Cassandra DB (all the code in the cassandra.db and cassandra.io packages -- we could split this in two)
2. Ring Management Logic (dht, gms, locator)
3. Messaging (cassandra.net.* )
4. APIs (thrift code, related code in cassandra.service)
5. Utilities and Tools
6. CQL
7. Other

Comments?

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694931#action_12694931 ] 

Johan Oskarsson commented on CASSANDRA-27:
------------------------------------------

+1 for Sandeep's suggestion, looks like a great start

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694053#action_12694053 ] 

Johan Oskarsson commented on CASSANDRA-27:
------------------------------------------

Which components do we want to add?
I'll leave it up to someone who is more familiar with the codebase then me, but perhaps some of these would make it?

cql
test
commitlog
memtable
gossiper

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Resolved: (CASSANDRA-27) Add jira components

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-27.
-------------------------------------

    Resolution: Fixed

created components & assigned open issues.

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694589#action_12694589 ] 

Jonathan Ellis commented on CASSANDRA-27:
-----------------------------------------

I don't have a good feel for what the components should be yet, either.

Definitely Service [client interaction], past that I am not sure if it makes more sense to divide by class (Memtable, SSTable, CommitLog) or operation (read, write, bootstrap, gossip, ...)

And a lot of our issues have to do with making cassandra suck less to run, such as "Log runtime stats for analysis by ops," "HashingStrategy does not default to RANDOM," and a bunch of resolved ones.  I can't think of a good name for that category...

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Assigned: (CASSANDRA-27) Add jira components

Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Oskarsson reassigned CASSANDRA-27:
----------------------------------------

    Assignee: Jonathan Ellis

Assigning to Jonathan who can add these

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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


[jira] Commented: (CASSANDRA-27) Add jira components

Posted by "Sandeep Tata (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702571#action_12702571 ] 

Sandeep Tata commented on CASSANDRA-27:
---------------------------------------

True, we're probably fine for the near future without components. 

The higher level comment is, over the last couple of months, much of the work seems to have gone into fixing the db node (adding remove support, fixing data-loss bugs, new get apis, refactoring the read path some). I'm guessing the histogram will change when we start working with the messaging layer :)

> Add jira components
> -------------------
>
>                 Key: CASSANDRA-27
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-27
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Johan Oskarsson
>            Assignee: Jonathan Ellis
>
> To make it easier to navigate the tickets we should create components in jira.

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