[jira] Issue Comment Edited: (CASSANDRA-1016) Coprocessors

[ https://issues.apache.org/jira/browse/CASSANDRA-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860656#action_12860656 ] Jeff Hodges edited comment on CASSANDRA-1016 at 4/25/10 1:49 AM:

[jira] Issue Comment Edited: (CASSANDRA-1016) Coprocessors

[ https://issues.apache.org/jira/browse/CASSANDRA-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860656#action_12860656 ] Jeff Hodges edited comment on CASSANDRA-1016 at 4/25/10 1:38 AM:

[jira] Updated: (CASSANDRA-1016) Coprocessors

[ https://issues.apache.org/jira/browse/CASSANDRA-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Hodges updated CASSANDRA-1016: --- Attachment: CASSANDRA-1016.patch Named them Callbacks. WriteCallbacks, specifically. Thi

[jira] Assigned: (CASSANDRA-1019) "java.net.ConnectException: Connection timed out" in MESSAGE-STREAMING-POOL:1

[ https://issues.apache.org/jira/browse/CASSANDRA-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reassigned CASSANDRA-1019: - Assignee: Stu Hood Stu, could you add some "retry N (3? 10?) times before ab

[jira] Resolved: (CASSANDRA-1021) no way to define a schema on boot

[ https://issues.apache.org/jira/browse/CASSANDRA-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-1021. --- Assignee: (was: Gary Dusbabek) Resolution: Invalid > no way to define a

[jira] Commented: (CASSANDRA-1021) no way to define a schema on boot

[ https://issues.apache.org/jira/browse/CASSANDRA-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860617#action_12860617 ] Jeff Hodges commented on CASSANDRA-1021: Nah, I screwed up and didn't double ch

[jira] Commented: (CASSANDRA-1021) no way to define a schema on boot

[ https://issues.apache.org/jira/browse/CASSANDRA-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860616#action_12860616 ] Gary Dusbabek commented on CASSANDRA-1021: -- Jeff, I take it auto bootstrap is

[jira] Assigned: (CASSANDRA-1021) no way to define a schema on boot

[ https://issues.apache.org/jira/browse/CASSANDRA-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reassigned CASSANDRA-1021: - Assignee: Gary Dusbabek It's supposed to pull the schema from an existing nod

[jira] Created: (CASSANDRA-1021) no way to define a schema on boot

no way to define a schema on boot - Key: CASSANDRA-1021 URL: https://issues.apache.org/jira/browse/CASSANDRA-1021 Project: Cassandra Issue Type: Bug Reporter: Jeff Hodges As of the latest in trun

[jira] Reopened: (CASSANDRA-946) Add a configuration and implementation to populate the data into memory

[ https://issues.apache.org/jira/browse/CASSANDRA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reopened CASSANDRA-946: -- > Add a configuration and implementation to populate the data into memory >

[jira] Commented: (CASSANDRA-946) Add a configuration and implementation to populate the data into memory

[ https://issues.apache.org/jira/browse/CASSANDRA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860569#action_12860569 ] Todd Blose commented on CASSANDRA-946: -- Just a small point.. wouldn't we want to us

[jira] Commented: (CASSANDRA-1018) Ability to close tables for embeddable cassandra

[ https://issues.apache.org/jira/browse/CASSANDRA-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860558#action_12860558 ] Gary Dusbabek commented on CASSANDRA-1018: -- Depending on the nature of the tes

[jira] Updated: (CASSANDRA-1020) keys are now byte[] but hashmap cannot have byte[] as keys so they need to be fixed

[ https://issues.apache.org/jira/browse/CASSANDRA-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-1020: -- Fix Version/s: (was: 0.8) Affects Version/s: (was: 0.8) > keys are

[jira] Reopened: (CASSANDRA-1020) keys are now byte[] but hashmap cannot have byte[] as keys so they need to be fixed

[ https://issues.apache.org/jira/browse/CASSANDRA-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reopened CASSANDRA-1020: --- you're right, that one is still a potential bug. > keys are now byte[] but hashmap c

[jira] Updated: (CASSANDRA-1020) keys are now byte[] but hashmap cannot have byte[] as keys so they need to be fixed

[ https://issues.apache.org/jira/browse/CASSANDRA-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-1020: -- Priority: Critical (was: Major) > keys are now byte[] but hashmap cannot have byte

[jira] Updated: (CASSANDRA-1014) GC storming, possible memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-1014: Attachment: 1014-2Gheap.png I thought perhaps the heap just needed more breathi

[jira] Commented: (CASSANDRA-1020) keys are now byte[] but hashmap cannot have byte[] as keys so they need to be fixed

[ https://issues.apache.org/jira/browse/CASSANDRA-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860537#action_12860537 ] Vijay commented on CASSANDRA-1020: -- Thanks Jonathan, but cfamilies.get(command.key) wi

[jira] Resolved: (CASSANDRA-1020) keys are now byte[] but hashmap cannot have byte[] as keys so they need to be fixed

[ https://issues.apache.org/jira/browse/CASSANDRA-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-1020. --- Resolution: Invalid as discussed on IRC, it looks like the only places we use byt