[jira] [Commented] (CASSANDRA-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256631#comment-13256631 ] Jonathan Ellis commented on CASSANDRA-556: -- Trivium: this was our oldest open issue. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: jmx, lhf > Fix For: 1.1.1 > > Attachments: cf_snapshots_556.diff, cf_snapshots_556_2.diff, > cf_snapshots_556_2A.diff > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255082#comment-13255082 ] Jonathan Ellis commented on CASSANDRA-556: -- Ah, I see. Quite right, CF names are not unique. (So what you could do is check the schema nodetool-side and spit back a "which KS did you want to snapshot CF in?" error...) > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > Attachments: cf_snapshots_556.diff > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255077#comment-13255077 ] Dave Brosius commented on CASSANDRA-556: if one did nodetool snapshot -cf foo that could potentially take snapshots of multiple 'foo's (one each in multiple keyspaces) which might be something the admin wasn't realizing... right? or am i wrong and cf names are unique across the cluster? > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > Attachments: cf_snapshots_556.diff > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255072#comment-13255072 ] Jonathan Ellis commented on CASSANDRA-556: -- bq. then you have the potential situation of n keyspaces with a cf name Not sure I follow, could you elaborate? > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > Attachments: cf_snapshots_556.diff > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255055#comment-13255055 ] Dave Brosius commented on CASSANDRA-556: the issue with -flags, is then you have the potential situation of n keyspaces with a cf name... which might be confusing... hopefully people don't have the same cf name in multiple keyspaces. -flags is also different then the way other commands handle cfs. But i'm fine with doing it that way as well. If that were the case there would be only one jmx call i would think. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > Attachments: cf_snapshots_556.diff > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255045#comment-13255045 ] Jonathan Ellis commented on CASSANDRA-556: -- bq. Just wanted to make sure folks were ok with splitting the command as it is I guess the main alternative would be to add more -flags... I'm okay breaking backwards compatibility there. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > Attachments: cf_snapshots_556.diff > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255038#comment-13255038 ] Dave Brosius commented on CASSANDRA-556: Sure that's fine, i'll fix tonite. Just wanted to make sure folks were ok with splitting the command as it is. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > Attachments: cf_snapshots_556.diff > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255029#comment-13255029 ] Jonathan Ellis commented on CASSANDRA-556: -- Thanks, Dave! I think it would be good to split up the method calls at the JMX level as well, since it doesn't really make sense to apply a specific CF name AND multiple keyspaces at the same time. What do you think? Nit: help in nodecommand adds a second line for "snapshot" instead of "snapshot_columnfamily" > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Assignee: Dave Brosius >Priority: Minor > Labels: lhf > Fix For: 1.1.1 > > Attachments: cf_snapshots_556.diff > > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157511#comment-13157511 ] Jonathan Ellis commented on CASSANDRA-556: -- Sounds reasonable. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157489#comment-13157489 ] Victor Z. Peng commented on CASSANDRA-556: -- I assume we don't need to support specific column family for CLEARSNAPSHOT? It's harder to implement and I think we don't have a use case in practice at the moment? > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144342#comment-13144342 ] Jonathan Ellis commented on CASSANDRA-556: -- Right. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144327#comment-13144327 ] Victor Z. Peng commented on CASSANDRA-556: -- You are right! I want to start with this fix now. My first fix for Cassandra :) 3 more questions: Do I have to start after I have been assigned to this bug? Or just write and submit? No tests for NodeTool? NodeTool Wiki page not updated. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144301#comment-13144301 ] Jonathan Ellis commented on CASSANDRA-556: -- I think it would be more consistent w/ the other options to just add an optional (single) columnfamily argument at the end. If you want to snapshot more than one you can always issue multiple snapshot commands. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144285#comment-13144285 ] Victor Z. Peng commented on CASSANDRA-556: -- It seems the implementation is not very hard, we simply just add more helper functions that could handle the request to snapshot a subset of columns, since org.apache.cassandra.db.Table#snapshot is snapshotting columns one by one already. One thing's worth discussing is how we support specifying both multi-tables and multi-columns simultaneously via NodeTool in CLI. What i propose is we add a '-c' option, which will accept an argument as column names. Since an option can accept at most on argument, the argument can be formatted as comma separated string: "-c col1,col2,col3". When -c is absent, we default it to all columns. Does this sound ok? > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133761#comment-13133761 ] Jonathan Ellis commented on CASSANDRA-556: -- An admin has to edit the Contributor list, but in the meantime, commenting here as you did is sufficient. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133684#comment-13133684 ] Victor Z. Peng commented on CASSANDRA-556: -- sorry. what i mean is, how to get this bug assigned to me? > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133681#comment-13133681 ] Jonathan Ellis commented on CASSANDRA-556: -- This is the only ticketing system we use. Maybe I'm not understanding the question. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133676#comment-13133676 ] Victor Z. Peng commented on CASSANDRA-556: -- Hi, Jonathan. I want to work on this bug, but I couldn't find where to file a ticket. Could you give me some guideline? Thank you. :) > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131689#comment-13131689 ] Jonathan Ellis commented on CASSANDRA-556: -- right > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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-556) nodeprobe snapshot to support specific column families
[ https://issues.apache.org/jira/browse/CASSANDRA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131645#comment-13131645 ] Victor Z. Peng commented on CASSANDRA-556: -- Just to get clarified, does this mean dumping specific column families for specific tables? So the 'snapshot' command will take both table names and column familie names. > nodeprobe snapshot to support specific column families > -- > > Key: CASSANDRA-556 > URL: https://issues.apache.org/jira/browse/CASSANDRA-556 > Project: Cassandra > Issue Type: Improvement > Components: Core >Reporter: Chris Were >Priority: Minor > Labels: lhf > > It would be good to support dumping specific column families via nodeprobe > for backup purposes. > In my particular case the majority of cassandra data doesn't need to be > backed up except for a couple of column families containing user settings / > profiles etc. -- 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
