Maybe related to https://issues.apache.org/jira/browse/CASSANDRA-1992 ?
On Jan 27, 2011, at Thu Jan 27, 1:22 AM, B. Todd Burruss wrote:
i ran out of file handles on the repairing node after doing nodetool repair
- strange as i have never had this issue until using 0.7.0 (but i should say
. Otherwise, we recommend
sticking with the stable branch until a beta is released.
On Fri, Jun 11, 2010 at 2:24 PM, Matthew Conway m...@backupify.com wrote:
Hi All,
I'd like to start using trunk for something real, but am concerned about
stability of the data format. That is, will I
13, 2010 at 1:37 PM, Matthew Conway m...@backupify.com wrote:
Not so much worried about temporary breakages, but more about design
decisions that are made to enhance cassandra at the cost of a data format
change. So long as the policy here is to preserve backwards compatibility
On Jun 13, 2010, at Sun Jun 13, 9:34 PM, Benjamin Black wrote:
On Sun, Jun 13, 2010 at 5:58 PM, Matthew Conway m...@backupify.com wrote:
The ability to dynamically add new column families. Our app is currently
under heavy development, and we will be adding new column families at least
On Jun 14, 2010, at Mon Jun 14, 10:45 AM, Jonathan Ellis wrote:
I already have automation, whats missing are the details of the exact steps
I need to automate to accomplish the schema modification on a live cluster.
Even the FAQ just points to the feature in 0.7 trunk.
Huh?
Done, https://issues.apache.org/jira/browse/CASSANDRA-1188
It was find_all_by_service_id that was the culprit, and it resolves down to a
multiget_slice on a super column family. The super CF is acting as an index
back into a regular CF, thus I'm providing key, supercolumn name, and getting
