[jira] [Updated] (CASSANDRA-2492) add an escapeSQLString function and fix unescapeSQLString
[
https://issues.apache.org/jira/browse/CASSANDRA-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Morton updated CASSANDRA-2492:
Attachment: 0001-use-StringEscapeUtils-to-escape-and-unescape.patch
Attached patch to use StringEscapeUtils to escape and unescape cli strings,
includes unit test.
add an escapeSQLString function and fix unescapeSQLString
-
Key: CASSANDRA-2492
URL: https://issues.apache.org/jira/browse/CASSANDRA-2492
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.7.4
Reporter: Aaron Morton
Assignee: Aaron Morton
Priority: Trivial
Attachments: 0001-use-StringEscapeUtils-to-escape-and-unescape.patch
CliUtils.unescapeSqlString repeats the escape character e.g.
{noformat}my \\t tab becomes my \tt{noformat}
because {{i}} is not bumped when an escape is processed.
Also for Cassandra-2221 I need a function to escape strings back so they will
work if processed by the cli again.
There are a number of non [standard
escapes|http://java.sun.com/docs/books/jls/second_edition/html/lexical.doc.html#101089]
which I assume is a hang over from is original source
https://github.com/apache/cassandra/blob/1aeca2b6257b0ad6680080b1756edf7ee9acf8c8/src/java/org/apache/cassandra/cli/CliUtils.java
Will change to use the
[StringEscapeUtils|http://commons.apache.org/lang/api-2.5/org/apache/commons/lang/StringEscapeUtils.html]
class
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1094945 - /cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/service/AntiEntropyServiceTest.java
Author: slebresne Date: Tue Apr 19 08:59:31 2011 New Revision: 1094945 URL: http://svn.apache.org/viewvc?rev=1094945view=rev Log: Fix unit test for CASSANDRA-2290 Modified: cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/service/AntiEntropyServiceTest.java Modified: cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/service/AntiEntropyServiceTest.java URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/service/AntiEntropyServiceTest.java?rev=1094945r1=1094944r2=1094945view=diff == --- cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/service/AntiEntropyServiceTest.java (original) +++ cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/service/AntiEntropyServiceTest.java Tue Apr 19 08:59:31 2011 @@ -39,6 +39,7 @@ import org.apache.cassandra.db.filter.Qu import org.apache.cassandra.dht.IPartitioner; import org.apache.cassandra.dht.Range; import org.apache.cassandra.dht.Token; +import org.apache.cassandra.gms.Gossiper; import org.apache.cassandra.io.PrecompactedRow; import org.apache.cassandra.io.util.DataOutputBuffer; import org.apache.cassandra.locator.AbstractReplicationStrategy; @@ -83,7 +84,9 @@ public class AntiEntropyServiceTest exte StorageService.instance.setToken(StorageService.getPartitioner().getRandomToken()); tmd.updateNormalToken(StorageService.getPartitioner().getMinimumToken(), REMOTE); assert tmd.isMember(REMOTE); - + +Gossiper.instance.initializeNodeUnsafe(REMOTE, 1); + // random session id for each test request = new TreeRequest(UUID.randomUUID().toString(), LOCAL, new CFPair(tablename, cfname)); }
svn commit: r1094960 - in /cassandra/trunk: ./ contrib/ interface/thrift/gen-java/org/apache/cassandra/thrift/ test/unit/org/apache/cassandra/service/
Author: slebresne Date: Tue Apr 19 09:22:30 2011 New Revision: 1094960 URL: http://svn.apache.org/viewvc?rev=1094960view=rev Log: Merge from 0.8 Modified: cassandra/trunk/ (props changed) cassandra/trunk/contrib/ (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/InvalidRequestException.java (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/NotFoundException.java (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/SuperColumn.java (props changed) cassandra/trunk/test/unit/org/apache/cassandra/service/AntiEntropyServiceTestAbstract.java Propchange: cassandra/trunk/ -- --- svn:mergeinfo (original) +++ svn:mergeinfo Tue Apr 19 09:22:30 2011 @@ -1,7 +1,7 @@ /cassandra/branches/cassandra-0.6:922689-1052356,1052358-1053452,1053454,1053456-1081914,1083000 /cassandra/branches/cassandra-0.7:1026516-1091087,1091503,1091542,1091654,1094796 /cassandra/branches/cassandra-0.7.0:1053690-1055654 -/cassandra/branches/cassandra-0.8:1090935-1094085,1094481,1094797 +/cassandra/branches/cassandra-0.8:1090935-1094085,1094481,1094797,1094959 /cassandra/tags/cassandra-0.7.0-rc3:1051699-1053689 /incubator/cassandra/branches/cassandra-0.3:774578-796573 /incubator/cassandra/branches/cassandra-0.4:810145-834239,834349-834350 Propchange: cassandra/trunk/contrib/ -- --- svn:mergeinfo (original) +++ svn:mergeinfo Tue Apr 19 09:22:30 2011 @@ -1,7 +1,7 @@ /cassandra/branches/cassandra-0.6/contrib:922689-1052356,1052358-1053452,1053454,1053456-1068009 /cassandra/branches/cassandra-0.7/contrib:1026516-1091087,1091503,1091542,1091654,1094481,1094796 /cassandra/branches/cassandra-0.7.0/contrib:1053690-1055654 -/cassandra/branches/cassandra-0.8/contrib:1090935-1094085,1094481,1094797 +/cassandra/branches/cassandra-0.8/contrib:1090935-1094085,1094481,1094797,1094959 /cassandra/tags/cassandra-0.7.0-rc3/contrib:1051699-1053689 /incubator/cassandra/branches/cassandra-0.3/contrib:774578-796573 /incubator/cassandra/branches/cassandra-0.4/contrib:810145-810987,810994-834239,834349-834350 Propchange: cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java -- --- svn:mergeinfo (original) +++ svn:mergeinfo Tue Apr 19 09:22:30 2011 @@ -1,7 +1,7 @@ /cassandra/branches/cassandra-0.6/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:922689-1052356,1052358-1053452,1053454,1053456-1081914,1083000 /cassandra/branches/cassandra-0.7/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1026516-1091087,1091503,1091542,1091654,1094481,1094796 /cassandra/branches/cassandra-0.7.0/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1053690-1055654 -/cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1090935-1094085,1094481,1094797 +/cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1090935-1094085,1094481,1094797,1094959 /cassandra/tags/cassandra-0.7.0-rc3/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1051699-1053689 /incubator/cassandra/branches/cassandra-0.3/interface/gen-java/org/apache/cassandra/service/Cassandra.java:774578-796573 /incubator/cassandra/branches/cassandra-0.4/interface/gen-java/org/apache/cassandra/service/Cassandra.java:810145-834239,834349-834350 Propchange: cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java -- --- svn:mergeinfo (original) +++ svn:mergeinfo Tue Apr 19 09:22:30 2011 @@ -1,7 +1,7 @@ /cassandra/branches/cassandra-0.6/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java:922689-1052356,1052358-1053452,1053454,1053456-1081914,1083000 /cassandra/branches/cassandra-0.7/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java:1026516-1091087,1091503,1091542,1091654,1094481,1094796 /cassandra/branches/cassandra-0.7.0/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java:1053690-1055654 -/cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java:1090935-1094085,1094481,1094797 +/cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java:1090935-1094085,1094481,1094797,1094959 /cassandra/tags/cassandra-0.7.0-rc3/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java:1051699-1053689
buildbot success in ASF Buildbot on cassandra-trunk
The Buildbot has detected a restored build on builder cassandra-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/cassandra-trunk/builds/1273 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: scheduler Build Source Stamp: [branch cassandra/trunk] 1094960 Blamelist: slebresne Build succeeded! sincerely, -The Buildbot
[jira] [Commented] (CASSANDRA-1740) Nodetool commands to query and stop compaction, repair, cleanup and scrub
[ https://issues.apache.org/jira/browse/CASSANDRA-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021521#comment-13021521 ] Pavel Yaskevich commented on CASSANDRA-1740: sgtm Nodetool commands to query and stop compaction, repair, cleanup and scrub - Key: CASSANDRA-1740 URL: https://issues.apache.org/jira/browse/CASSANDRA-1740 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Chip Salzenberg Assignee: Pavel Yaskevich Priority: Minor Fix For: 0.7.6 Attachments: CASSANDRA-1740.patch Original Estimate: 24h Remaining Estimate: 24h The only way to stop compaction, repair, cleanup, or scrub in progress is to stop and restart the entire Cassandra server. Please provide nodetool commands to query whether such things are running, and stop them if they are. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2290) Repair hangs if one of the neighbor is dead
[ https://issues.apache.org/jira/browse/CASSANDRA-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021527#comment-13021527 ] Hudson commented on CASSANDRA-2290: --- Integrated in Cassandra #856 (See [https://hudson.apache.org/hudson/job/Cassandra/856/]) Repair hangs if one of the neighbor is dead --- Key: CASSANDRA-2290 URL: https://issues.apache.org/jira/browse/CASSANDRA-2290 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.6 Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Minor Fix For: 0.7.5, 0.8 Attachments: 0001-Don-t-start-repair-if-a-neighbor-is-dead.patch Original Estimate: 1h Remaining Estimate: 1h Repair don't cope well with dead/dying neighbors. There is 2 problems: # Repair don't check if a node is dead before sending a TreeRequest; this is easily fixable. # If a neighbor dies mid-repair, the repair will also hang forever. The second point is not easy to deal with. The best approach is probably CASSANDRA-1740 however. That is, if we add a way to query the state of a repair, and that this query correctly check all neighbors and also add a way to cancel a repair, this would probably be enough. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2290) Repair hangs if one of the neighbor is dead
[ https://issues.apache.org/jira/browse/CASSANDRA-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021529#comment-13021529 ] Hudson commented on CASSANDRA-2290: --- Integrated in Cassandra-0.8 #19 (See [https://hudson.apache.org/hudson/job/Cassandra-0.8/19/]) Fix unit tests for CASSANDRA-2290 Repair hangs if one of the neighbor is dead --- Key: CASSANDRA-2290 URL: https://issues.apache.org/jira/browse/CASSANDRA-2290 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.6 Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Minor Fix For: 0.7.5, 0.8 Attachments: 0001-Don-t-start-repair-if-a-neighbor-is-dead.patch Original Estimate: 1h Remaining Estimate: 1h Repair don't cope well with dead/dying neighbors. There is 2 problems: # Repair don't check if a node is dead before sending a TreeRequest; this is easily fixable. # If a neighbor dies mid-repair, the repair will also hang forever. The second point is not easy to deal with. The best approach is probably CASSANDRA-1740 however. That is, if we add a way to query the state of a repair, and that this query correctly check all neighbors and also add a way to cancel a repair, this would probably be enough. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095070 - in /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra: db/ db/context/ io/sstable/
Author: slebresne
Date: Tue Apr 19 12:51:56 2011
New Revision: 1095070
URL: http://svn.apache.org/viewvc?rev=1095070view=rev
Log:
Make scrub validate column fields
patch by slebresne; reviewed by jbellis for CASSANDRA-2460
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/Column.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/ColumnFamily.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CounterColumn.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/DeletedColumn.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/ExpiringColumn.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/IColumn.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/SuperColumn.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/context/CounterContext.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/io/sstable/SSTableIdentityIterator.java
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/Column.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/Column.java?rev=1095070r1=1095069r2=1095070view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/Column.java
(original)
+++
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/Column.java
Tue Apr 19 12:51:56 2011
@@ -26,7 +26,9 @@ import java.util.Collection;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
+import org.apache.cassandra.config.CFMetaData;
import org.apache.cassandra.db.marshal.AbstractType;
+import org.apache.cassandra.db.marshal.MarshalException;
import org.apache.cassandra.io.util.DataOutputBuffer;
import org.apache.cassandra.utils.ByteBufferUtil;
@@ -237,5 +239,19 @@ public class Column implements IColumn
{
return !isMarkedForDelete();
}
+
+protected void validateName(CFMetaData metadata) throws MarshalException
+{
+AbstractType nameValidator = metadata.cfType == ColumnFamilyType.Super
? metadata.subcolumnComparator : metadata.comparator;
+nameValidator.validate(name());
+}
+
+public void validateFields(CFMetaData metadata) throws MarshalException
+{
+validateName(metadata);
+AbstractType valueValidator = metadata.getValueValidator(name());
+if (valueValidator != null)
+valueValidator.validate(value());
+}
}
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/ColumnFamily.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/ColumnFamily.java?rev=1095070r1=1095069r2=1095070view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/ColumnFamily.java
(original)
+++
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/ColumnFamily.java
Tue Apr 19 12:51:56 2011
@@ -38,6 +38,7 @@ import org.apache.cassandra.config.Datab
import org.apache.cassandra.db.filter.QueryPath;
import org.apache.cassandra.db.marshal.AbstractCommutativeType;
import org.apache.cassandra.db.marshal.AbstractType;
+import org.apache.cassandra.db.marshal.MarshalException;
import org.apache.cassandra.io.IColumnSerializer;
import org.apache.cassandra.io.util.IIterableColumns;
import org.apache.cassandra.utils.FBUtilities;
@@ -432,4 +433,18 @@ public class ColumnFamily implements ICo
size += column.serializedSize();
return size;
}
+
+/**
+ * Goes over all columns and check the fields are valid (as far as we can
+ * tell).
+ * This is used to detect corruption after deserialization.
+ */
+public void validateColumnFields() throws MarshalException
+{
+CFMetaData metadata = metadata();
+for (IColumn column : getSortedColumns())
+{
+column.validateFields(metadata);
+}
+}
}
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CounterColumn.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CounterColumn.java?rev=1095070r1=1095069r2=1095070view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CounterColumn.java
(original)
+++
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CounterColumn.java
Tue Apr 19 12:51:56 2011
@@ -27,9 +27,11 @@ import java.util.Map;
import org.apache.log4j.Logger;
+import org.apache.cassandra.config.CFMetaData;
import org.apache.cassandra.db.context.CounterContext;
import org.apache.cassandra.db.context.IContext.ContextRelationship;
import
svn commit: r1095071 - in /cassandra/trunk: ./ contrib/ interface/thrift/gen-java/org/apache/cassandra/thrift/ src/java/org/apache/cassandra/db/ src/java/org/apache/cassandra/db/context/ src/java/org/
Author: slebresne Date: Tue Apr 19 12:54:08 2011 New Revision: 1095071 URL: http://svn.apache.org/viewvc?rev=1095071view=rev Log: merger CASSANDRA-2460 from 0.8 Modified: cassandra/trunk/ (props changed) cassandra/trunk/contrib/ (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/InvalidRequestException.java (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/NotFoundException.java (props changed) cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/SuperColumn.java (props changed) cassandra/trunk/src/java/org/apache/cassandra/db/Column.java cassandra/trunk/src/java/org/apache/cassandra/db/ColumnFamily.java cassandra/trunk/src/java/org/apache/cassandra/db/CounterColumn.java cassandra/trunk/src/java/org/apache/cassandra/db/DeletedColumn.java cassandra/trunk/src/java/org/apache/cassandra/db/ExpiringColumn.java cassandra/trunk/src/java/org/apache/cassandra/db/IColumn.java cassandra/trunk/src/java/org/apache/cassandra/db/SuperColumn.java cassandra/trunk/src/java/org/apache/cassandra/db/context/CounterContext.java cassandra/trunk/src/java/org/apache/cassandra/io/sstable/SSTableIdentityIterator.java Propchange: cassandra/trunk/ -- --- svn:mergeinfo (original) +++ svn:mergeinfo Tue Apr 19 12:54:08 2011 @@ -1,7 +1,7 @@ /cassandra/branches/cassandra-0.6:922689-1052356,1052358-1053452,1053454,1053456-1081914,1083000 /cassandra/branches/cassandra-0.7:1026516-1091087,1091503,1091542,1091654,1094796 /cassandra/branches/cassandra-0.7.0:1053690-1055654 -/cassandra/branches/cassandra-0.8:1090935-1094085,1094481,1094797,1094959 +/cassandra/branches/cassandra-0.8:1090935-1094085,1094481,1094797,1094959,1095070 /cassandra/tags/cassandra-0.7.0-rc3:1051699-1053689 /incubator/cassandra/branches/cassandra-0.3:774578-796573 /incubator/cassandra/branches/cassandra-0.4:810145-834239,834349-834350 Propchange: cassandra/trunk/contrib/ -- --- svn:mergeinfo (original) +++ svn:mergeinfo Tue Apr 19 12:54:08 2011 @@ -1,7 +1,7 @@ /cassandra/branches/cassandra-0.6/contrib:922689-1052356,1052358-1053452,1053454,1053456-1068009 /cassandra/branches/cassandra-0.7/contrib:1026516-1091087,1091503,1091542,1091654,1094481,1094796 /cassandra/branches/cassandra-0.7.0/contrib:1053690-1055654 -/cassandra/branches/cassandra-0.8/contrib:1090935-1094085,1094481,1094797,1094959 +/cassandra/branches/cassandra-0.8/contrib:1090935-1094085,1094481,1094797,1094959,1095070 /cassandra/tags/cassandra-0.7.0-rc3/contrib:1051699-1053689 /incubator/cassandra/branches/cassandra-0.3/contrib:774578-796573 /incubator/cassandra/branches/cassandra-0.4/contrib:810145-810987,810994-834239,834349-834350 Propchange: cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java -- --- svn:mergeinfo (original) +++ svn:mergeinfo Tue Apr 19 12:54:08 2011 @@ -1,7 +1,7 @@ /cassandra/branches/cassandra-0.6/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:922689-1052356,1052358-1053452,1053454,1053456-1081914,1083000 /cassandra/branches/cassandra-0.7/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1026516-1091087,1091503,1091542,1091654,1094481,1094796 /cassandra/branches/cassandra-0.7.0/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1053690-1055654 -/cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1090935-1094085,1094481,1094797,1094959 +/cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1090935-1094085,1094481,1094797,1094959,1095070 /cassandra/tags/cassandra-0.7.0-rc3/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java:1051699-1053689 /incubator/cassandra/branches/cassandra-0.3/interface/gen-java/org/apache/cassandra/service/Cassandra.java:774578-796573 /incubator/cassandra/branches/cassandra-0.4/interface/gen-java/org/apache/cassandra/service/Cassandra.java:810145-834239,834349-834350 Propchange: cassandra/trunk/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java -- --- svn:mergeinfo (original) +++ svn:mergeinfo Tue Apr 19 12:54:08 2011 @@ -1,7 +1,7 @@ /cassandra/branches/cassandra-0.6/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java:922689-1052356,1052358-1053452,1053454,1053456-1081914,1083000
[jira] [Resolved] (CASSANDRA-2290) Repair hangs if one of the neighbor is dead
[ https://issues.apache.org/jira/browse/CASSANDRA-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne resolved CASSANDRA-2290. - Resolution: Fixed Repair hangs if one of the neighbor is dead --- Key: CASSANDRA-2290 URL: https://issues.apache.org/jira/browse/CASSANDRA-2290 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.6 Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Minor Fix For: 0.7.5, 0.8 Attachments: 0001-Don-t-start-repair-if-a-neighbor-is-dead.patch Original Estimate: 1h Remaining Estimate: 1h Repair don't cope well with dead/dying neighbors. There is 2 problems: # Repair don't check if a node is dead before sending a TreeRequest; this is easily fixable. # If a neighbor dies mid-repair, the repair will also hang forever. The second point is not easy to deal with. The best approach is probably CASSANDRA-1740 however. That is, if we add a way to query the state of a repair, and that this query correctly check all neighbors and also add a way to cancel a repair, this would probably be enough. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2460) Make scrub validate deserialized columns
[ https://issues.apache.org/jira/browse/CASSANDRA-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021575#comment-13021575 ] Hudson commented on CASSANDRA-2460: --- Integrated in Cassandra #857 (See [https://hudson.apache.org/hudson/job/Cassandra/857/]) merger CASSANDRA-2460 from 0.8 Make scrub validate deserialized columns Key: CASSANDRA-2460 URL: https://issues.apache.org/jira/browse/CASSANDRA-2460 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Fix For: 0.7.5 Attachments: 0001-Make-scrub-check-column-fields-v2.patch, 0001-Make-scrub-check-column-fields.patch Original Estimate: 4h Remaining Estimate: 4h Right now, scrub deserialize the columns but don't validate the fields, and such there is a number of errors it could fix (or at least corrupted rows it could skip) but don't. This ticket proposes to handle those errors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095082 - /cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py
Author: jbellis Date: Tue Apr 19 13:32:54 2011 New Revision: 1095082 URL: http://svn.apache.org/viewvc?rev=1095082view=rev Log: add SchemaDisagreementException import patch by jbellis; tested by Cathy Daw for CASSANDRA-2501 Modified: cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py Modified: cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py?rev=1095082r1=1095081r2=1095082view=diff == --- cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py (original) +++ cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py Tue Apr 19 13:32:54 2011 @@ -22,8 +22,12 @@ import cql from cql.marshal import prepare from cql.decoders import SchemaDecoder from cql.results import ResultSet -from cql.cassandra.ttypes import (Compression, CqlResultType, InvalidRequestException, - TApplicationException) +from cql.cassandra.ttypes import ( +Compression, +CqlResultType, +InvalidRequestException, +TApplicationException, +SchemaDisagreementException) class Cursor:
[jira] [Resolved] (CASSANDRA-2501) Error running cqlsh from .tar file -- global name 'SchemaDisagreementException' is not defined
[
https://issues.apache.org/jira/browse/CASSANDRA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-2501.
---
Resolution: Fixed
Fix Version/s: 0.8
Reviewer: cdaw
Will mark Fixed since the missing SchemaDisagreementException import was a real
bug.
Error running cqlsh from .tar file -- global name
'SchemaDisagreementException' is not defined
--
Key: CASSANDRA-2501
URL: https://issues.apache.org/jira/browse/CASSANDRA-2501
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.8
Environment: Running on 3-node Centos 5.5. The cql package was
installed with Python 2.6 and prior to installation, I downloaded and
installed thrift05-0.5.0.
Reporter: Cathy Daw
Assignee: Jonathan Ellis
Fix For: 0.8
Attachments: 2501.txt
*Error when running cqlsh*
{code}
[cassandra@cdaw-qa1 cql-1.0.0]$ cqlsh cdaw-qa1
Traceback (most recent call last):
File /usr/bin/cqlsh, line 212, in module
password=options.password)
File /usr/bin/cqlsh, line 55, in __init__
self.conn = cql.connect(hostname, port, user=username, password=password)
File /usr/lib/python2.6/site-packages/cql/__init__.py, line 51, in connect
return connection.Connection(host, port, keyspace, user, password)
File /usr/lib/python2.6/site-packages/cql/connection.py, line 53, in
__init__
c.execute('USE %s;' % keyspace)
File /usr/lib/python2.6/site-packages/cql/cursor.py, line 126, in execute
except SchemaDisagreementException, sde:
NameError: global name 'SchemaDisagreementException' is not defined
{code}
*Build*
* Install the cassandra binary from the nightly build
wget
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/apache-cassandra-2011-04-18_11-02-29-bin.tar.gz
* Install cql from .tar file on nightly build
wget
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/cql-1.0.0.tar.gz
*CQL Install Output*
{code}
[cassandra@cdaw-qa1 cql-1.0.0]$ sudo python2.6 ./setup.py install
[sudo] password for cassandra:
running install
running build
running build_py
running build_scripts
creating build/scripts-2.6
copying and adjusting cqlsh - build/scripts-2.6
changing mode of build/scripts-2.6/cqlsh from 644 to 755
running install_lib
creating /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/results.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/marshal.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/connection.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/cursor.py - /usr/lib/python2.6/site-packages/cql
creating /usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/__init__.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/Cassandra.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/constants.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/ttypes.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/decoders.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/__init__.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/errors.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/connection_pool.py -
/usr/lib/python2.6/site-packages/cql
byte-compiling /usr/lib/python2.6/site-packages/cql/results.py to results.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/marshal.py to marshal.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/connection.py to
connection.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cursor.py to cursor.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/__init__.py to
__init__.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/Cassandra.py to
Cassandra.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/constants.py to
constants.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/ttypes.py to
ttypes.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/decoders.py to
decoders.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/__init__.py to
__init__.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/errors.py to errors.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/connection_pool.py to
connection_pool.pyc
running install_scripts
copying build/scripts-2.6/cqlsh - /usr/bin
changing mode of /usr/bin/cqlsh to 755
running install_egg_info
Writing /usr/lib/python2.6/site-packages/cql-1.0.0-py2.6.egg-info
{code}
--
This message is automatically generated by JIRA.
For more information on
[jira] [Commented] (CASSANDRA-2501) Error running cqlsh from .tar file -- global name 'SchemaDisagreementException' is not defined
[
https://issues.apache.org/jira/browse/CASSANDRA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021582#comment-13021582
]
Jonathan Ellis commented on CASSANDRA-2501:
---
(committed in r1095082)
Error running cqlsh from .tar file -- global name
'SchemaDisagreementException' is not defined
--
Key: CASSANDRA-2501
URL: https://issues.apache.org/jira/browse/CASSANDRA-2501
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.8
Environment: Running on 3-node Centos 5.5. The cql package was
installed with Python 2.6 and prior to installation, I downloaded and
installed thrift05-0.5.0.
Reporter: Cathy Daw
Assignee: Jonathan Ellis
Fix For: 0.8
Attachments: 2501.txt
*Error when running cqlsh*
{code}
[cassandra@cdaw-qa1 cql-1.0.0]$ cqlsh cdaw-qa1
Traceback (most recent call last):
File /usr/bin/cqlsh, line 212, in module
password=options.password)
File /usr/bin/cqlsh, line 55, in __init__
self.conn = cql.connect(hostname, port, user=username, password=password)
File /usr/lib/python2.6/site-packages/cql/__init__.py, line 51, in connect
return connection.Connection(host, port, keyspace, user, password)
File /usr/lib/python2.6/site-packages/cql/connection.py, line 53, in
__init__
c.execute('USE %s;' % keyspace)
File /usr/lib/python2.6/site-packages/cql/cursor.py, line 126, in execute
except SchemaDisagreementException, sde:
NameError: global name 'SchemaDisagreementException' is not defined
{code}
*Build*
* Install the cassandra binary from the nightly build
wget
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/apache-cassandra-2011-04-18_11-02-29-bin.tar.gz
* Install cql from .tar file on nightly build
wget
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/cql-1.0.0.tar.gz
*CQL Install Output*
{code}
[cassandra@cdaw-qa1 cql-1.0.0]$ sudo python2.6 ./setup.py install
[sudo] password for cassandra:
running install
running build
running build_py
running build_scripts
creating build/scripts-2.6
copying and adjusting cqlsh - build/scripts-2.6
changing mode of build/scripts-2.6/cqlsh from 644 to 755
running install_lib
creating /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/results.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/marshal.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/connection.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/cursor.py - /usr/lib/python2.6/site-packages/cql
creating /usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/__init__.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/Cassandra.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/constants.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/ttypes.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/decoders.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/__init__.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/errors.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/connection_pool.py -
/usr/lib/python2.6/site-packages/cql
byte-compiling /usr/lib/python2.6/site-packages/cql/results.py to results.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/marshal.py to marshal.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/connection.py to
connection.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cursor.py to cursor.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/__init__.py to
__init__.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/Cassandra.py to
Cassandra.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/constants.py to
constants.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/ttypes.py to
ttypes.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/decoders.py to
decoders.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/__init__.py to
__init__.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/errors.py to errors.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/connection_pool.py to
connection_pool.pyc
running install_scripts
copying build/scripts-2.6/cqlsh - /usr/bin
changing mode of /usr/bin/cqlsh to 755
running install_egg_info
Writing /usr/lib/python2.6/site-packages/cql-1.0.0-py2.6.egg-info
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2401) getColumnFamily() return null, which is not checked in ColumnFamilyStore.java scan() method, causing Timeout Exception in query
[ https://issues.apache.org/jira/browse/CASSANDRA-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021583#comment-13021583 ] Roland Gude commented on CASSANDRA-2401: i just looked a little closer at your index expressions again. If i understand them correctly they are subject to https://issues.apache.org/jira/browse/CASSANDRA-2347 Although i don't really think it is the issue you are describing it would be nice if you could apply the patch and see if the error still occurs. You are creating the bytebuffers for author_id and file_type in a different way. Is this a mistake? getColumnFamily() return null, which is not checked in ColumnFamilyStore.java scan() method, causing Timeout Exception in query --- Key: CASSANDRA-2401 URL: https://issues.apache.org/jira/browse/CASSANDRA-2401 Project: Cassandra Issue Type: Bug Affects Versions: 0.7.4 Environment: Hector 0.7.0-28, Cassandra 0.7.4, Windows 7, Eclipse Reporter: Tey Kar Shiang ColumnFamilyStore.java, line near 1680, ColumnFamily data = getColumnFamily(new QueryFilter(dk, path, firstFilter)), the data is returned null, causing NULL exception in satisfies(data, clause, primary) which is not captured. The callback got timeout and return a Timeout exception to Hector. The data is empty, as I traced, I have the the columns Count as 0 in removeDeletedCF(), which return the null there. (I am new and trying to understand the logics around still). Instead of crash to NULL, could we bypass the data? About my test: A stress-test program to add, modify and delete data to keyspace. I have 30 threads simulate concurrent users to perform the actions above, and do a query to all rows periodically. I have Column Family with rows (as File) and columns as index (e.g. userID, fileType). No issue on the first day of test, and stopped for 3 days. I restart the test on 4th day, 1 of the users failed to query the files (timeout exception received). Most of the users are still okay with the query. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095084 - in /cassandra/branches/cassandra-0.7: CHANGES.txt src/java/org/apache/cassandra/cli/CliUtils.java test/unit/org/apache/cassandra/cli/CliTest.java
Author: jbellis
Date: Tue Apr 19 13:42:19 2011
New Revision: 1095084
URL: http://svn.apache.org/viewvc?rev=1095084view=rev
Log:
fix backslash substitutions in CLI
patch by Aaron Morton; reviewed by jbellis for CASSANDRA-2492
Modified:
cassandra/branches/cassandra-0.7/CHANGES.txt
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/cli/CliUtils.java
cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/cli/CliTest.java
Modified: cassandra/branches/cassandra-0.7/CHANGES.txt
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/CHANGES.txt?rev=1095084r1=1095083r2=1095084view=diff
==
--- cassandra/branches/cassandra-0.7/CHANGES.txt (original)
+++ cassandra/branches/cassandra-0.7/CHANGES.txt Tue Apr 19 13:42:19 2011
@@ -31,6 +31,7 @@
* fix duplicate results from CFS.scan (CASSANDRA-2406)
* avoid caching token-only decoratedkeys (CASSANDRA-2416)
* preserve version when streaming data from old sstables (CASSANDRA-2283)
+ * fix backslash substitutions in CLI (CASSANDRA-2492)
0.7.4
Modified:
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/cli/CliUtils.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/cli/CliUtils.java?rev=1095084r1=1095083r2=1095084view=diff
==
---
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/cli/CliUtils.java
(original)
+++
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/cli/CliUtils.java
Tue Apr 19 13:42:19 2011
@@ -6,6 +6,7 @@ import java.util.Set;
import org.apache.cassandra.thrift.CfDef;
import org.apache.cassandra.thrift.IndexOperator;
import org.apache.cassandra.thrift.KsDef;
+import org.apache.commons.lang.StringEscapeUtils;
/*
*
* Licensed to the Apache Software Foundation (ASF) under one
@@ -38,70 +39,16 @@ public class CliUtils
*/
public static String unescapeSQLString(String b)
{
-int j = 1;
-final char start = b.charAt(0);
-final char end = b.charAt(b.length() - 1);
-
-if (start != '\'' end != '\'')
-{
-j = 0;
-}
-
-StringBuilder sb = new StringBuilder(b.length());
-
-for (int i = j; ((j == 0) ? i : i + 1) b.length(); i++)
-{
-if (b.charAt(i) == '\\' i + 2 b.length())
-{
-char n = b.charAt(i + 1);
-switch (n)
-{
-case '0':
-sb.append(\0);
-break;
-case '\'':
-sb.append(');
-break;
-case '':
-sb.append(\);
-break;
-case 'b':
-sb.append(\b);
-break;
-case 'n':
-sb.append(\n);
-break;
-case 'r':
-sb.append(\r);
-break;
-case 't':
-sb.append(\t);
-break;
-case 'Z':
-sb.append(\u001A);
-break;
-case '\\':
-sb.append(\\);
-break;
-case '%':
-sb.append(%);
-break;
-case '_':
-sb.append(_);
-break;
-default:
-sb.append(n);
-}
-}
-else
-{
-sb.append(b.charAt(i));
-}
-}
-
-return sb.toString();
+if (b.charAt(0) == '\'' b.charAt(b.length()-1) == '\'')
+b = b.substring(1, b.length()-1);
+return StringEscapeUtils.unescapeJava(b);
}
+public static String escapeSQLString(String b)
+{
+// single quotes are not escaped in java, need to be for cli
+return StringEscapeUtils.escapeJava(b).replace(\', \\');
+}
/**
* Returns IndexOperator from string representation
* @param operator - string representing IndexOperator (=, =, , , =)
Modified:
cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/cli/CliTest.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/cli/CliTest.java?rev=1095084r1=1095083r2=1095084view=diff
==
---
cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/cli/CliTest.java
(original)
+++
cassandra/branches/cassandra-0.7/test/unit/org/apache/cassandra/cli/CliTest.java
Tue Apr 19 13:42:19 2011
[jira] [Commented] (CASSANDRA-2355) Allow parameters for comparator
[ https://issues.apache.org/jira/browse/CASSANDRA-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021589#comment-13021589 ] Jonathan Ellis commented on CASSANDRA-2355: --- +1 Allow parameters for comparator --- Key: CASSANDRA-2355 URL: https://issues.apache.org/jira/browse/CASSANDRA-2355 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Minor Fix For: 1.0 Attachments: Allow-comparators-to-take-arguments-ReversedType.patch Original Estimate: 4h Remaining Estimate: 4h Being able to provide arguments to a comparator, to parametrize its behavior, can be useful. For example, a generic ReverseComparator is trivial to write, but without the ability to provide arguments at the comparator constriction, it cannot be used. CASSANDRA-2231 provides another use case for this. This ticket proposes to introduce a parser for comparator definition that supports optional parameters and to introduce a generic ReverseType as a simple example of this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2290) Repair hangs if one of the neighbor is dead
[ https://issues.apache.org/jira/browse/CASSANDRA-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021595#comment-13021595 ] Hudson commented on CASSANDRA-2290: --- Integrated in Cassandra-0.7 #447 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/447/]) Repair hangs if one of the neighbor is dead --- Key: CASSANDRA-2290 URL: https://issues.apache.org/jira/browse/CASSANDRA-2290 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.6 Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Minor Fix For: 0.7.5, 0.8 Attachments: 0001-Don-t-start-repair-if-a-neighbor-is-dead.patch Original Estimate: 1h Remaining Estimate: 1h Repair don't cope well with dead/dying neighbors. There is 2 problems: # Repair don't check if a node is dead before sending a TreeRequest; this is easily fixable. # If a neighbor dies mid-repair, the repair will also hang forever. The second point is not easy to deal with. The best approach is probably CASSANDRA-1740 however. That is, if we add a way to query the state of a repair, and that this query correctly check all neighbors and also add a way to cancel a repair, this would probably be enough. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2502) disable cache saving on system CFs
[ https://issues.apache.org/jira/browse/CASSANDRA-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021596#comment-13021596 ] Hudson commented on CASSANDRA-2502: --- Integrated in Cassandra-0.7 #447 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/447/]) disable cache saving on system CFs -- Key: CASSANDRA-2502 URL: https://issues.apache.org/jira/browse/CASSANDRA-2502 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 0.7.0 Reporter: Ryan King Assignee: Ryan King Priority: Minor Fix For: 0.7.5 Attachments: 0001-disable-cache-saving-on-system-tables.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2316) NoSuchElement exception on node which is streaming a repair
[
https://issues.apache.org/jira/browse/CASSANDRA-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021593#comment-13021593
]
Hudson commented on CASSANDRA-2316:
---
Integrated in Cassandra-0.7 #447 (See
[https://hudson.apache.org/hudson/job/Cassandra-0.7/447/])
NoSuchElement exception on node which is streaming a repair
---
Key: CASSANDRA-2316
URL: https://issues.apache.org/jira/browse/CASSANDRA-2316
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.6
Reporter: Jason Harvey
Assignee: Jonathan Ellis
Labels: repair
Fix For: 0.7.5
Attachments: 2316-assert.txt
Running latest SVN snapshot of 0.7.
When I ran a repair on a node, that node's neighbor threw the following
exception. Let me know what other info could be helpful.
{code}
INFO 23:43:44,358 Streaming to /10.251.166.15
ERROR 23:50:21,321 Fatal exception in thread
Thread[CompactionExecutor:1,1,main]
java.util.NoSuchElementException
at
com.google.common.collect.AbstractIterator.next(AbstractIterator.java:146)
at
org.apache.cassandra.service.AntiEntropyService$Validator.add(AntiEntropyService.java:366)
at
org.apache.cassandra.db.CompactionManager.doValidationCompaction(CompactionManager.java:825)
at
org.apache.cassandra.db.CompactionManager.access$800(CompactionManager.java:56)
at
org.apache.cassandra.db.CompactionManager$6.call(CompactionManager.java:358)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2429) Silence non-errors while reconnecting
[ https://issues.apache.org/jira/browse/CASSANDRA-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021594#comment-13021594 ] Hudson commented on CASSANDRA-2429: --- Integrated in Cassandra-0.7 #447 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/447/]) Silence non-errors while reconnecting - Key: CASSANDRA-2429 URL: https://issues.apache.org/jira/browse/CASSANDRA-2429 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 0.6 Reporter: Joaquin Casares Assignee: Jonathan Ellis Priority: Trivial Fix For: 0.7.5 Attachments: 2429.txt This is from 0.6.3: INFO [Timer-0] 2010-10-28 18:49:08,714 Gossiper.java (line 181) InetAddress /192.168.80.17 is now dead. INFO [WRITE-/192.168.80.17] 2010-10-28 18:49:48,719 OutboundTcpConnection.java (line 102) error writing to /192.168.80.17 INFO [GC inspection] 2010-10-28 18:50:18,425 GCInspector.java (line 110) GC for ConcurrentMarkSweep: 3463 ms, 77366288 reclaimed leaving 1006804528 used; max is 1207828480 INFO [GC inspection] 2010-10-28 18:50:29,792 GCInspector.java (line 110) GC for ConcurrentMarkSweep: 3465 ms, 71343920 reclaimed leaving 1013965608 used; max is 1207828480 INFO [GMFD:1] 2010-10-28 18:50:32,713 Gossiper.java (line 593) Node /192.168.80.17 has restarted, now UP again INFO [HINTED-HANDOFF-POOL:1] 2010-10-28 18:50:32,713 HintedHandOffManager.java (line 153) Started hinted handoff for endPoint /192.168.80.17 INFO [GMFD:1] 2010-10-28 18:50:32,713 StorageService.java (line 548) Node /192.168.80.17 state jump to normal This is from 0.7.1: INFO [ScheduledTasks:1] 2011-02-25 17:54:41,445 Gossiper.java (line 224) InetAddress /10.240.17.235 is now dead. INFO [GossipStage:1] 2011-02-25 17:54:41,449 Gossiper.java (line 605) InetAddress /10.240.17.235 is now UP INFO [GossipStage:1] 2011-02-25 17:55:05,570 Gossiper.java (line 619) Node /10.241.103.223 has restarted, now UP again INFO [HintedHandoff:1] 2011-02-25 17:55:20,581 HintedHandOffManager.java (line 286) Started hinted handoff for endpoint /10.240.17.235 INFO [HintedHandoff:1] 2011-02-25 17:55:20,583 HintedHandOffManager.java (line 342) Finished hinted handoff of 0 rows to endpoint /10.240.17.235 INFO [HintedHandoff:1] 2011-02-25 17:55:20,583 HintedHandOffManager.java (line 266) Checking remote schema before delivering hints INFO [HintedHandoff:1] 2011-02-25 17:55:20,583 HintedHandOffManager.java (line 272) Sleeping 56493ms to stagger hint delivery INFO [HintedHandoff:1] 2011-02-25 17:56:17,077 HintedHandOffManager.java (line 286) Started hinted handoff for endpoint /10.253.202.128 INFO [HintedHandoff:1] 2011-02-25 17:56:17,077 HintedHandOffManager.java (line 342) Finished hinted handoff of 0 rows to endpoint /10.253.202.128 INFO [HintedHandoff:1] 2011-02-25 17:56:17,078 HintedHandOffManager.java (line 266) Checking remote schema before delivering hints INFO [HintedHandoff:1] 2011-02-25 17:56:17,078 HintedHandOffManager.java (line 272) Sleeping 8680ms to stagger hint delivery INFO [HintedHandoff:1] 2011-02-25 17:56:25,758 HintedHandOffManager.java (line 286) Started hinted handoff for endpoint /10.241.103.223 INFO [HintedHandoff:1] 2011-02-25 17:56:25,759 HintedHandOffManager.java (line 342) Finished hinted handoff of 0 rows to endpoint /10.241.103.223 INFO [GossipStage:1] 2011-02-25 17:58:30,021 Gossiper.java (line 619) Node /10.253.183.111 has restarted, now UP again INFO [HintedHandoff:1] 2011-02-25 17:58:30,022 HintedHandOffManager.java (line 266) Checking remote schema before delivering hints INFO [HintedHandoff:1] 2011-02-25 17:58:30,022 HintedHandOffManager.java (line 272) Sleeping 43058ms to stagger hint delivery INFO [HintedHandoff:1] 2011-02-25 17:59:13,080 HintedHandOffManager.java (line 286) Started hinted handoff for endpoint /10.253.183.111 INFO [HintedHandoff:1] 2011-02-25 17:59:13,081 HintedHandOffManager.java (line 342) Finished hinted handoff of 0 rows to endpoint /10.253.183.111 INFO [GossipStage:1] 2011-02-25 18:00:27,827 Gossiper.java (line 619) Node /10.194.249.140 has restarted, now UP again INFO [HintedHandoff:1] 2011-02-25 18:00:27,827 HintedHandOffManager.java (line 266) Checking remote schema before delivering hints INFO [HintedHandoff:1] 2011-02-25 18:00:27,827 HintedHandOffManager.java (line 272) Sleeping 43035ms to stagger hint delivery INFO [HintedHandoff:1] 2011-02-25 18:01:10,863 HintedHandOffManager.java (line 286) Started hinted handoff for endpoint /10.194.249.140 INFO [HintedHandoff:1] 2011-02-25 18:01:10,863 HintedHandOffManager.java (line 342) Finished hinted handoff of 0 rows to endpoint /10.194.249.140 They are all over most logs and are very apparent
[jira] [Commented] (CASSANDRA-2501) Error running cqlsh from .tar file -- global name 'SchemaDisagreementException' is not defined
[
https://issues.apache.org/jira/browse/CASSANDRA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021599#comment-13021599
]
Hudson commented on CASSANDRA-2501:
---
Integrated in Cassandra-0.8 #21 (See
[https://hudson.apache.org/hudson/job/Cassandra-0.8/21/])
add SchemaDisagreementException import
patch by jbellis; tested by Cathy Daw for CASSANDRA-2501
Error running cqlsh from .tar file -- global name
'SchemaDisagreementException' is not defined
--
Key: CASSANDRA-2501
URL: https://issues.apache.org/jira/browse/CASSANDRA-2501
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.8
Environment: Running on 3-node Centos 5.5. The cql package was
installed with Python 2.6 and prior to installation, I downloaded and
installed thrift05-0.5.0.
Reporter: Cathy Daw
Assignee: Jonathan Ellis
Fix For: 0.8
Attachments: 2501.txt
*Error when running cqlsh*
{code}
[cassandra@cdaw-qa1 cql-1.0.0]$ cqlsh cdaw-qa1
Traceback (most recent call last):
File /usr/bin/cqlsh, line 212, in module
password=options.password)
File /usr/bin/cqlsh, line 55, in __init__
self.conn = cql.connect(hostname, port, user=username, password=password)
File /usr/lib/python2.6/site-packages/cql/__init__.py, line 51, in connect
return connection.Connection(host, port, keyspace, user, password)
File /usr/lib/python2.6/site-packages/cql/connection.py, line 53, in
__init__
c.execute('USE %s;' % keyspace)
File /usr/lib/python2.6/site-packages/cql/cursor.py, line 126, in execute
except SchemaDisagreementException, sde:
NameError: global name 'SchemaDisagreementException' is not defined
{code}
*Build*
* Install the cassandra binary from the nightly build
wget
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/apache-cassandra-2011-04-18_11-02-29-bin.tar.gz
* Install cql from .tar file on nightly build
wget
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/cql-1.0.0.tar.gz
*CQL Install Output*
{code}
[cassandra@cdaw-qa1 cql-1.0.0]$ sudo python2.6 ./setup.py install
[sudo] password for cassandra:
running install
running build
running build_py
running build_scripts
creating build/scripts-2.6
copying and adjusting cqlsh - build/scripts-2.6
changing mode of build/scripts-2.6/cqlsh from 644 to 755
running install_lib
creating /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/results.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/marshal.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/connection.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/cursor.py - /usr/lib/python2.6/site-packages/cql
creating /usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/__init__.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/Cassandra.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/constants.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/ttypes.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/decoders.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/__init__.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/errors.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/connection_pool.py -
/usr/lib/python2.6/site-packages/cql
byte-compiling /usr/lib/python2.6/site-packages/cql/results.py to results.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/marshal.py to marshal.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/connection.py to
connection.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cursor.py to cursor.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/__init__.py to
__init__.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/Cassandra.py to
Cassandra.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/constants.py to
constants.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/ttypes.py to
ttypes.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/decoders.py to
decoders.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/__init__.py to
__init__.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/errors.py to errors.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/connection_pool.py to
connection_pool.pyc
running install_scripts
copying build/scripts-2.6/cqlsh - /usr/bin
changing mode of /usr/bin/cqlsh to 755
running install_egg_info
Writing /usr/lib/python2.6/site-packages/cql-1.0.0-py2.6.egg-info
{code}
--
[jira] [Commented] (CASSANDRA-2408) Faulty memory causes adjacent nodes to have invalid data and fail compactation (java.io.IOException: Keys must be written in ascending order.)
[ https://issues.apache.org/jira/browse/CASSANDRA-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021602#comment-13021602 ] Jonathan Ellis commented on CASSANDRA-2408: --- Did you run any repairs _before_ seeing this? SSTableWriter checks order (of data written out of a memtable) at write time, so the only way to get data out-of-order should be to stream it from a corrupt node. Repair would explain why it affects adjacent noces too. Faulty memory causes adjacent nodes to have invalid data and fail compactation (java.io.IOException: Keys must be written in ascending order.) -- Key: CASSANDRA-2408 URL: https://issues.apache.org/jira/browse/CASSANDRA-2408 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.4 Reporter: Thibaut Fix For: 0.7.6 Hi, We had to replace a node with faulty ram. Besides the cassandra cluster getting unresponsive, we also observerd a keys must be written in ascending order exception on all adjacent quorum nodes, causing their compactation to fail. We had another node with faulty ram a week earlier, and it was causing the same errors on it's neighbours. A faulty node shouldn't affect the key ordering of adjacent nodes? INFO [CompactionExecutor:1] 2011-03-31 09:57:29,529 CompactionManager.java (line 396) Compacting [SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1793-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1798-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1803-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1808-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1832-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1841-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1852-Data.db')] INFO [CompactionExecutor:1] 2011-03-31 09:58:26,437 SSTableWriter.java (line 108) Last written key : DecoratedKey(ba578bed5e75a06d1156dabccc68abd5_www.abc.com_hostinlinks_9223370735413988125_870cc25d-7e4f-437b-aa83-a311dfbf7f88, 62613537386265643565373561303664313135366461626363633638616264355f772e6b6f7475736f7a6c756b2e636f6d5f686f7374696e6c696e6b735f39323237303733353431333938383132355f38373063633235642d376534662d343337622d616138332d613331316466626637663838) INFO [CompactionExecutor:1] 2011-03-31 09:58:26,515 SSTableWriter.java (line 109) Current key : DecoratedKey(ba578bed5e75a06d1156dabccc68abd5_www.abc.com_hostinlinks_9223370735413988136_17070303-ab24-4207-83bd-1604e2c159e4, 62613537386265643565373561303664313135366461626363633638616264355f772e6b677475736f7a6c756b2e636f6d5f686f7374696e6c696e6b735f39323237303733353431333938383133365f31373037303330332d616232342d343230372d383362642d313630346532633135396534) INFO [CompactionExecutor:1] 2011-03-31 09:58:26,515 SSTableWriter.java (line 110) Writing into file /cassandra/data/table_lists/table_lists-tmp-f-1861-Data.db ERROR [CompactionExecutor:1] 2011-03-31 09:58:26,516 AbstractCassandraDaemon.java (line 112) Fatal exception in thread Thread[CompactionExecutor:1,1,main] java.io.IOException: Keys must be written in ascending order. at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:111) at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:128) at org.apache.cassandra.db.CompactionManager.doCompaction(CompactionManager.java:452) at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:124) at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:94) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2460) Make scrub validate deserialized columns
[ https://issues.apache.org/jira/browse/CASSANDRA-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021600#comment-13021600 ] Hudson commented on CASSANDRA-2460: --- Integrated in Cassandra-0.8 #21 (See [https://hudson.apache.org/hudson/job/Cassandra-0.8/21/]) Make scrub validate deserialized columns Key: CASSANDRA-2460 URL: https://issues.apache.org/jira/browse/CASSANDRA-2460 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Fix For: 0.7.5 Attachments: 0001-Make-scrub-check-column-fields-v2.patch, 0001-Make-scrub-check-column-fields.patch Original Estimate: 4h Remaining Estimate: 4h Right now, scrub deserialize the columns but don't validate the fields, and such there is a number of errors it could fix (or at least corrupted rows it could skip) but don't. This ticket proposes to handle those errors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-2408) Faulty memory causes adjacent nodes to have invalid data and fail compactation (java.io.IOException: Keys must be written in ascending order.)
[ https://issues.apache.org/jira/browse/CASSANDRA-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021602#comment-13021602 ] Jonathan Ellis edited comment on CASSANDRA-2408 at 4/19/11 2:21 PM: Did you run any repairs _before_ seeing this? SSTableWriter checks order (of data written out of a memtable) at write time, so the only way to get data out-of-order should be to stream it from a corrupt node. Repair would explain why it affects adjacent nodes too. was (Author: jbellis): Did you run any repairs _before_ seeing this? SSTableWriter checks order (of data written out of a memtable) at write time, so the only way to get data out-of-order should be to stream it from a corrupt node. Repair would explain why it affects adjacent noces too. Faulty memory causes adjacent nodes to have invalid data and fail compactation (java.io.IOException: Keys must be written in ascending order.) -- Key: CASSANDRA-2408 URL: https://issues.apache.org/jira/browse/CASSANDRA-2408 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.4 Reporter: Thibaut Fix For: 0.7.6 Hi, We had to replace a node with faulty ram. Besides the cassandra cluster getting unresponsive, we also observerd a keys must be written in ascending order exception on all adjacent quorum nodes, causing their compactation to fail. We had another node with faulty ram a week earlier, and it was causing the same errors on it's neighbours. A faulty node shouldn't affect the key ordering of adjacent nodes? INFO [CompactionExecutor:1] 2011-03-31 09:57:29,529 CompactionManager.java (line 396) Compacting [SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1793-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1798-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1803-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1808-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1832-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1841-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1852-Data.db')] INFO [CompactionExecutor:1] 2011-03-31 09:58:26,437 SSTableWriter.java (line 108) Last written key : DecoratedKey(ba578bed5e75a06d1156dabccc68abd5_www.abc.com_hostinlinks_9223370735413988125_870cc25d-7e4f-437b-aa83-a311dfbf7f88, 62613537386265643565373561303664313135366461626363633638616264355f772e6b6f7475736f7a6c756b2e636f6d5f686f7374696e6c696e6b735f39323237303733353431333938383132355f38373063633235642d376534662d343337622d616138332d613331316466626637663838) INFO [CompactionExecutor:1] 2011-03-31 09:58:26,515 SSTableWriter.java (line 109) Current key : DecoratedKey(ba578bed5e75a06d1156dabccc68abd5_www.abc.com_hostinlinks_9223370735413988136_17070303-ab24-4207-83bd-1604e2c159e4, 62613537386265643565373561303664313135366461626363633638616264355f772e6b677475736f7a6c756b2e636f6d5f686f7374696e6c696e6b735f39323237303733353431333938383133365f31373037303330332d616232342d343230372d383362642d313630346532633135396534) INFO [CompactionExecutor:1] 2011-03-31 09:58:26,515 SSTableWriter.java (line 110) Writing into file /cassandra/data/table_lists/table_lists-tmp-f-1861-Data.db ERROR [CompactionExecutor:1] 2011-03-31 09:58:26,516 AbstractCassandraDaemon.java (line 112) Fatal exception in thread Thread[CompactionExecutor:1,1,main] java.io.IOException: Keys must be written in ascending order. at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:111) at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:128) at org.apache.cassandra.db.CompactionManager.doCompaction(CompactionManager.java:452) at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:124) at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:94) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2408) Faulty memory causes adjacent nodes to have invalid data and fail compactation (java.io.IOException: Keys must be written in ascending order.)
[ https://issues.apache.org/jira/browse/CASSANDRA-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021612#comment-13021612 ] Thibaut commented on CASSANDRA-2408: I might have run a repair on the faulty node before, but I don't think I ran a repair on the adjacent nodes, as there was no logical need to do this. However, I can't completely exclude it. We also replaced about 8 machines so far with faulty memory, and this problem only occured twice (on 6 different machines). If I do a write ONE on the faulty node, the faulty node might also be buffering delayed writes for the other nodes? What if the a bit flip happens there? Faulty memory causes adjacent nodes to have invalid data and fail compactation (java.io.IOException: Keys must be written in ascending order.) -- Key: CASSANDRA-2408 URL: https://issues.apache.org/jira/browse/CASSANDRA-2408 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.4 Reporter: Thibaut Fix For: 0.7.6 Hi, We had to replace a node with faulty ram. Besides the cassandra cluster getting unresponsive, we also observerd a keys must be written in ascending order exception on all adjacent quorum nodes, causing their compactation to fail. We had another node with faulty ram a week earlier, and it was causing the same errors on it's neighbours. A faulty node shouldn't affect the key ordering of adjacent nodes? INFO [CompactionExecutor:1] 2011-03-31 09:57:29,529 CompactionManager.java (line 396) Compacting [SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1793-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1798-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1803-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1808-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1832-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1841-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1852-Data.db')] INFO [CompactionExecutor:1] 2011-03-31 09:58:26,437 SSTableWriter.java (line 108) Last written key : DecoratedKey(ba578bed5e75a06d1156dabccc68abd5_www.abc.com_hostinlinks_9223370735413988125_870cc25d-7e4f-437b-aa83-a311dfbf7f88, 62613537386265643565373561303664313135366461626363633638616264355f772e6b6f7475736f7a6c756b2e636f6d5f686f7374696e6c696e6b735f39323237303733353431333938383132355f38373063633235642d376534662d343337622d616138332d613331316466626637663838) INFO [CompactionExecutor:1] 2011-03-31 09:58:26,515 SSTableWriter.java (line 109) Current key : DecoratedKey(ba578bed5e75a06d1156dabccc68abd5_www.abc.com_hostinlinks_9223370735413988136_17070303-ab24-4207-83bd-1604e2c159e4, 62613537386265643565373561303664313135366461626363633638616264355f772e6b677475736f7a6c756b2e636f6d5f686f7374696e6c696e6b735f39323237303733353431333938383133365f31373037303330332d616232342d343230372d383362642d313630346532633135396534) INFO [CompactionExecutor:1] 2011-03-31 09:58:26,515 SSTableWriter.java (line 110) Writing into file /cassandra/data/table_lists/table_lists-tmp-f-1861-Data.db ERROR [CompactionExecutor:1] 2011-03-31 09:58:26,516 AbstractCassandraDaemon.java (line 112) Fatal exception in thread Thread[CompactionExecutor:1,1,main] java.io.IOException: Keys must be written in ascending order. at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:111) at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:128) at org.apache.cassandra.db.CompactionManager.doCompaction(CompactionManager.java:452) at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:124) at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:94) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2355) Allow parameters for comparator
[ https://issues.apache.org/jira/browse/CASSANDRA-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-2355: Attachment: 0001-Allow-comparators-to-take-arguments-ReversedType-v3.patch Attached v3 (v3 is for coherence with CASSANDRA-2231) is rebased on 0.8. Allow parameters for comparator --- Key: CASSANDRA-2355 URL: https://issues.apache.org/jira/browse/CASSANDRA-2355 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Minor Fix For: 1.0 Attachments: 0001-Allow-comparators-to-take-arguments-ReversedType-v3.patch, Allow-comparators-to-take-arguments-ReversedType.patch Original Estimate: 4h Remaining Estimate: 4h Being able to provide arguments to a comparator, to parametrize its behavior, can be useful. For example, a generic ReverseComparator is trivial to write, but without the ability to provide arguments at the comparator constriction, it cannot be used. CASSANDRA-2231 provides another use case for this. This ticket proposes to introduce a parser for comparator definition that supports optional parameters and to introduce a generic ReverseType as a simple example of this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2355) Allow parameters for comparator
[ https://issues.apache.org/jira/browse/CASSANDRA-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-2355: Fix Version/s: (was: 1.0) 0.8 Allow parameters for comparator --- Key: CASSANDRA-2355 URL: https://issues.apache.org/jira/browse/CASSANDRA-2355 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Minor Fix For: 0.8 Attachments: 0001-Allow-comparators-to-take-arguments-ReversedType-v3.patch, Allow-comparators-to-take-arguments-ReversedType.patch Original Estimate: 4h Remaining Estimate: 4h Being able to provide arguments to a comparator, to parametrize its behavior, can be useful. For example, a generic ReverseComparator is trivial to write, but without the ability to provide arguments at the comparator constriction, it cannot be used. CASSANDRA-2231 provides another use case for this. This ticket proposes to introduce a parser for comparator definition that supports optional parameters and to introduce a generic ReverseType as a simple example of this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2231) Add CompositeType comparer to the comparers provided in org.apache.cassandra.db.marshal
[ https://issues.apache.org/jira/browse/CASSANDRA-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-2231: Attachment: 0001-Add-compositeType-and-DynamicCompositeType-v3.patch Attaching v3 rebased to 0.8. It applies on top of CASSANDRA-2355. Add CompositeType comparer to the comparers provided in org.apache.cassandra.db.marshal --- Key: CASSANDRA-2231 URL: https://issues.apache.org/jira/browse/CASSANDRA-2231 Project: Cassandra Issue Type: Improvement Components: Contrib Affects Versions: 0.7.3 Reporter: Ed Anuff Assignee: Sylvain Lebresne Priority: Minor Fix For: 0.7.5 Attachments: 0001-Add-compositeType-and-DynamicCompositeType-v2.patch, 0001-Add-compositeType-and-DynamicCompositeType-v3.patch, CompositeType-and-DynamicCompositeType.patch, edanuff-CassandraCompositeType-1e253c4.zip CompositeType is a custom comparer that makes it possible to create comparable composite values out of the basic types that Cassandra currently supports, such as Long, UUID, etc. This is very useful in both the creation of custom inverted indexes using columns in a skinny row, where each column name is a composite value, and also when using Cassandra's built-in secondary index support, where it can be used to encode the values in the columns that Cassandra indexes. One scenario for the usage of these is documented here: http://www.anuff.com/2010/07/secondary-indexes-in-cassandra.html. Source for contribution is attached and has been previously maintained on github here: https://github.com/edanuff/CassandraCompositeType -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2355) Allow parameters for comparator
[ https://issues.apache.org/jira/browse/CASSANDRA-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-2355: Fix Version/s: (was: 0.8) 0.8.1 Issue Type: New Feature (was: Improvement) Allow parameters for comparator --- Key: CASSANDRA-2355 URL: https://issues.apache.org/jira/browse/CASSANDRA-2355 Project: Cassandra Issue Type: New Feature Components: Core Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Priority: Minor Fix For: 0.8.1 Attachments: 0001-Allow-comparators-to-take-arguments-ReversedType-v3.patch, Allow-comparators-to-take-arguments-ReversedType.patch Original Estimate: 4h Remaining Estimate: 4h Being able to provide arguments to a comparator, to parametrize its behavior, can be useful. For example, a generic ReverseComparator is trivial to write, but without the ability to provide arguments at the comparator constriction, it cannot be used. CASSANDRA-2231 provides another use case for this. This ticket proposes to introduce a parser for comparator definition that supports optional parameters and to introduce a generic ReverseType as a simple example of this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2231) Add CompositeType comparer to the comparers provided in org.apache.cassandra.db.marshal
[ https://issues.apache.org/jira/browse/CASSANDRA-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-2231: Affects Version/s: (was: 0.7.3) Fix Version/s: (was: 0.7.5) 0.8.1 Issue Type: New Feature (was: Improvement) Add CompositeType comparer to the comparers provided in org.apache.cassandra.db.marshal --- Key: CASSANDRA-2231 URL: https://issues.apache.org/jira/browse/CASSANDRA-2231 Project: Cassandra Issue Type: New Feature Components: Contrib Reporter: Ed Anuff Assignee: Sylvain Lebresne Priority: Minor Fix For: 0.8.1 Attachments: 0001-Add-compositeType-and-DynamicCompositeType-v2.patch, 0001-Add-compositeType-and-DynamicCompositeType-v3.patch, CompositeType-and-DynamicCompositeType.patch, edanuff-CassandraCompositeType-1e253c4.zip CompositeType is a custom comparer that makes it possible to create comparable composite values out of the basic types that Cassandra currently supports, such as Long, UUID, etc. This is very useful in both the creation of custom inverted indexes using columns in a skinny row, where each column name is a composite value, and also when using Cassandra's built-in secondary index support, where it can be used to encode the values in the columns that Cassandra indexes. One scenario for the usage of these is documented here: http://www.anuff.com/2010/07/secondary-indexes-in-cassandra.html. Source for contribution is attached and has been previously maintained on github here: https://github.com/edanuff/CassandraCompositeType -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2501) Error running cqlsh from .tar file -- global name 'SchemaDisagreementException' is not defined
[
https://issues.apache.org/jira/browse/CASSANDRA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Evans updated CASSANDRA-2501:
--
Labels: cql (was: )
Error running cqlsh from .tar file -- global name
'SchemaDisagreementException' is not defined
--
Key: CASSANDRA-2501
URL: https://issues.apache.org/jira/browse/CASSANDRA-2501
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.8
Environment: Running on 3-node Centos 5.5. The cql package was
installed with Python 2.6 and prior to installation, I downloaded and
installed thrift05-0.5.0.
Reporter: Cathy Daw
Assignee: Jonathan Ellis
Labels: cql
Fix For: 0.8
Attachments: 2501.txt
*Error when running cqlsh*
{code}
[cassandra@cdaw-qa1 cql-1.0.0]$ cqlsh cdaw-qa1
Traceback (most recent call last):
File /usr/bin/cqlsh, line 212, in module
password=options.password)
File /usr/bin/cqlsh, line 55, in __init__
self.conn = cql.connect(hostname, port, user=username, password=password)
File /usr/lib/python2.6/site-packages/cql/__init__.py, line 51, in connect
return connection.Connection(host, port, keyspace, user, password)
File /usr/lib/python2.6/site-packages/cql/connection.py, line 53, in
__init__
c.execute('USE %s;' % keyspace)
File /usr/lib/python2.6/site-packages/cql/cursor.py, line 126, in execute
except SchemaDisagreementException, sde:
NameError: global name 'SchemaDisagreementException' is not defined
{code}
*Build*
* Install the cassandra binary from the nightly build
wget
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/apache-cassandra-2011-04-18_11-02-29-bin.tar.gz
* Install cql from .tar file on nightly build
wget
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/cql-1.0.0.tar.gz
*CQL Install Output*
{code}
[cassandra@cdaw-qa1 cql-1.0.0]$ sudo python2.6 ./setup.py install
[sudo] password for cassandra:
running install
running build
running build_py
running build_scripts
creating build/scripts-2.6
copying and adjusting cqlsh - build/scripts-2.6
changing mode of build/scripts-2.6/cqlsh from 644 to 755
running install_lib
creating /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/results.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/marshal.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/connection.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/cursor.py - /usr/lib/python2.6/site-packages/cql
creating /usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/__init__.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/Cassandra.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/constants.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/cassandra/ttypes.py -
/usr/lib/python2.6/site-packages/cql/cassandra
copying build/lib/cql/decoders.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/__init__.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/errors.py - /usr/lib/python2.6/site-packages/cql
copying build/lib/cql/connection_pool.py -
/usr/lib/python2.6/site-packages/cql
byte-compiling /usr/lib/python2.6/site-packages/cql/results.py to results.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/marshal.py to marshal.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/connection.py to
connection.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cursor.py to cursor.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/__init__.py to
__init__.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/Cassandra.py to
Cassandra.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/constants.py to
constants.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/cassandra/ttypes.py to
ttypes.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/decoders.py to
decoders.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/__init__.py to
__init__.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/errors.py to errors.pyc
byte-compiling /usr/lib/python2.6/site-packages/cql/connection_pool.py to
connection_pool.pyc
running install_scripts
copying build/scripts-2.6/cqlsh - /usr/bin
changing mode of /usr/bin/cqlsh to 755
running install_egg_info
Writing /usr/lib/python2.6/site-packages/cql-1.0.0-py2.6.egg-info
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Cassandra Wiki] Update of FAQ_JP by MakiWatanabe
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The FAQ_JP page has been changed by MakiWatanabe. The comment on this change is: Translate bigcommitlog. http://wiki.apache.org/cassandra/FAQ_JP?action=diffrev1=81rev2=82 -- * [[#jna|Keyspaceを更新したり、スナップショットをとろうとしたときに java.io.IOException: Cannot run program ln が発生します]] * [[#replicaplacement|Cassandraはどのデータがどのノードに配置されているかをどのように判定しますか？]] * [[#cachehitrateunits|JMXで行キャッシュあるいはキーキャッシュのヒット率が0.XX123456789のように表示されます。これはXX%という意味でしょうか？それとも0.XX%でしょうか？]] + * [[#bigcommitlog|Commit Logが大変肥大化しています。Cassandraは古いCommit Logを削除しないのでしょうか？]] Anchor(cant_listen_on_ip_any) @@ -488, +489 @@ == JMXで行キャッシュあるいはキーキャッシュのヒット率が0.XX123456789のように表示されます。これはXX%という意味でしょうか？それとも0.XX%でしょうか？ == - XX% + XX%です。 + Anchor(bigcommitlog) + + == Commit Logが大変肥大化しています。Cassandraは古いCommit Logを削除しないのでしょうか？ == + + 少数のカラムファミリーを非常に低いスループットで使用していませんか？このようなカラムファミリはフラッシュされる頻度が低く、commit logは削除されません。回避方法をひとつ紹介します。それは、カラムファミリー別のオプションである、memtable_flush_after_minを設定することです。この設定により、カラムファミリーを X 分毎にフラッシュさせることができます。初期設定としては、60分からはじめるのがよいでしょう。この設定をするには、cassandra-cliで以下のコマンドを実行して下さい。 + + update column family XXX with memtable_flush_after=60; +
[jira] [Created] (CASSANDRA-2505) cqlsh can't decode column names/values
cqlsh can't decode column names/values -- Key: CASSANDRA-2505 URL: https://issues.apache.org/jira/browse/CASSANDRA-2505 Project: Cassandra Issue Type: Bug Components: API, Tools Affects Versions: 0.8 Reporter: Eric Evans Assignee: Eric Evans Fix For: 0.8 The way results are accessed, cqlsh is displaying the raw thrift results and not the decoded values. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2505) cqlsh can't decode column names/values
[ https://issues.apache.org/jira/browse/CASSANDRA-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Evans updated CASSANDRA-2505: -- Attachment: v1-0001-CASSANDRA-2505-use-dbapi-interface-for-decoded-values.txt cqlsh can't decode column names/values -- Key: CASSANDRA-2505 URL: https://issues.apache.org/jira/browse/CASSANDRA-2505 Project: Cassandra Issue Type: Bug Components: API, Tools Affects Versions: 0.8 Reporter: Eric Evans Assignee: Eric Evans Labels: cql Fix For: 0.8 Attachments: v1-0001-CASSANDRA-2505-use-dbapi-interface-for-decoded-values.txt The way results are accessed, cqlsh is displaying the raw thrift results and not the decoded values. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-2506) Push read repair setting down to the DC-level
Push read repair setting down to the DC-level - Key: CASSANDRA-2506 URL: https://issues.apache.org/jira/browse/CASSANDRA-2506 Project: Cassandra Issue Type: New Feature Components: Core Reporter: Brandon Williams Currently, read repair is a global setting. However, when you have two DCs and use one for analytics, it would be nice to turn it off only for that DC to the live DC serving the application can still benefit from it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-2506: Description: Currently, read repair is a global setting. However, when you have two DCs and use one for analytics, it would be nice to turn it off only for that DC so the live DC serving the application can still benefit from it. (was: Currently, read repair is a global setting. However, when you have two DCs and use one for analytics, it would be nice to turn it off only for that DC to the live DC serving the application can still benefit from it.) Push read repair setting down to the DC-level - Key: CASSANDRA-2506 URL: https://issues.apache.org/jira/browse/CASSANDRA-2506 Project: Cassandra Issue Type: New Feature Components: Core Reporter: Brandon Williams Currently, read repair is a global setting. However, when you have two DCs and use one for analytics, it would be nice to turn it off only for that DC so the live DC serving the application can still benefit from it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-2507) Python CQL driver does not decode most values
Python CQL driver does not decode most values
-
Key: CASSANDRA-2507
URL: https://issues.apache.org/jira/browse/CASSANDRA-2507
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 0.8
Reporter: Eric Evans
Fix For: 0.8
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything but
strings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2507) Python CQL driver does not decode most values
[
https://issues.apache.org/jira/browse/CASSANDRA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Evans updated CASSANDRA-2507:
--
Labels: cql (was: )
Python CQL driver does not decode most values
-
Key: CASSANDRA-2507
URL: https://issues.apache.org/jira/browse/CASSANDRA-2507
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 0.8
Reporter: Eric Evans
Labels: cql
Fix For: 0.8
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything
but strings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2507) Python CQL driver does not decode most values
[
https://issues.apache.org/jira/browse/CASSANDRA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Evans updated CASSANDRA-2507:
--
Description:
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
_Note: requires the patch from CASSANDRA-2505 to be applied_
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything but
strings.
was:
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything but
strings.
Python CQL driver does not decode most values
-
Key: CASSANDRA-2507
URL: https://issues.apache.org/jira/browse/CASSANDRA-2507
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 0.8
Reporter: Eric Evans
Labels: cql
Fix For: 0.8
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
_Note: requires the patch from CASSANDRA-2505 to be applied_
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything
but strings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2505) cqlsh can't decode column names/values
[ https://issues.apache.org/jira/browse/CASSANDRA-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021666#comment-13021666 ] Jonathan Ellis commented on CASSANDRA-2505: --- +1 cqlsh can't decode column names/values -- Key: CASSANDRA-2505 URL: https://issues.apache.org/jira/browse/CASSANDRA-2505 Project: Cassandra Issue Type: Bug Components: API, Tools Affects Versions: 0.8 Reporter: Eric Evans Assignee: Eric Evans Labels: cql Fix For: 0.8 Attachments: v1-0001-CASSANDRA-2505-use-dbapi-interface-for-decoded-values.txt The way results are accessed, cqlsh is displaying the raw thrift results and not the decoded values. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2408) Faulty memory causes adjacent nodes to have invalid data and fail compactation (java.io.IOException: Keys must be written in ascending order.)
[ https://issues.apache.org/jira/browse/CASSANDRA-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021669#comment-13021669 ] Jonathan Ellis commented on CASSANDRA-2408: --- If the coordinator flips bits before sending the write to a data node, the data node will write out the flipped key, but in the correct order (for the flipped version). Faulty memory causes adjacent nodes to have invalid data and fail compactation (java.io.IOException: Keys must be written in ascending order.) -- Key: CASSANDRA-2408 URL: https://issues.apache.org/jira/browse/CASSANDRA-2408 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.4 Reporter: Thibaut Fix For: 0.7.6 Hi, We had to replace a node with faulty ram. Besides the cassandra cluster getting unresponsive, we also observerd a keys must be written in ascending order exception on all adjacent quorum nodes, causing their compactation to fail. We had another node with faulty ram a week earlier, and it was causing the same errors on it's neighbours. A faulty node shouldn't affect the key ordering of adjacent nodes? INFO [CompactionExecutor:1] 2011-03-31 09:57:29,529 CompactionManager.java (line 396) Compacting [SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1793-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1798-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1803-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1808-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1832-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1841-Data.db'),SSTableReader(path='/cassandra/data/table_lists/table_lists-f-1852-Data.db')] INFO [CompactionExecutor:1] 2011-03-31 09:58:26,437 SSTableWriter.java (line 108) Last written key : DecoratedKey(ba578bed5e75a06d1156dabccc68abd5_www.abc.com_hostinlinks_9223370735413988125_870cc25d-7e4f-437b-aa83-a311dfbf7f88, 62613537386265643565373561303664313135366461626363633638616264355f772e6b6f7475736f7a6c756b2e636f6d5f686f7374696e6c696e6b735f39323237303733353431333938383132355f38373063633235642d376534662d343337622d616138332d613331316466626637663838) INFO [CompactionExecutor:1] 2011-03-31 09:58:26,515 SSTableWriter.java (line 109) Current key : DecoratedKey(ba578bed5e75a06d1156dabccc68abd5_www.abc.com_hostinlinks_9223370735413988136_17070303-ab24-4207-83bd-1604e2c159e4, 62613537386265643565373561303664313135366461626363633638616264355f772e6b677475736f7a6c756b2e636f6d5f686f7374696e6c696e6b735f39323237303733353431333938383133365f31373037303330332d616232342d343230372d383362642d313630346532633135396534) INFO [CompactionExecutor:1] 2011-03-31 09:58:26,515 SSTableWriter.java (line 110) Writing into file /cassandra/data/table_lists/table_lists-tmp-f-1861-Data.db ERROR [CompactionExecutor:1] 2011-03-31 09:58:26,516 AbstractCassandraDaemon.java (line 112) Fatal exception in thread Thread[CompactionExecutor:1,1,main] java.io.IOException: Keys must be written in ascending order. at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:111) at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:128) at org.apache.cassandra.db.CompactionManager.doCompaction(CompactionManager.java:452) at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:124) at org.apache.cassandra.db.CompactionManager$1.call(CompactionManager.java:94) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2507) Python CQL driver does not decode most values
[
https://issues.apache.org/jira/browse/CASSANDRA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Evans updated CASSANDRA-2507:
--
Attachment: repro.cql
Python CQL driver does not decode most values
-
Key: CASSANDRA-2507
URL: https://issues.apache.org/jira/browse/CASSANDRA-2507
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 0.8
Reporter: Eric Evans
Labels: cql
Fix For: 0.8
Attachments: repro.cql
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
_Note: requires the patch from CASSANDRA-2505 to be applied_
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything
but strings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095143 - /cassandra/branches/cassandra-0.8/drivers/py/cqlsh
Author: eevans Date: Tue Apr 19 17:35:25 2011 New Revision: 1095143 URL: http://svn.apache.org/viewvc?rev=1095143view=rev Log: use dbapi interface for decoded values Patch by eevans; reviewed by jbellis for CASSANDRA-2505 Modified: cassandra/branches/cassandra-0.8/drivers/py/cqlsh Modified: cassandra/branches/cassandra-0.8/drivers/py/cqlsh URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cqlsh?rev=1095143r1=1095142r2=1095143view=diff == --- cassandra/branches/cassandra-0.8/drivers/py/cqlsh (original) +++ cassandra/branches/cassandra-0.8/drivers/py/cqlsh Tue Apr 19 17:35:25 2011 @@ -90,14 +90,15 @@ class Shell(cmd.Cmd): cursor.execute(statement) if isinstance(cursor.result, ResultSet): -for row in cursor.result.rows: -self.printout(row.key, BLUE, False) -for column in row.columns: +for x in range(cursor.rowcount): +row = cursor.fetchone() +self.printout(row[0], BLUE, False) +for (i, value) in enumerate(row[1:]): +name = cursor.description[i+1][0] self.printout( | , newline=False) -# XXX: repr() is better than trying to print binary -self.printout(repr(column.name), MAGENTA, False) +self.printout(repr(name), MAGENTA, False) self.printout(,, newline=False) -self.printout(repr(column.value), YELLOW, False) +self.printout(repr(value), YELLOW, False) self.printout() else: if cursor.result: print cursor.result[0]
[jira] [Assigned] (CASSANDRA-2507) Python CQL driver does not decode most values
[
https://issues.apache.org/jira/browse/CASSANDRA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis reassigned CASSANDRA-2507:
-
Assignee: Tyler Hobbs
Python CQL driver does not decode most values
-
Key: CASSANDRA-2507
URL: https://issues.apache.org/jira/browse/CASSANDRA-2507
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 0.8
Reporter: Eric Evans
Assignee: Tyler Hobbs
Labels: cql
Fix For: 0.8
Attachments: repro.cql
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
_Note: requires the patch from CASSANDRA-2505 to be applied_
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything
but strings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2488) cqlsh errors on comments that end with a semicolon
[ https://issues.apache.org/jira/browse/CASSANDRA-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021680#comment-13021680 ] Gary Dusbabek commented on CASSANDRA-2488: -- +1 cqlsh errors on comments that end with a semicolon -- Key: CASSANDRA-2488 URL: https://issues.apache.org/jira/browse/CASSANDRA-2488 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 0.8 Environment: OS X 10.6.7 $ java -version java version 1.6.0_24 Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode) (This stuff isn't really important. It's a bug in a Python script) Reporter: Geoff Greer Assignee: Eric Evans Priority: Minor Labels: cql Fix For: 0.8 Attachments: v2-0001-CASSANDRA-2488-teach-cqlsh-to-ignore-comments.txt Commented-out lines that end in a semicolon cause an error. Examples: cqlsh -- CREATE KEYSPACE ELE WITH replication_factor = 3 AND strategy_class = SimpleStrategy AND strategy_options:replication_factor=3; Bad Request: line 0:-1 no viable alternative at input 'EOF' cqlsh -- CREATE KEYSPACE ELE WITH replication_factor = 3 AND strategy_class = SimpleStrategy AND strategy_options:replication_factor=3 ... ... ... ; Bad Request: line 2:0 no viable alternative at input ';' cqlsh -- ; Bad Request: line 0:-1 no viable alternative at input 'EOF' cqlsh --; Bad Request: line 0:-1 no viable alternative at input 'EOF' As long as there's a line with valid CQL before the semicolon, things work fine though. I'm pretty sure the problem is on line 75 of cqlsh: if not line.endswith(;): self.set_prompt(Shell.continue_prompt) return None A quick workaround would be to kill the pretty continue prompt. A more involved fix would detect whether or not the semicolon was in a comment. This is harder than it sounds, since /* and */ allow multi-line comments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-2508) missing imports in CQL Python driver
missing imports in CQL Python driver Key: CASSANDRA-2508 URL: https://issues.apache.org/jira/browse/CASSANDRA-2508 Project: Cassandra Issue Type: Bug Reporter: Eric Evans Try: bq. cd drivers/py python -c 'from cql import DateFromTicks; DateFromTicks(1)' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2508) missing imports in CQL Python driver
[
https://issues.apache.org/jira/browse/CASSANDRA-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Evans updated CASSANDRA-2508:
--
Description:
Try:
bq. cd drivers/py python -c 'from cql import DateFromTicks; DateFromTicks(1)'
Also:
{{cql.connection}} is missing an import of {{AuthenticationRequest}} from
{{ttypes}}, and the exceptions {{NotSupportedError}}, and {{InternalError}}.
was:
Try:
bq. cd drivers/py python -c 'from cql import DateFromTicks; DateFromTicks(1)'
missing imports in CQL Python driver
Key: CASSANDRA-2508
URL: https://issues.apache.org/jira/browse/CASSANDRA-2508
Project: Cassandra
Issue Type: Bug
Reporter: Eric Evans
Labels: cql
Try:
bq. cd drivers/py python -c 'from cql import DateFromTicks;
DateFromTicks(1)'
Also:
{{cql.connection}} is missing an import of {{AuthenticationRequest}} from
{{ttypes}}, and the exceptions {{NotSupportedError}}, and {{InternalError}}.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095149 - /cassandra/branches/cassandra-0.8/drivers/py/cqlsh
Author: eevans Date: Tue Apr 19 17:53:38 2011 New Revision: 1095149 URL: http://svn.apache.org/viewvc?rev=1095149view=rev Log: teach cqlsh to ignore comments Patch by eevans; reviewed by gdusbabek for CASSANDRA-2488 Modified: cassandra/branches/cassandra-0.8/drivers/py/cqlsh Modified: cassandra/branches/cassandra-0.8/drivers/py/cqlsh URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cqlsh?rev=1095149r1=1095148r2=1095149view=diff == --- cassandra/branches/cassandra-0.8/drivers/py/cqlsh (original) +++ cassandra/branches/cassandra-0.8/drivers/py/cqlsh Tue Apr 19 17:53:38 2011 @@ -64,12 +64,33 @@ class Shell(cmd.Cmd): self.statement = StringIO() self.color = color +self.in_comment = False def reset_statement(self): self.set_prompt(Shell.default_prompt) self.statement.truncate(0) def get_statement(self, line): +if self.in_comment: +if */ in line: +fragment = line[line.index(*/)+2:] +if fragment.strip(): +line = fragment +self.in_comment = False +else: +self.in_comment = False +self.set_prompt(Shell.default_prompt) +return None +else: +return None + +if /* in line and (not self.in_comment): +self.in_comment = True +self.set_prompt(Shell.continue_prompt) +if line.lstrip().index(/*) != 0: +self.statement.write(line[:line.lstrip().index(/*)]) +return None + self.statement.write(%s\n % line) if not line.endswith(;): @@ -82,8 +103,14 @@ class Shell(cmd.Cmd): self.reset_statement() def default(self, arg): -if not arg.strip(): return -statement = self.get_statement(arg) +def scrub_oneline_comments(s): +res = re.sub(r'\/\*.*\*\/', '', s) +res = re.sub(r'--.*$', '', res) +return res + +input = scrub_oneline_comments(arg) +if not input.strip(): return +statement = self.get_statement(input) if not statement: return cursor = self.conn.cursor()
[jira] [Resolved] (CASSANDRA-2488) cqlsh errors on comments that end with a semicolon
[ https://issues.apache.org/jira/browse/CASSANDRA-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Evans resolved CASSANDRA-2488. --- Resolution: Fixed committed cqlsh errors on comments that end with a semicolon -- Key: CASSANDRA-2488 URL: https://issues.apache.org/jira/browse/CASSANDRA-2488 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 0.8 Environment: OS X 10.6.7 $ java -version java version 1.6.0_24 Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode) (This stuff isn't really important. It's a bug in a Python script) Reporter: Geoff Greer Assignee: Eric Evans Priority: Minor Labels: cql Fix For: 0.8 Attachments: v2-0001-CASSANDRA-2488-teach-cqlsh-to-ignore-comments.txt Commented-out lines that end in a semicolon cause an error. Examples: cqlsh -- CREATE KEYSPACE ELE WITH replication_factor = 3 AND strategy_class = SimpleStrategy AND strategy_options:replication_factor=3; Bad Request: line 0:-1 no viable alternative at input 'EOF' cqlsh -- CREATE KEYSPACE ELE WITH replication_factor = 3 AND strategy_class = SimpleStrategy AND strategy_options:replication_factor=3 ... ... ... ; Bad Request: line 2:0 no viable alternative at input ';' cqlsh -- ; Bad Request: line 0:-1 no viable alternative at input 'EOF' cqlsh --; Bad Request: line 0:-1 no viable alternative at input 'EOF' As long as there's a line with valid CQL before the semicolon, things work fine though. I'm pretty sure the problem is on line 75 of cqlsh: if not line.endswith(;): self.set_prompt(Shell.continue_prompt) return None A quick workaround would be to kill the pretty continue prompt. A more involved fix would detect whether or not the semicolon was in a comment. This is harder than it sounds, since /* and */ allow multi-line comments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-2177) OPP + NTS + RF=2 reports wrong getRangeToEndpointMap
[
https://issues.apache.org/jira/browse/CASSANDRA-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-2177.
---
Resolution: Cannot Reproduce
Here is what I did:
{noformat}
ccm create 2177 -p OrderPreservingPartitioner
ccm add node2 -i 127.0.0.2 -j 7200 -s -n N
ccm add node1 -i 127.0.0.1 -j 7100 -s -n a
ccm add node3 -i 127.0.0.3 -j 7300 -s -n z
create keyspace bar with placement_strategy=NetworkTopologyStrategy and
strategy_options=[{datacenter1: 2}];
Address Status State LoadOwnsToken
z
127.0.0.2 Up Normal 50.65 KB33.33% N
127.0.0.1 Up Normal 50.65 KB33.33% a
127.0.0.3 Up Normal 50.65 KB33.33% z
{noformat}
(Note that capital letters sort before lower-case ones.)
getRangeToEndpointMap(bar) is (a,z]:[127.0.0.3, 127.0.0.2],(z,N]:[127.0.0.2,
127.0.0.1],(N,a]:[127.0.0.1, 127.0.0.3]
all nodes are represented twice.
OPP + NTS + RF=2 reports wrong getRangeToEndpointMap
Key: CASSANDRA-2177
URL: https://issues.apache.org/jira/browse/CASSANDRA-2177
Project: Cassandra
Issue Type: Bug
Reporter: Mike Bulman
OPP, 3 node cluster, RackInferringSnitch.
Ring:
[root@mb541 apache-cassandra-0.7.1]# bin/nodetool -h localhost ring
Address Status State LoadOwnsToken
zzz
1.2.3.4 Up Normal 42.48 KB33.33% aaa
1.2.3.5 Up Normal 42.39 KB33.33% rDwPSSIKSaXEwaaV
1.2.3.6 Up Normal 42.5 KB33.33% zzz
getRangeToEndPointMap for KS using NTS with {'2':2} replication returns:
{
('aaa', 'zzz'): ('1.2.3.6', '1.2.3.5'),
('zzz', 'NVOt7oNr1UcCzCEU'): ('1.2.3.5', '1.2.3.6'),
('NVOt7oNr1UcCzCEU', 'aaa'): ('1.2.3.4', '1.2.3.6')
}
node '4' is only represented once.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-2177) OPP + NTS + RF=2 reports wrong getRangeToEndpointMap
[
https://issues.apache.org/jira/browse/CASSANDRA-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021691#comment-13021691
]
Jonathan Ellis edited comment on CASSANDRA-2177 at 4/19/11 6:06 PM:
Here is what I did:
{noformat}
ccm create 2177 -p OrderPreservingPartitioner
ccm add node2 -i 127.0.0.2 -j 7200 -s -n N
ccm add node1 -i 127.0.0.1 -j 7100 -s -n a
ccm add node3 -i 127.0.0.3 -j 7300 -s -n z
create keyspace bar with placement_strategy=NetworkTopologyStrategy and
strategy_options=[{datacenter1: 2}];
Address Status State LoadOwnsToken
z
127.0.0.2 Up Normal 50.65 KB33.33% N
127.0.0.1 Up Normal 50.65 KB33.33% a
127.0.0.3 Up Normal 50.65 KB33.33% z
{noformat}
(Note that capital letters sort before lower-case ones.)
getRangeToEndpointMap(bar) is (a,z]:[127.0.0.3, 127.0.0.2], (z,N]:[127.0.0.2,
127.0.0.1], (N,a]:[127.0.0.1, 127.0.0.3]
all nodes are represented twice.
was (Author: jbellis):
Here is what I did:
{noformat}
ccm create 2177 -p OrderPreservingPartitioner
ccm add node2 -i 127.0.0.2 -j 7200 -s -n N
ccm add node1 -i 127.0.0.1 -j 7100 -s -n a
ccm add node3 -i 127.0.0.3 -j 7300 -s -n z
create keyspace bar with placement_strategy=NetworkTopologyStrategy and
strategy_options=[{datacenter1: 2}];
Address Status State LoadOwnsToken
z
127.0.0.2 Up Normal 50.65 KB33.33% N
127.0.0.1 Up Normal 50.65 KB33.33% a
127.0.0.3 Up Normal 50.65 KB33.33% z
{noformat}
(Note that capital letters sort before lower-case ones.)
getRangeToEndpointMap(bar) is (a,z]:[127.0.0.3, 127.0.0.2],(z,N]:[127.0.0.2,
127.0.0.1],(N,a]:[127.0.0.1, 127.0.0.3]
all nodes are represented twice.
OPP + NTS + RF=2 reports wrong getRangeToEndpointMap
Key: CASSANDRA-2177
URL: https://issues.apache.org/jira/browse/CASSANDRA-2177
Project: Cassandra
Issue Type: Bug
Reporter: Mike Bulman
OPP, 3 node cluster, RackInferringSnitch.
Ring:
[root@mb541 apache-cassandra-0.7.1]# bin/nodetool -h localhost ring
Address Status State LoadOwnsToken
zzz
1.2.3.4 Up Normal 42.48 KB33.33% aaa
1.2.3.5 Up Normal 42.39 KB33.33% rDwPSSIKSaXEwaaV
1.2.3.6 Up Normal 42.5 KB33.33% zzz
getRangeToEndPointMap for KS using NTS with {'2':2} replication returns:
{
('aaa', 'zzz'): ('1.2.3.6', '1.2.3.5'),
('zzz', 'NVOt7oNr1UcCzCEU'): ('1.2.3.5', '1.2.3.6'),
('NVOt7oNr1UcCzCEU', 'aaa'): ('1.2.3.4', '1.2.3.6')
}
node '4' is only represented once.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095151 - /cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/utils/FBUtilities.java
Author: jbellis
Date: Tue Apr 19 18:07:03 2011
New Revision: 1095151
URL: http://svn.apache.org/viewvc?rev=1095151view=rev
Log:
tweak toString(map)
Modified:
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/utils/FBUtilities.java
Modified:
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/utils/FBUtilities.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/utils/FBUtilities.java?rev=1095151r1=1095150r2=1095151view=diff
==
---
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/utils/FBUtilities.java
(original)
+++
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/utils/FBUtilities.java
Tue Apr 19 18:07:03 2011
@@ -575,7 +575,7 @@ public class FBUtilities
public static String toString(Map?,? map)
{
-Joiner.MapJoiner joiner = Joiner.on(,).withKeyValueSeparator(:);
+Joiner.MapJoiner joiner = Joiner.on(, ).withKeyValueSeparator(:);
return joiner.join(map);
}
[jira] [Issue Comment Edited] (CASSANDRA-2177) OPP + NTS + RF=2 reports wrong getRangeToEndpointMap
[
https://issues.apache.org/jira/browse/CASSANDRA-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021691#comment-13021691
]
Jonathan Ellis edited comment on CASSANDRA-2177 at 4/19/11 6:08 PM:
Here is what I did:
{noformat}
ccm create 2177 -p OrderPreservingPartitioner
ccm add node1 -i 127.0.0.1 -j 7100 -s -n a
ccm add node2 -i 127.0.0.2 -j 7200 -s -n N
ccm add node3 -i 127.0.0.3 -j 7300 -s -n z
create keyspace bar with placement_strategy=NetworkTopologyStrategy and
strategy_options=[{datacenter1: 2}];
Address Status State LoadOwnsToken
z
127.0.0.2 Up Normal 50.65 KB33.33% N
127.0.0.1 Up Normal 50.65 KB33.33% a
127.0.0.3 Up Normal 50.65 KB33.33% z
{noformat}
(Note that capital letters sort before lower-case ones.)
getRangeToEndpointMap(bar) is (a,z]:[127.0.0.3, 127.0.0.2], (z,N]:[127.0.0.2,
127.0.0.1], (N,a]:[127.0.0.1, 127.0.0.3]
all nodes are represented twice.
was (Author: jbellis):
Here is what I did:
{noformat}
ccm create 2177 -p OrderPreservingPartitioner
ccm add node2 -i 127.0.0.2 -j 7200 -s -n N
ccm add node1 -i 127.0.0.1 -j 7100 -s -n a
ccm add node3 -i 127.0.0.3 -j 7300 -s -n z
create keyspace bar with placement_strategy=NetworkTopologyStrategy and
strategy_options=[{datacenter1: 2}];
Address Status State LoadOwnsToken
z
127.0.0.2 Up Normal 50.65 KB33.33% N
127.0.0.1 Up Normal 50.65 KB33.33% a
127.0.0.3 Up Normal 50.65 KB33.33% z
{noformat}
(Note that capital letters sort before lower-case ones.)
getRangeToEndpointMap(bar) is (a,z]:[127.0.0.3, 127.0.0.2], (z,N]:[127.0.0.2,
127.0.0.1], (N,a]:[127.0.0.1, 127.0.0.3]
all nodes are represented twice.
OPP + NTS + RF=2 reports wrong getRangeToEndpointMap
Key: CASSANDRA-2177
URL: https://issues.apache.org/jira/browse/CASSANDRA-2177
Project: Cassandra
Issue Type: Bug
Reporter: Mike Bulman
OPP, 3 node cluster, RackInferringSnitch.
Ring:
[root@mb541 apache-cassandra-0.7.1]# bin/nodetool -h localhost ring
Address Status State LoadOwnsToken
zzz
1.2.3.4 Up Normal 42.48 KB33.33% aaa
1.2.3.5 Up Normal 42.39 KB33.33% rDwPSSIKSaXEwaaV
1.2.3.6 Up Normal 42.5 KB33.33% zzz
getRangeToEndPointMap for KS using NTS with {'2':2} replication returns:
{
('aaa', 'zzz'): ('1.2.3.6', '1.2.3.5'),
('zzz', 'NVOt7oNr1UcCzCEU'): ('1.2.3.5', '1.2.3.6'),
('NVOt7oNr1UcCzCEU', 'aaa'): ('1.2.3.4', '1.2.3.6')
}
node '4' is only represented once.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2505) cqlsh can't decode column names/values
[ https://issues.apache.org/jira/browse/CASSANDRA-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021734#comment-13021734 ] Hudson commented on CASSANDRA-2505: --- Integrated in Cassandra-0.8 #22 (See [https://hudson.apache.org/hudson/job/Cassandra-0.8/22/]) use dbapi interface for decoded values Patch by eevans; reviewed by jbellis for CASSANDRA-2505 cqlsh can't decode column names/values -- Key: CASSANDRA-2505 URL: https://issues.apache.org/jira/browse/CASSANDRA-2505 Project: Cassandra Issue Type: Bug Components: API, Tools Affects Versions: 0.8 Reporter: Eric Evans Assignee: Eric Evans Labels: cql Fix For: 0.8 Attachments: v1-0001-CASSANDRA-2505-use-dbapi-interface-for-decoded-values.txt The way results are accessed, cqlsh is displaying the raw thrift results and not the decoded values. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2488) cqlsh errors on comments that end with a semicolon
[ https://issues.apache.org/jira/browse/CASSANDRA-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021735#comment-13021735 ] Hudson commented on CASSANDRA-2488: --- Integrated in Cassandra-0.8 #22 (See [https://hudson.apache.org/hudson/job/Cassandra-0.8/22/]) teach cqlsh to ignore comments Patch by eevans; reviewed by gdusbabek for CASSANDRA-2488 cqlsh errors on comments that end with a semicolon -- Key: CASSANDRA-2488 URL: https://issues.apache.org/jira/browse/CASSANDRA-2488 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 0.8 Environment: OS X 10.6.7 $ java -version java version 1.6.0_24 Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode) (This stuff isn't really important. It's a bug in a Python script) Reporter: Geoff Greer Assignee: Eric Evans Priority: Minor Labels: cql Fix For: 0.8 Attachments: v2-0001-CASSANDRA-2488-teach-cqlsh-to-ignore-comments.txt Commented-out lines that end in a semicolon cause an error. Examples: cqlsh -- CREATE KEYSPACE ELE WITH replication_factor = 3 AND strategy_class = SimpleStrategy AND strategy_options:replication_factor=3; Bad Request: line 0:-1 no viable alternative at input 'EOF' cqlsh -- CREATE KEYSPACE ELE WITH replication_factor = 3 AND strategy_class = SimpleStrategy AND strategy_options:replication_factor=3 ... ... ... ; Bad Request: line 2:0 no viable alternative at input ';' cqlsh -- ; Bad Request: line 0:-1 no viable alternative at input 'EOF' cqlsh --; Bad Request: line 0:-1 no viable alternative at input 'EOF' As long as there's a line with valid CQL before the semicolon, things work fine though. I'm pretty sure the problem is on line 75 of cqlsh: if not line.endswith(;): self.set_prompt(Shell.continue_prompt) return None A quick workaround would be to kill the pretty continue prompt. A more involved fix would detect whether or not the semicolon was in a comment. This is harder than it sounds, since /* and */ allow multi-line comments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2507) Python CQL driver does not decode most values
[
https://issues.apache.org/jira/browse/CASSANDRA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-2507:
---
Attachment: 2507.txt
Attached patch fixes the issue by:
1. Not creating a new cursor for every line of CQL.
2. Updating the driver's view of the schema after DDL statements instead of
before them.
Python CQL driver does not decode most values
-
Key: CASSANDRA-2507
URL: https://issues.apache.org/jira/browse/CASSANDRA-2507
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 0.8
Reporter: Eric Evans
Assignee: Tyler Hobbs
Labels: cql
Fix For: 0.8
Attachments: 2507.txt, repro.cql
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
_Note: requires the patch from CASSANDRA-2505 to be applied_
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything
but strings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095183 - in /cassandra/branches/cassandra-0.8/drivers/py: cql/cursor.py cql/decoders.py cqlsh
Author: jbellis
Date: Tue Apr 19 20:02:16 2011
New Revision: 1095183
URL: http://svn.apache.org/viewvc?rev=1095183view=rev
Log:
cqlsh fixes
patch by thobbs; reviewed by jbellis for CASSANDRA-2507
Modified:
cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py
cassandra/branches/cassandra-0.8/drivers/py/cql/decoders.py
cassandra/branches/cassandra-0.8/drivers/py/cqlsh
Modified: cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py?rev=1095183r1=1095182r2=1095183view=diff
==
--- cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py (original)
+++ cassandra/branches/cassandra-0.8/drivers/py/cql/cursor.py Tue Apr 19
20:02:16 2011
@@ -62,6 +62,7 @@ class Cursor:
def prepare(self, query, params):
prepared_query = prepare(query, params)
+self._schema_update_needed = False
# Snag the keyspace or column family and stash it for later use in
# decoding columns. These regexes don't match every query, but the
@@ -78,9 +79,7 @@ class Cursor:
# If this is a CREATE, then refresh the schema for decoding purposes.
match = Cursor._ddl_re.match(prepared_query)
if match:
-if isinstance(self.decoder, SchemaDecoder):
-self.decoder.schema = self.__get_schema()
-
+self._schema_update_needed = True
return prepared_query
def __get_schema(self):
@@ -110,6 +109,9 @@ class Cursor:
def execute(self, cql_query, params={}):
self.__checksock()
+self.rs_idx = 0
+self.rowcount = 0
+self.description = None
try:
prepared_q = self.prepare(cql_query, params)
except KeyError, e:
@@ -132,6 +134,9 @@ class Cursor:
except TApplicationException, tapp:
raise cql.InternalError(Internal application error)
+if self._schema_update_needed and isinstance(self.decoder,
SchemaDecoder):
+self.decoder.schema = self.__get_schema()
+
if response.type == CqlResultType.ROWS:
self.result = ResultSet(response.rows,
self._query_ks,
Modified: cassandra/branches/cassandra-0.8/drivers/py/cql/decoders.py
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cql/decoders.py?rev=1095183r1=1095182r2=1095183view=diff
==
--- cassandra/branches/cassandra-0.8/drivers/py/cql/decoders.py (original)
+++ cassandra/branches/cassandra-0.8/drivers/py/cql/decoders.py Tue Apr 19
20:02:16 2011
@@ -26,9 +26,8 @@ class SchemaDecoder(object):
self.schema = schema
def __get_column_family_def(self, keyspace, column_family):
-if self.schema.has_key(keyspace):
-if self.schema[keyspace].has_key(column_family):
-return self.schema[keyspace][column_family]
+if keyspace in self.schema and column_family in self.schema[keyspace]:
+return self.schema[keyspace][column_family]
return None
def __comparator_for(self, keyspace, column_family):
Modified: cassandra/branches/cassandra-0.8/drivers/py/cqlsh
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cqlsh?rev=1095183r1=1095182r2=1095183view=diff
==
--- cassandra/branches/cassandra-0.8/drivers/py/cqlsh (original)
+++ cassandra/branches/cassandra-0.8/drivers/py/cqlsh Tue Apr 19 20:02:16 2011
@@ -48,12 +48,13 @@ def startswith(words, text):
class Shell(cmd.Cmd):
default_prompt = cqlsh
continue_prompt =...
-
+
def __init__(self, hostname, port, color=False, username=None,
password=None):
cmd.Cmd.__init__(self)
self.conn = cql.connect(hostname, port, user=username,
password=password)
-
+self.cursor = self.conn.cursor()
+
if os.path.exists(HISTORY):
readline.read_history_file(HISTORY)
@@ -112,23 +113,22 @@ class Shell(cmd.Cmd):
if not input.strip(): return
statement = self.get_statement(input)
if not statement: return
-
-cursor = self.conn.cursor()
-cursor.execute(statement)
-
-if isinstance(cursor.result, ResultSet):
-for x in range(cursor.rowcount):
-row = cursor.fetchone()
-self.printout(row[0], BLUE, False)
+
+self.cursor.execute(statement)
+
+if isinstance(self.cursor.result, ResultSet):
+for x in range(self.cursor.rowcount):
+row = self.cursor.fetchone()
+self.printout(repr(row[0]), BLUE, False)
for (i, value) in enumerate(row[1:]):
-name =
[jira] [Updated] (CASSANDRA-2508) missing imports in CQL Python driver
[
https://issues.apache.org/jira/browse/CASSANDRA-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2508:
--
Attachment: 2508.txt
bq. python -c 'from cql import DateFromTicks; DateFromTicks(1)'
fixed
bq. cql.connection is missing an import of AuthenticationRequest from ttypes
fixed
bq. NotSupportedError
changed to builtin NotImplementedError
bq. InternalError
ttypes InternalError should be internal errors on the server; change this to a
no-op (in the case of repeated closes) and ValueError (in the case of
operation-on-closed-handle), which match the behavior of the file class.
bq. marshal.unmarshal_long has a NameError waiting to happen in the form of
unpack
fixed, and also pulled the if out of the unmarshal definition to only execute
once.
missing imports in CQL Python driver
Key: CASSANDRA-2508
URL: https://issues.apache.org/jira/browse/CASSANDRA-2508
Project: Cassandra
Issue Type: Bug
Reporter: Eric Evans
Labels: cql
Fix For: 0.8
Attachments: 2508.txt
Try:
bq. cd drivers/py python -c 'from cql import DateFromTicks;
DateFromTicks(1)'
Also:
{{cql.connection}} is missing an import of {{AuthenticationRequest}} from
{{ttypes}}, and the exceptions {{NotSupportedError}}, and {{InternalError}}.
Also:
{{marshal.unmarshal_long}} has a NameError waiting to happen in the form of
unpack
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2508) missing imports in CQL Python driver
[
https://issues.apache.org/jira/browse/CASSANDRA-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2508:
--
Component/s: Tools
Affects Version/s: 0.8
missing imports in CQL Python driver
Key: CASSANDRA-2508
URL: https://issues.apache.org/jira/browse/CASSANDRA-2508
Project: Cassandra
Issue Type: Bug
Components: Tools
Affects Versions: 0.8
Reporter: Eric Evans
Assignee: Jonathan Ellis
Labels: cql
Fix For: 0.8
Attachments: 2508.txt
Try:
bq. cd drivers/py python -c 'from cql import DateFromTicks;
DateFromTicks(1)'
Also:
{{cql.connection}} is missing an import of {{AuthenticationRequest}} from
{{ttypes}}, and the exceptions {{NotSupportedError}}, and {{InternalError}}.
Also:
{{marshal.unmarshal_long}} has a NameError waiting to happen in the form of
unpack
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-2509) Update py_test to use strategy_options
Update py_test to use strategy_options -- Key: CASSANDRA-2509 URL: https://issues.apache.org/jira/browse/CASSANDRA-2509 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 0.8 Reporter: Robert Jackson KsDef was changed in cassandra.thrift to accept a hash of options as strategy_options. py_test/stress.py needs to be updated with the new method arguments. CASSANDRA-1263 changed the parameters to KsDef. CASSANDRA-2462 fixed this issue in the native Java stress package. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-2509) Update py_test to use strategy_options
[ https://issues.apache.org/jira/browse/CASSANDRA-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021764#comment-13021764 ] Robert Jackson edited comment on CASSANDRA-2509 at 4/19/11 8:21 PM: Attached patch fixes issue with py_test. was (Author: rwjblue): Fixes issue with py_test. Update py_test to use strategy_options -- Key: CASSANDRA-2509 URL: https://issues.apache.org/jira/browse/CASSANDRA-2509 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 0.8 Reporter: Robert Jackson Attachments: 0001-Update-py_stress-to-make-replication_factor-part-of-.patch KsDef was changed in cassandra.thrift to accept a hash of options as strategy_options. py_test/stress.py needs to be updated with the new method arguments. CASSANDRA-1263 changed the parameters to KsDef. CASSANDRA-2462 fixed this issue in the native Java stress package. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095192 - /cassandra/branches/cassandra-0.8/tools/py_stress/stress.py
Author: jbellis
Date: Tue Apr 19 20:25:42 2011
New Revision: 1095192
URL: http://svn.apache.org/viewvc?rev=1095192view=rev
Log:
update stress.py for KsDef replication_factor change
patch by Robert Jackson; reviewed by jbellis for CASSANDRA-2509
Modified:
cassandra/branches/cassandra-0.8/tools/py_stress/stress.py
Modified: cassandra/branches/cassandra-0.8/tools/py_stress/stress.py
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/tools/py_stress/stress.py?rev=1095192r1=1095191r2=1095192view=diff
==
--- cassandra/branches/cassandra-0.8/tools/py_stress/stress.py (original)
+++ cassandra/branches/cassandra-0.8/tools/py_stress/stress.py Tue Apr 19
20:25:42 2011
@@ -185,7 +185,10 @@ def make_keyspaces():
colms = [ColumnDef(name='C1', validation_class='UTF8Type',
index_type=IndexType.KEYS_BITMAP)]
cfams = [CfDef(keyspace='Keyspace1', name='Standard1',
column_metadata=colms),
CfDef(keyspace='Keyspace1', name='Super1', column_type='Super')]
-keyspace = KsDef(name='Keyspace1',
strategy_class='org.apache.cassandra.locator.SimpleStrategy',
replication_factor=options.replication, cf_defs=cfams)
+keyspace = KsDef(name='Keyspace1',
+
strategy_class='org.apache.cassandra.locator.SimpleStrategy',
+ strategy_options={'replication_factor':
str(options.replication)},
+ cf_defs=cfams)
client = get_client(nodes[0], options.port)
client.transport.open()
try:
[jira] [Commented] (CASSANDRA-2508) missing imports in CQL Python driver
[
https://issues.apache.org/jira/browse/CASSANDRA-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021769#comment-13021769
]
Tyler Hobbs commented on CASSANDRA-2508:
Looks good with the exception of changing the exceptions that are raised.
Internal error refers to cql.InternalError here, and PEP 249 outlines its usage
in a way that closely matches the way it was used.
{noformat}
InternalError
Exception raised when the database encounters an internal
error, e.g. the cursor is not valid anymore, the
transaction is out of sync, etc. It must be a subclass of
DatabaseError.
{noformat}
PEP 249 also mentions using NotSupportedError explicitly in reference to
rollback():
{noformat}
NotSupportedError
Exception raised in case a method or database API was used
which is not supported by the database, e.g. requesting a
.rollback() on a connection that does not support
transaction or has transactions turned off. It must be a
subclass of DatabaseError.
{noformat}
I think it should be kept here.
missing imports in CQL Python driver
Key: CASSANDRA-2508
URL: https://issues.apache.org/jira/browse/CASSANDRA-2508
Project: Cassandra
Issue Type: Bug
Components: Tools
Affects Versions: 0.8
Reporter: Eric Evans
Assignee: Jonathan Ellis
Labels: cql
Fix For: 0.8
Attachments: 2508.txt
Try:
bq. cd drivers/py python -c 'from cql import DateFromTicks;
DateFromTicks(1)'
Also:
{{cql.connection}} is missing an import of {{AuthenticationRequest}} from
{{ttypes}}, and the exceptions {{NotSupportedError}}, and {{InternalError}}.
Also:
{{marshal.unmarshal_long}} has a NameError waiting to happen in the form of
unpack
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095205 - in /cassandra/branches/cassandra-0.8/drivers/py/cql: __init__.py connection.py marshal.py
Author: jbellis Date: Tue Apr 19 20:39:46 2011 New Revision: 1095205 URL: http://svn.apache.org/viewvc?rev=1095205view=rev Log: fix imports in python cql driver patch by jbellis; reviewed by thobbs for CASSANDRA-2508 Modified: cassandra/branches/cassandra-0.8/drivers/py/cql/__init__.py cassandra/branches/cassandra-0.8/drivers/py/cql/connection.py cassandra/branches/cassandra-0.8/drivers/py/cql/marshal.py Modified: cassandra/branches/cassandra-0.8/drivers/py/cql/__init__.py URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cql/__init__.py?rev=1095205r1=1095204r2=1095205view=diff == --- cassandra/branches/cassandra-0.8/drivers/py/cql/__init__.py (original) +++ cassandra/branches/cassandra-0.8/drivers/py/cql/__init__.py Tue Apr 19 20:39:46 2011 @@ -17,6 +17,7 @@ import exceptions import datetime +import time import connection import marshal Modified: cassandra/branches/cassandra-0.8/drivers/py/cql/connection.py URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cql/connection.py?rev=1095205r1=1095204r2=1095205view=diff == --- cassandra/branches/cassandra-0.8/drivers/py/cql/connection.py (original) +++ cassandra/branches/cassandra-0.8/drivers/py/cql/connection.py Tue Apr 19 20:39:46 2011 @@ -19,6 +19,7 @@ from cursor import Cursor from cassandra import Cassandra from thrift.transport import TTransport, TSocket from thrift.protocol import TBinaryProtocol +from cql.cassandra.ttypes import AuthenticationRequest class Connection(object): @@ -62,7 +63,7 @@ class Connection(object): def close(self): if not self.open_socket: -raise InternalError(Connection has been closed.) +return self.transport.close() self.open_socket = False @@ -75,9 +76,11 @@ class Connection(object): return def rollback(self): +from cql import NotSupportedError raise NotSupportedError(Rollback functionality not present in Cassandra.) def cursor(self): +from cql import ProgrammingError if not self.open_socket: -raise InternalError(Connection has been closed.) +raise ProgrammingError(Connection has been closed.) return Cursor(self) Modified: cassandra/branches/cassandra-0.8/drivers/py/cql/marshal.py URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/drivers/py/cql/marshal.py?rev=1095205r1=1095204r2=1095205view=diff == --- cassandra/branches/cassandra-0.8/drivers/py/cql/marshal.py (original) +++ cassandra/branches/cassandra-0.8/drivers/py/cql/marshal.py Tue Apr 19 20:39:46 2011 @@ -66,11 +66,12 @@ def unmarshal_utf8(bytestr): def unmarshal_int(bytestr): return decode_bigint(bytestr) -def unmarshal_long(bytestr): -if _have_struct: +if _have_struct: +def unmarshal_long(bytestr): return _long_packer.unpack(bytestr)[0] -else: -return unpack(q, bytestr)[0] +else: +def unmarshal_long(bytestr): +return struct.unpack(q, bytestr)[0] def unmarshal_uuid(bytestr): return UUID(bytes=bytestr)
[jira] [Created] (CASSANDRA-2510) Word count example won't compile
Word count example won't compile Key: CASSANDRA-2510 URL: https://issues.apache.org/jira/browse/CASSANDRA-2510 Project: Cassandra Issue Type: Bug Reporter: Jeremy Hanna Assignee: Jeremy Hanna Priority: Minor On the 0.8 branch, the word count stuff isn't compiling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2510) Word count example won't compile
[ https://issues.apache.org/jira/browse/CASSANDRA-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2510: -- Affects Version/s: 0.8 Fix Version/s: 0.8 Word count example won't compile Key: CASSANDRA-2510 URL: https://issues.apache.org/jira/browse/CASSANDRA-2510 Project: Cassandra Issue Type: Bug Affects Versions: 0.8 Reporter: Jeremy Hanna Assignee: Jeremy Hanna Priority: Minor Labels: hadoop Fix For: 0.8 Attachments: 2510.txt On the 0.8 branch, the word count stuff isn't compiling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-2511) Need to forward merge parts of r1088800 to make the pig CassandraStorage build
Need to forward merge parts of r1088800 to make the pig CassandraStorage build -- Key: CASSANDRA-2511 URL: https://issues.apache.org/jira/browse/CASSANDRA-2511 Project: Cassandra Issue Type: Bug Reporter: Jeremy Hanna Assignee: Jeremy Hanna Parts of revision 1088800 weren't forward merged into 0.8/trunk. So the 0.8/trunk version of CassandraStorage doesn't currently build. Specifically, it needs the decompose method in the AbstractType hierarchy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2508) missing imports in CQL Python driver
[
https://issues.apache.org/jira/browse/CASSANDRA-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021810#comment-13021810
]
Hudson commented on CASSANDRA-2508:
---
Integrated in Cassandra-0.8 #23 (See
[https://hudson.apache.org/hudson/job/Cassandra-0.8/23/])
fix imports in python cql driver
patch by jbellis; reviewed by thobbs for CASSANDRA-2508
missing imports in CQL Python driver
Key: CASSANDRA-2508
URL: https://issues.apache.org/jira/browse/CASSANDRA-2508
Project: Cassandra
Issue Type: Bug
Components: Tools
Affects Versions: 0.8
Reporter: Eric Evans
Assignee: Jonathan Ellis
Labels: cql
Fix For: 0.8
Attachments: 2508.txt
Try:
bq. cd drivers/py python -c 'from cql import DateFromTicks;
DateFromTicks(1)'
Also:
{{cql.connection}} is missing an import of {{AuthenticationRequest}} from
{{ttypes}}, and the exceptions {{NotSupportedError}}, and {{InternalError}}.
Also:
{{marshal.unmarshal_long}} has a NameError waiting to happen in the form of
unpack
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2507) Python CQL driver does not decode most values
[
https://issues.apache.org/jira/browse/CASSANDRA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021811#comment-13021811
]
Hudson commented on CASSANDRA-2507:
---
Integrated in Cassandra-0.8 #23 (See
[https://hudson.apache.org/hudson/job/Cassandra-0.8/23/])
cqlsh fixes
patch by thobbs; reviewed by jbellis for CASSANDRA-2507
Python CQL driver does not decode most values
-
Key: CASSANDRA-2507
URL: https://issues.apache.org/jira/browse/CASSANDRA-2507
Project: Cassandra
Issue Type: Bug
Components: API
Affects Versions: 0.8
Reporter: Eric Evans
Assignee: Tyler Hobbs
Labels: cql
Fix For: 0.8
Attachments: 2507.txt, repro.cql
Most keys, and column name/values are not decoded properly. The attached CQL
input can be used to demonstrate:
_Note: requires the patch from CASSANDRA-2505 to be applied_
{noformat}
$ drivers/py/cqlsh localhost 9170 repro.cql
| '\x00\x00\x00\x00\x00\x00\x00\x01','\x00\x00\x00\x00\x00\x00\x00\x01' |
'\x00\x00\x00\x00\x00\x00\x00\x02','\x00\x00\x00\x00\x00\x00\x00\x02'
e�#j�� |
'e\xe2#\x01j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff','e\xe2#\x02j\xa2\x11\xe0\x00\x00\xfe\x8e\xbe\xea\xd9\xff'
{noformat}
For all practical purposes, this renders the driver useless for everything
but strings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2509) Update py_test to use strategy_options
[ https://issues.apache.org/jira/browse/CASSANDRA-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021809#comment-13021809 ] Hudson commented on CASSANDRA-2509: --- Integrated in Cassandra-0.8 #23 (See [https://hudson.apache.org/hudson/job/Cassandra-0.8/23/]) update stress.py for KsDef replication_factor change patch by Robert Jackson; reviewed by jbellis for CASSANDRA-2509 Update py_test to use strategy_options -- Key: CASSANDRA-2509 URL: https://issues.apache.org/jira/browse/CASSANDRA-2509 Project: Cassandra Issue Type: Bug Components: Tools Affects Versions: 0.8 Reporter: Robert Jackson Assignee: Robert Jackson Fix For: 0.8 Attachments: 0001-Update-py_stress-to-make-replication_factor-part-of-.patch KsDef was changed in cassandra.thrift to accept a hash of options as strategy_options. py_test/stress.py needs to be updated with the new method arguments. CASSANDRA-1263 changed the parameters to KsDef. CASSANDRA-2462 fixed this issue in the native Java stress package. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2511) Need to forward merge parts of r1088800 to make the pig CassandraStorage build
[ https://issues.apache.org/jira/browse/CASSANDRA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hanna updated CASSANDRA-2511: Attachment: 2511.txt Forward merged the parts from CASSANDRA-2387 that hadn't made it in. The only question I had was whether it was worth it to embed a call to decompose in the TimeUUIDType.fromString method. It may not be worth it. Need to forward merge parts of r1088800 to make the pig CassandraStorage build -- Key: CASSANDRA-2511 URL: https://issues.apache.org/jira/browse/CASSANDRA-2511 Project: Cassandra Issue Type: Bug Reporter: Jeremy Hanna Assignee: Jeremy Hanna Labels: hadoop, pig Attachments: 2511.txt Parts of revision 1088800 weren't forward merged into 0.8/trunk. So the 0.8/trunk version of CassandraStorage doesn't currently build. Specifically, it needs the decompose method in the AbstractType hierarchy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2511) Need to forward merge parts of r1088800 to make the pig CassandraStorage build
[ https://issues.apache.org/jira/browse/CASSANDRA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021816#comment-13021816 ] Jeremy Hanna commented on CASSANDRA-2511: - So this makes it so the pig CassandraStorage can compile and run in 0.8. Patch is against 0.8-branch. Need to forward merge parts of r1088800 to make the pig CassandraStorage build -- Key: CASSANDRA-2511 URL: https://issues.apache.org/jira/browse/CASSANDRA-2511 Project: Cassandra Issue Type: Bug Reporter: Jeremy Hanna Assignee: Jeremy Hanna Labels: hadoop, pig Attachments: 2511.txt Parts of revision 1088800 weren't forward merged into 0.8/trunk. So the 0.8/trunk version of CassandraStorage doesn't currently build. Specifically, it needs the decompose method in the AbstractType hierarchy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095223 - /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/
Author: jbellis
Date: Tue Apr 19 21:54:07 2011
New Revision: 1095223
URL: http://svn.apache.org/viewvc?rev=1095223view=rev
Log:
fix merging r1088800 from 0.7
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AsciiType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/BytesType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/IntegerType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/LexicalUUIDType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/LocalByPartionerType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/LongType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/TimeUUIDType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/UTF8Type.java
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractType.java?rev=1095223r1=1095222r2=1095223view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractType.java
(original)
+++
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractType.java
Tue Apr 19 21:54:07 2011
@@ -93,6 +93,8 @@ public abstract class AbstractTypeT im
}
public abstract T compose(ByteBuffer bytes);
+
+public abstract ByteBuffer decompose(T value);
/** get a string representation of a particular type. */
public abstract String toString(T t);
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AsciiType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AsciiType.java?rev=1095223r1=1095222r2=1095223view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AsciiType.java
(original)
+++
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AsciiType.java
Tue Apr 19 21:54:07 2011
@@ -32,6 +32,12 @@ public class AsciiType extends AbstractT
{
public static final AsciiType instance = new AsciiType();
+public static AsciiType getInstance()
+{
+return instance;
+}
+
+
AsciiType() {} // singleton
public String getString(ByteBuffer bytes)
@@ -61,9 +67,14 @@ public class AsciiType extends AbstractT
return getString(bytes);
}
+public ByteBuffer decompose(String value)
+{
+return ByteBufferUtil.bytes(value, Charsets.US_ASCII);
+}
+
public ByteBuffer fromString(String source)
{
-return ByteBufferUtil.bytes(source, Charsets.US_ASCII);
+return decompose(source);
}
public void validate(ByteBuffer bytes) throws MarshalException
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/BytesType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/BytesType.java?rev=1095223r1=1095222r2=1095223view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/BytesType.java
(original)
+++
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/BytesType.java
Tue Apr 19 21:54:07 2011
@@ -30,18 +30,28 @@ public class BytesType extends AbstractT
{
public static final BytesType instance = new BytesType();
+public static BytesType getInstance()
+{
+return instance;
+}
+
BytesType() {} // singleton
public ByteBuffer compose(ByteBuffer bytes)
{
return bytes.duplicate();
}
+
+public ByteBuffer decompose(ByteBuffer value)
+{
+return value;
+}
public int compare(ByteBuffer o1, ByteBuffer o2)
{
return BytesType.bytesCompare(o1, o2);
}
-
+
public static int bytesCompare(ByteBuffer o1, ByteBuffer o2)
{
if(null == o1){
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/IntegerType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/IntegerType.java?rev=1095223r1=1095222r2=1095223view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/IntegerType.java
(original)
+++
[jira] [Updated] (CASSANDRA-2511) Need to forward merge parts of r1088800 to make the pig CassandraStorage build
[ https://issues.apache.org/jira/browse/CASSANDRA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2511: -- Affects Version/s: 0.8 Fix Version/s: 0.8 Need to forward merge parts of r1088800 to make the pig CassandraStorage build -- Key: CASSANDRA-2511 URL: https://issues.apache.org/jira/browse/CASSANDRA-2511 Project: Cassandra Issue Type: Bug Affects Versions: 0.8 Reporter: Jeremy Hanna Assignee: Jeremy Hanna Labels: hadoop, pig Fix For: 0.8 Attachments: 2511.txt Parts of revision 1088800 weren't forward merged into 0.8/trunk. So the 0.8/trunk version of CassandraStorage doesn't currently build. Specifically, it needs the decompose method in the AbstractType hierarchy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2405) should expose 'time since last successful repair' for easier aes monitoring
[ https://issues.apache.org/jira/browse/CASSANDRA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Yaskevich updated CASSANDRA-2405: --- Attachment: CASSANDRA-2405-v2.patch should expose 'time since last successful repair' for easier aes monitoring --- Key: CASSANDRA-2405 URL: https://issues.apache.org/jira/browse/CASSANDRA-2405 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Peter Schuller Assignee: Pavel Yaskevich Priority: Minor Fix For: 0.8.1 Attachments: CASSANDRA-2405-v2.patch, CASSANDRA-2405.patch The practical implementation issues of actually ensuring repair runs is somewhat of an undocumented/untreated issue. One hopefully low hanging fruit would be to at least expose the time since last successful repair for a particular column family, to make it easier to write a correct script to monitor for lack of repair in a non-buggy fashion. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2405) should expose 'time since last successful repair' for easier aes monitoring
[ https://issues.apache.org/jira/browse/CASSANDRA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Yaskevich updated CASSANDRA-2405: --- Attachment: (was: CASSANDRA-2405-v2.patch) should expose 'time since last successful repair' for easier aes monitoring --- Key: CASSANDRA-2405 URL: https://issues.apache.org/jira/browse/CASSANDRA-2405 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Peter Schuller Assignee: Pavel Yaskevich Priority: Minor Fix For: 0.8.1 Attachments: CASSANDRA-2405.patch The practical implementation issues of actually ensuring repair runs is somewhat of an undocumented/untreated issue. One hopefully low hanging fruit would be to at least expose the time since last successful repair for a particular column family, to make it easier to write a correct script to monitor for lack of repair in a non-buggy fashion. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-2512) Updating a column's validation class from AsciiType to UTF8Type does not actually work
Updating a column's validation class from AsciiType to UTF8Type does not
actually work
--
Key: CASSANDRA-2512
URL: https://issues.apache.org/jira/browse/CASSANDRA-2512
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.7.4
Environment: Single Node on MacOSX, installed from 0.7.4 binary .tar
ball.
Reporter: Cathy Daw
Please note this is reproducible on both Cassandra 0.74 and the April 18th
trunk build.
*Reproduction Steps*
{code}
create column family users with comparator = UTF8Type
and column_metadata = [{column_name: password, validation_class: UTF8Type},
{column_name: gender, validation_class: AsciiType}];
update column family users with comparator = UTF8Type
and column_metadata = [{column_name: password, validation_class: UTF8Type}
{column_name: gender, validation_class: UTF8Type}];
{code}
*Before After quitting cassandra-cli: Notice the validation class for the
gender client still shows AsciiType*
{code}
[default@demo] describe keyspace demo;
Keyspace: demo:
Replication Strategy: org.apache.cassandra.locator.NetworkTopologyStrategy
Options: [datacenter1:1]
Column Families:
ColumnFamily: users
Key Validation Class: org.apache.cassandra.db.marshal.BytesType
Default column value validator: org.apache.cassandra.db.marshal.BytesType
Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
Row cache size / save period in seconds: 0.0/0
Key cache size / save period in seconds: 20.0/14400
Memtable thresholds: 0.290624997/62/1440 (millions of
ops/MB/minutes)
GC grace seconds: 864000
Compaction min/max thresholds: 4/32
Read repair chance: 1.0
Replicate on write: false
Built indexes: []
Column Metadata:
Column Name: gender
Validation Class: org.apache.cassandra.db.marshal.AsciiType
Column Name: password
Validation Class: org.apache.cassandra.db.marshal.UTF8Type
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2405) should expose 'time since last successful repair' for easier aes monitoring
[ https://issues.apache.org/jira/browse/CASSANDRA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Yaskevich updated CASSANDRA-2405: --- Attachment: CASSANDRA-2405-v2.patch working branch - trunk, latest commit 1adcd1c52e87a2f59d9006a29fb9476174968a60 should expose 'time since last successful repair' for easier aes monitoring --- Key: CASSANDRA-2405 URL: https://issues.apache.org/jira/browse/CASSANDRA-2405 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Peter Schuller Assignee: Pavel Yaskevich Priority: Minor Fix For: 0.8.1 Attachments: CASSANDRA-2405-v2.patch, CASSANDRA-2405.patch The practical implementation issues of actually ensuring repair runs is somewhat of an undocumented/untreated issue. One hopefully low hanging fruit would be to at least expose the time since last successful repair for a particular column family, to make it easier to write a correct script to monitor for lack of repair in a non-buggy fashion. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2511) Need to forward merge parts of r1088800 to make the pig CassandraStorage build
[ https://issues.apache.org/jira/browse/CASSANDRA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hanna updated CASSANDRA-2511: Attachment: 2511-newer-types.txt The counter type may have an incorrect decompose (in its parent class) but I think the rest should be fine. Sorry about missing these the first time. Need to forward merge parts of r1088800 to make the pig CassandraStorage build -- Key: CASSANDRA-2511 URL: https://issues.apache.org/jira/browse/CASSANDRA-2511 Project: Cassandra Issue Type: Bug Affects Versions: 0.8 Reporter: Jeremy Hanna Assignee: Jeremy Hanna Labels: hadoop, pig Fix For: 0.8 Attachments: 2511-newer-types.txt, 2511.txt Parts of revision 1088800 weren't forward merged into 0.8/trunk. So the 0.8/trunk version of CassandraStorage doesn't currently build. Specifically, it needs the decompose method in the AbstractType hierarchy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail
[
https://issues.apache.org/jira/browse/CASSANDRA-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021869#comment-13021869
]
Jonathan Ellis commented on CASSANDRA-2497:
---
Pavel, can you describe the problem + fix?
CLI: issue with keys being interpreted as hex and causing SET statement to
fail
---
Key: CASSANDRA-2497
URL: https://issues.apache.org/jira/browse/CASSANDRA-2497
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.8
Environment: * Single Node instance on MacOSX
* Nightly Compiled Build from 4/18/2011
* Installed from:
https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/apache-cassandra-2011-04-18_11-02-29-bin.tar.gz
Reporter: Cathy Daw
Assignee: Pavel Yaskevich
Priority: Minor
Fix For: 0.8
Attachments: CASSANDRA-2497.patch
*Original Summary*: Issues with Update Column Family and adding a
key_validation_class
_Changed summary because the issue repros on drop/create. see comment._
*Reproduction Steps*
{code}
create column family users with comparator = UTF8Type
and column_metadata = [{column_name: password, validation_class: UTF8Type}];
update column family users with key_validation_class=UTF8Type;
set users['jsmith']['password']='ch@ngem3';
{code}
*EXPECTED RESULT:* After the UPDATE statement, the SET statement should go
through successfully.
*ACTUAL RESULT:* The SET statement gives the same error message, regardless
of the UPDATE statement:
{code}
org.apache.cassandra.db.marshal.MarshalException: cannot parse 'jsmith' as
hex bytes
{code}
*Output from describe keyspace*
{code}
ColumnFamily: users
Key Validation Class: org.apache.cassandra.db.marshal.UTF8Type
Default column value validator:
org.apache.cassandra.db.marshal.BytesType
Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
Row cache size / save period in seconds: 0.0/0
Key cache size / save period in seconds: 20.0/14400
Memtable thresholds: 0.290624997/62/1440 (millions of
ops/MB/minutes)
GC grace seconds: 864000
Compaction min/max thresholds: 4/32
Read repair chance: 1.0
Replicate on write: false
Built indexes: []
Column Metadata:
Column Name: password
Validation Class: org.apache.cassandra.db.marshal.UTF8Type
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095239 - in /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal: AbstractCommutativeType.java UUIDType.java
Author: jbellis
Date: Wed Apr 20 00:13:02 2011
New Revision: 1095239
URL: http://svn.apache.org/viewvc?rev=1095239view=rev
Log:
add decompose methods to new-since-0.7 AbstractTypes
patch by jbellis
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractCommutativeType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/UUIDType.java
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractCommutativeType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractCommutativeType.java?rev=1095239r1=1095238r2=1095239view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractCommutativeType.java
(original)
+++
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AbstractCommutativeType.java
Wed Apr 20 00:13:02 2011
@@ -24,6 +24,7 @@ import java.nio.ByteBuffer;
import org.apache.cassandra.db.Column;
import org.apache.cassandra.db.context.CounterContext;
+import org.apache.cassandra.utils.ByteBufferUtil;
public abstract class AbstractCommutativeType extends AbstractTypeLong
{
@@ -37,6 +38,11 @@ public abstract class AbstractCommutativ
return CounterContext.instance().total(bytes);
}
+public ByteBuffer decompose(Long value)
+{
+return ByteBufferUtil.bytes(value);
+}
+
/**
* create commutative column
*/
Modified:
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/UUIDType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/UUIDType.java?rev=1095239r1=1095238r2=1095239view=diff
==
---
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/UUIDType.java
(original)
+++
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/UUIDType.java
Wed Apr 20 00:13:02 2011
@@ -204,6 +204,11 @@ public class UUIDType extends AbstractTy
return uuid.toString();
}
+public ByteBuffer decompose(UUID value)
+{
+return ByteBuffer.wrap(UUIDGen.decompose(value));
+}
+
@Override
public ByteBuffer fromString(String source) throws MarshalException
{
[jira] [Created] (CASSANDRA-2513) r/m unnecessary AbstractType getInstance methods
r/m unnecessary AbstractType getInstance methods Key: CASSANDRA-2513 URL: https://issues.apache.org/jira/browse/CASSANDRA-2513 Project: Cassandra Issue Type: Improvement Components: Core, Hadoop Affects Versions: 0.7.5 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.7.5 Attachments: 2513.txt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2513) r/m unnecessary AbstractType getInstance methods
[ https://issues.apache.org/jira/browse/CASSANDRA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2513: -- Attachment: 2513.txt r/m unnecessary AbstractType getInstance methods Key: CASSANDRA-2513 URL: https://issues.apache.org/jira/browse/CASSANDRA-2513 Project: Cassandra Issue Type: Improvement Components: Core, Hadoop Affects Versions: 0.7.5 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.7.5 Attachments: 2513.txt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-2514) batch_mutate operations with CL=LOCAL_QUORUM throw TimeOutException when there aren't sufficient live nodes
batch_mutate operations with CL=LOCAL_QUORUM throw TimeOutException when there aren't sufficient live nodes --- Key: CASSANDRA-2514 URL: https://issues.apache.org/jira/browse/CASSANDRA-2514 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.4 Environment: 1. Cassandra 0.7.4 running on RHEL 5.5 2. 2 DC setup 3. RF = 4 (DC1 = 2, DC2 = 2) 4. CL = LOCAL_QUORUM Reporter: Narendra Sharma Fix For: 0.7.5 We have a 2 DC setup with RF = 4. There are 2 nodes in each DC. Following is the keyspace definition: snip keyspaces: - name: KeyspaceMetadata replica_placement_strategy: org.apache.cassandra.locator.NetworkTopologyStrategy strategy_options: DC1 : 2 DC2 : 2 replication_factor: 4 /snip I shutdown all except one node and waited for the live node to recognize that other nodes are dead. Following is the nodetool ring output on the live node: Address Status State LoadOwnsToken 169579575332184635438912517119426957796 10.17.221.19Down Normal ? 29.20% 49117425183422571410176530597442406739 10.17.221.17Up Normal 81.64 KB4.41% 56615248844645582918169246064691229930 10.16.80.54 Down Normal ? 21.13% 92563519227261352488017033924602789201 10.17.221.18Down Normal ? 45.27% 169579575332184635438912517119426957796 I expect UnavailableException when I send batch_mutate request to node that is up. However, it returned TimeOutException: TimedOutException() at org.apache.cassandra.thrift.Cassandra$batch_mutate_result.read(Cassandra.java:16493) at org.apache.cassandra.thrift.Cassandra$Client.recv_batch_mutate(Cassandra.java:916) at org.apache.cassandra.thrift.Cassandra$Client.batch_mutate(Cassandra.java:890) Following is the cassandra-topology.properties # Cassandra Node IP=Data Center:Rack 10.17.221.17=DC1:RAC1 10.17.221.19=DC1:RAC2 10.17.221.18=DC2:RAC1 10.16.80.54=DC2:RAC2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2514) batch_mutate operations with CL=LOCAL_QUORUM throw TimeOutException when there aren't sufficient live nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021875#comment-13021875 ] Narendra Sharma commented on CASSANDRA-2514: I think the issue is because DatacenterWriteResponseHandler.assureSufficientLiveNodes is not checking for live nodes. DatacenterWriteResponseHandler.assureSufficientLiveNodes works on writeEndpoints. writeEndpoints contains list of the all the endpoints (may be more if there are nodes bootstrapping). I think either writeEndpoints should ignore dead/unreachable nodes or DatacenterWriteResponseHandler.assureSufficientLiveNodes should use hintedEndpoints.keySet() as that contains the live endpoints. I compared the implementation with WriteResponseHandler.assureSufficientLiveNodes and found that it uses hintedEndpoints. I am attaching the patch that works for me. batch_mutate operations with CL=LOCAL_QUORUM throw TimeOutException when there aren't sufficient live nodes --- Key: CASSANDRA-2514 URL: https://issues.apache.org/jira/browse/CASSANDRA-2514 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.4 Environment: 1. Cassandra 0.7.4 running on RHEL 5.5 2. 2 DC setup 3. RF = 4 (DC1 = 2, DC2 = 2) 4. CL = LOCAL_QUORUM Reporter: Narendra Sharma Fix For: 0.7.5 We have a 2 DC setup with RF = 4. There are 2 nodes in each DC. Following is the keyspace definition: snip keyspaces: - name: KeyspaceMetadata replica_placement_strategy: org.apache.cassandra.locator.NetworkTopologyStrategy strategy_options: DC1 : 2 DC2 : 2 replication_factor: 4 /snip I shutdown all except one node and waited for the live node to recognize that other nodes are dead. Following is the nodetool ring output on the live node: Address Status State LoadOwnsToken 169579575332184635438912517119426957796 10.17.221.19Down Normal ? 29.20% 49117425183422571410176530597442406739 10.17.221.17Up Normal 81.64 KB4.41% 56615248844645582918169246064691229930 10.16.80.54 Down Normal ? 21.13% 92563519227261352488017033924602789201 10.17.221.18Down Normal ? 45.27% 169579575332184635438912517119426957796 I expect UnavailableException when I send batch_mutate request to node that is up. However, it returned TimeOutException: TimedOutException() at org.apache.cassandra.thrift.Cassandra$batch_mutate_result.read(Cassandra.java:16493) at org.apache.cassandra.thrift.Cassandra$Client.recv_batch_mutate(Cassandra.java:916) at org.apache.cassandra.thrift.Cassandra$Client.batch_mutate(Cassandra.java:890) Following is the cassandra-topology.properties # Cassandra Node IP=Data Center:Rack 10.17.221.17=DC1:RAC1 10.17.221.19=DC1:RAC2 10.17.221.18=DC2:RAC1 10.16.80.54=DC2:RAC2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2514) batch_mutate operations with CL=LOCAL_QUORUM throw TimeOutException when there aren't sufficient live nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Narendra Sharma updated CASSANDRA-2514: --- Attachment: CASSANDRA-2514.patch Use hintedEndpoints instead of writeEndpoints to work on live endpoints only. batch_mutate operations with CL=LOCAL_QUORUM throw TimeOutException when there aren't sufficient live nodes --- Key: CASSANDRA-2514 URL: https://issues.apache.org/jira/browse/CASSANDRA-2514 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.4 Environment: 1. Cassandra 0.7.4 running on RHEL 5.5 2. 2 DC setup 3. RF = 4 (DC1 = 2, DC2 = 2) 4. CL = LOCAL_QUORUM Reporter: Narendra Sharma Fix For: 0.7.5 Attachments: CASSANDRA-2514.patch We have a 2 DC setup with RF = 4. There are 2 nodes in each DC. Following is the keyspace definition: snip keyspaces: - name: KeyspaceMetadata replica_placement_strategy: org.apache.cassandra.locator.NetworkTopologyStrategy strategy_options: DC1 : 2 DC2 : 2 replication_factor: 4 /snip I shutdown all except one node and waited for the live node to recognize that other nodes are dead. Following is the nodetool ring output on the live node: Address Status State LoadOwnsToken 169579575332184635438912517119426957796 10.17.221.19Down Normal ? 29.20% 49117425183422571410176530597442406739 10.17.221.17Up Normal 81.64 KB4.41% 56615248844645582918169246064691229930 10.16.80.54 Down Normal ? 21.13% 92563519227261352488017033924602789201 10.17.221.18Down Normal ? 45.27% 169579575332184635438912517119426957796 I expect UnavailableException when I send batch_mutate request to node that is up. However, it returned TimeOutException: TimedOutException() at org.apache.cassandra.thrift.Cassandra$batch_mutate_result.read(Cassandra.java:16493) at org.apache.cassandra.thrift.Cassandra$Client.recv_batch_mutate(Cassandra.java:916) at org.apache.cassandra.thrift.Cassandra$Client.batch_mutate(Cassandra.java:890) Following is the cassandra-topology.properties # Cassandra Node IP=Data Center:Rack 10.17.221.17=DC1:RAC1 10.17.221.19=DC1:RAC2 10.17.221.18=DC2:RAC1 10.16.80.54=DC2:RAC2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-2515) Error starting a cassandra 0.8 cluster using the config file from an existing 0.74 cluster upgrade scenario
Error starting a cassandra 0.8 cluster using the config file from an existing
0.74 cluster upgrade scenario
-
Key: CASSANDRA-2515
URL: https://issues.apache.org/jira/browse/CASSANDRA-2515
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.8
Environment: 3-node Centos 5.5 cluster on rackspace
Reporter: Cathy Daw
Priority: Trivial
This is probably just a documentation bug, but very frequently I will see users
perform this same action when upgrading a cluster.
*Reproduction Steps*
* Install a 3 node 0.74 cassandra cluster
* Edit cassandra.yaml for each cluster
* Start 0.74 do some stuff, shut it down.
* Install 0.8 on the same cluster, but a different directory
* Copy the cassandra.yaml from the 0.74 cluster to the 0.8 cluster.
* Try to startup the 0.8 cluster
*Error starting an 0.8*
{code}
[cassandra@cdaw-qa1 bin]$ ./cassandra -f
INFO 00:06:12,875 Logging initialized
INFO 00:06:12,891 Heap size: 510263296/511311872
INFO 00:06:12,893 JNA not found. Native methods will be disabled.
INFO 00:06:12,904 Loading settings from
file:/home/cassandra/apr19/conf/cassandra.yaml
ERROR 00:06:13,041 Fatal configuration error error
Can't construct a java object for
tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create
property=seeds for JavaBean=org.apache.cassandra.config.Config@207f5580; Unable
to find property 'seeds' on class: org.apache.cassandra.config.Config
in reader, line 10, column 1:
cluster_name: 'Test Cluster'
^
at
org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:372)
at
org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:177)
at
org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:136)
at
org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:122)
at org.yaml.snakeyaml.Loader.load(Loader.java:52)
at org.yaml.snakeyaml.Yaml.load(Yaml.java:166)
at
org.apache.cassandra.config.DatabaseDescriptor.clinit(DatabaseDescriptor.java:139)
at
org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:98)
at
org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:314)
at
org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:80)
Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create property=seeds
for JavaBean=org.apache.cassandra.config.Config@207f5580; Unable to find
property 'seeds' on class: org.apache.cassandra.config.Config
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:305)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct(Constructor.java:184)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:370)
... 9 more
Caused by: org.yaml.snakeyaml.error.YAMLException: Unable to find property
'seeds' on class: org.apache.cassandra.config.Config
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.getProperty(Constructor.java:342)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:240)
... 11 more
null; Can't construct a java object for
tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create
property=seeds for JavaBean=org.apache.cassandra.config.Config@207f5580; Unable
to find property 'seeds' on class: org.apache.cassandra.config.Config
Invalid yaml; unable to start server. See log for stacktrace.
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2513) r/m unnecessary AbstractType getInstance methods
[ https://issues.apache.org/jira/browse/CASSANDRA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2513: -- Attachment: 2513.txt r/m unnecessary AbstractType getInstance methods Key: CASSANDRA-2513 URL: https://issues.apache.org/jira/browse/CASSANDRA-2513 Project: Cassandra Issue Type: Improvement Components: Core, Hadoop Affects Versions: 0.7.5 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.7.5 Attachments: 2513.txt, 2513.txt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2515) Error starting a cassandra 0.8 cluster using the config file from an existing 0.74 cluster upgrade scenario
[
https://issues.apache.org/jira/browse/CASSANDRA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cathy Daw updated CASSANDRA-2515:
-
Description:
This is probably just a documentation bug, but very frequently I will see users
perform this same action when upgrading a cluster.
*Reproduction Steps*
* Install a 3 node 0.74 cassandra cluster
* Edit cassandra.yaml for each cluster
* Start 0.74 do some stuff, shut it down.
* Install 0.8 on the same cluster, but a different directory
* Copy the cassandra.yaml from the 0.74 cluster to the 0.8 cluster.
* Try to startup the 0.8 cluster
*Error starting an 0.8*
{code}
[cassandra@cdaw-qa1 bin]$ ./cassandra -f
INFO 00:06:12,875 Logging initialized
INFO 00:06:12,891 Heap size: 510263296/511311872
INFO 00:06:12,893 JNA not found. Native methods will be disabled.
INFO 00:06:12,904 Loading settings from
file:/home/cassandra/apr19/conf/cassandra.yaml
ERROR 00:06:13,041 Fatal configuration error error
Can't construct a java object for
tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create
property=seeds for JavaBean=org.apache.cassandra.config.Config@207f5580; Unable
to find property 'seeds' on class: org.apache.cassandra.config.Config
in reader, line 10, column 1:
cluster_name: 'Test Cluster'
^
at
org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:372)
at
org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:177)
at
org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:136)
at
org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:122)
at org.yaml.snakeyaml.Loader.load(Loader.java:52)
at org.yaml.snakeyaml.Yaml.load(Yaml.java:166)
at
org.apache.cassandra.config.DatabaseDescriptor.clinit(DatabaseDescriptor.java:139)
at
org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:98)
at
org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:314)
at
org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:80)
Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create property=seeds
for JavaBean=org.apache.cassandra.config.Config@207f5580; Unable to find
property 'seeds' on class: org.apache.cassandra.config.Config
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:305)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct(Constructor.java:184)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:370)
... 9 more
Caused by: org.yaml.snakeyaml.error.YAMLException: Unable to find property
'seeds' on class: org.apache.cassandra.config.Config
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.getProperty(Constructor.java:342)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:240)
... 11 more
null; Can't construct a java object for
tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create
property=seeds for JavaBean=org.apache.cassandra.config.Config@207f5580; Unable
to find property 'seeds' on class: org.apache.cassandra.config.Config
Invalid yaml; unable to start server. See log for stacktrace.
{code}
*0.74 cassandra.yaml*
{noformat}
# Addresses of hosts that are deemed contact points.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring. You must change this if you are running
# multiple nodes!
seeds:
- 184.106.199.149
{noformat}
*0.8 cassandra.yaml*
{noformat}
# any class that implements the SeedProvider interface and has a constructor
that takes a MapString, String of
# parameters will do.
seed_provider:
# Addresses of hosts that are deemed contact points.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring. You must change this if you are running
# multiple nodes!
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
# seeds is actually a comma-delimited list of addresses.
- seeds: 184.106.199.149
{noformat}
was:
This is probably just a documentation bug, but very frequently I will see users
perform this same action when upgrading a cluster.
*Reproduction Steps*
* Install a 3 node 0.74 cassandra cluster
* Edit cassandra.yaml for each cluster
* Start 0.74 do some stuff, shut it down.
* Install 0.8 on the same cluster, but a different directory
* Copy the cassandra.yaml from the 0.74 cluster to the 0.8 cluster.
* Try to startup the 0.8 cluster
*Error starting an 0.8*
{code}
[cassandra@cdaw-qa1 bin]$ ./cassandra -f
INFO 00:06:12,875
[jira] [Commented] (CASSANDRA-2514) batch_mutate operations with CL=LOCAL_QUORUM throw TimeOutException when there aren't sufficient live nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021883#comment-13021883 ] Narendra Sharma commented on CASSANDRA-2514: The code to reproduce this issue is a simple batch mutate operation. The operation I performed involved adding 2 columns to a SuperColumn. Let me know if it is not reproducible. I will provide the sample code. batch_mutate operations with CL=LOCAL_QUORUM throw TimeOutException when there aren't sufficient live nodes --- Key: CASSANDRA-2514 URL: https://issues.apache.org/jira/browse/CASSANDRA-2514 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.4 Environment: 1. Cassandra 0.7.4 running on RHEL 5.5 2. 2 DC setup 3. RF = 4 (DC1 = 2, DC2 = 2) 4. CL = LOCAL_QUORUM Reporter: Narendra Sharma Fix For: 0.7.5 Attachments: CASSANDRA-2514.patch We have a 2 DC setup with RF = 4. There are 2 nodes in each DC. Following is the keyspace definition: snip keyspaces: - name: KeyspaceMetadata replica_placement_strategy: org.apache.cassandra.locator.NetworkTopologyStrategy strategy_options: DC1 : 2 DC2 : 2 replication_factor: 4 /snip I shutdown all except one node and waited for the live node to recognize that other nodes are dead. Following is the nodetool ring output on the live node: Address Status State LoadOwnsToken 169579575332184635438912517119426957796 10.17.221.19Down Normal ? 29.20% 49117425183422571410176530597442406739 10.17.221.17Up Normal 81.64 KB4.41% 56615248844645582918169246064691229930 10.16.80.54 Down Normal ? 21.13% 92563519227261352488017033924602789201 10.17.221.18Down Normal ? 45.27% 169579575332184635438912517119426957796 I expect UnavailableException when I send batch_mutate request to node that is up. However, it returned TimeOutException: TimedOutException() at org.apache.cassandra.thrift.Cassandra$batch_mutate_result.read(Cassandra.java:16493) at org.apache.cassandra.thrift.Cassandra$Client.recv_batch_mutate(Cassandra.java:916) at org.apache.cassandra.thrift.Cassandra$Client.batch_mutate(Cassandra.java:890) Following is the cassandra-topology.properties # Cassandra Node IP=Data Center:Rack 10.17.221.17=DC1:RAC1 10.17.221.19=DC1:RAC2 10.17.221.18=DC2:RAC1 10.16.80.54=DC2:RAC2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-2515) Error starting a cassandra 0.8 cluster using the config file from an existing 0.74 cluster upgrade scenario
[
https://issues.apache.org/jira/browse/CASSANDRA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-2515.
---
Resolution: Not A Problem
0.8 isn't supposed to start up w/ a 0.7 config. diff the two sample files to
see what's changed; in this case it's CASSANDRA-1669.
Error starting a cassandra 0.8 cluster using the config file from an existing
0.74 cluster upgrade scenario
-
Key: CASSANDRA-2515
URL: https://issues.apache.org/jira/browse/CASSANDRA-2515
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.8
Environment: 3-node Centos 5.5 cluster on rackspace
Reporter: Cathy Daw
Priority: Trivial
This is probably just a documentation bug, but very frequently I will see
users perform this same action when upgrading a cluster.
*Reproduction Steps*
* Install a 3 node 0.74 cassandra cluster
* Edit cassandra.yaml for each cluster
* Start 0.74 do some stuff, shut it down.
* Install 0.8 on the same cluster, but a different directory
* Copy the cassandra.yaml from the 0.74 cluster to the 0.8 cluster.
* Try to startup the 0.8 cluster
*Error starting an 0.8*
{code}
[cassandra@cdaw-qa1 bin]$ ./cassandra -f
INFO 00:06:12,875 Logging initialized
INFO 00:06:12,891 Heap size: 510263296/511311872
INFO 00:06:12,893 JNA not found. Native methods will be disabled.
INFO 00:06:12,904 Loading settings from
file:/home/cassandra/apr19/conf/cassandra.yaml
ERROR 00:06:13,041 Fatal configuration error error
Can't construct a java object for
tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create
property=seeds for JavaBean=org.apache.cassandra.config.Config@207f5580;
Unable to find property 'seeds' on class: org.apache.cassandra.config.Config
in reader, line 10, column 1:
cluster_name: 'Test Cluster'
^
at
org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:372)
at
org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:177)
at
org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:136)
at
org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:122)
at org.yaml.snakeyaml.Loader.load(Loader.java:52)
at org.yaml.snakeyaml.Yaml.load(Yaml.java:166)
at
org.apache.cassandra.config.DatabaseDescriptor.clinit(DatabaseDescriptor.java:139)
at
org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:98)
at
org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:314)
at
org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:80)
Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create
property=seeds for JavaBean=org.apache.cassandra.config.Config@207f5580;
Unable to find property 'seeds' on class: org.apache.cassandra.config.Config
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:305)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct(Constructor.java:184)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:370)
... 9 more
Caused by: org.yaml.snakeyaml.error.YAMLException: Unable to find property
'seeds' on class: org.apache.cassandra.config.Config
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.getProperty(Constructor.java:342)
at
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:240)
... 11 more
null; Can't construct a java object for
tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create
property=seeds for JavaBean=org.apache.cassandra.config.Config@207f5580;
Unable to find property 'seeds' on class: org.apache.cassandra.config.Config
Invalid yaml; unable to start server. See log for stacktrace.
{code}
*0.74 cassandra.yaml*
{noformat}
# Addresses of hosts that are deemed contact points.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring. You must change this if you are running
# multiple nodes!
seeds:
- 184.106.199.149
{noformat}
*0.8 cassandra.yaml*
{noformat}
# any class that implements the SeedProvider interface and has a constructor
that takes a MapString, String of
# parameters will do.
seed_provider:
# Addresses of hosts that are deemed contact points.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring. You must change this if you are running
# multiple
[jira] [Commented] (CASSANDRA-2499) cassandra-env.sh pattern matching for OpenJDK broken in some cases
[
https://issues.apache.org/jira/browse/CASSANDRA-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021889#comment-13021889
]
Jackson Chung commented on CASSANDRA-2499:
--
chances are the default /bin/sh is linked to dash, please run a ls -al /bin/sh
to confirm
a minor fix could be remove the [[ and add around the variables and values.
-if [[ $java_version != *OpenJDK* ]]
+if [ $java_version != *OpenJDK* ]
a more drastic fix is to update all the /bin/sh with /bin/bash (if desired to
only support on bash)
see ref: https://wiki.ubuntu.com/DashAsBinSh
suggest to be reviewed to make a decision.
cassandra-env.sh pattern matching for OpenJDK broken in some cases
--
Key: CASSANDRA-2499
URL: https://issues.apache.org/jira/browse/CASSANDRA-2499
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.8
Reporter: Tyler Hobbs
Assignee: Eric Evans
Fix For: 0.8
With bash version 4.1.5, the section of cassandra-env that tries to match the
JDK distribution seems to have some kind of syntax error. I get the
following message when running bin/cassandra:
{noformat}
bin/../conf/cassandra-env.sh: 99: [[: not found
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-2499) cassandra-env.sh pattern matching for OpenJDK broken in some cases
[
https://issues.apache.org/jira/browse/CASSANDRA-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021889#comment-13021889
]
Jackson Chung edited comment on CASSANDRA-2499 at 4/20/11 1:11 AM:
---
chances are the default /bin/sh is linked to dash, please run a ls -al /bin/sh
to confirm
a minor fix could be remove the [[ and add around the variables and values.
-if [[ $java_version != \*OpenJDK\* ]]
+if [ $java_version != \*OpenJDK\* ]
a more drastic fix is to update all the /bin/sh with /bin/bash (if desired to
only support on bash)
see ref: https://wiki.ubuntu.com/DashAsBinSh
suggest to be reviewed to make a decision.
was (Author: cywjackson):
chances are the default /bin/sh is linked to dash, please run a ls -al
/bin/sh to confirm
a minor fix could be remove the [[ and add around the variables and values.
-if [[ $java_version != *OpenJDK* ]]
+if [ $java_version != *OpenJDK* ]
a more drastic fix is to update all the /bin/sh with /bin/bash (if desired to
only support on bash)
see ref: https://wiki.ubuntu.com/DashAsBinSh
suggest to be reviewed to make a decision.
cassandra-env.sh pattern matching for OpenJDK broken in some cases
--
Key: CASSANDRA-2499
URL: https://issues.apache.org/jira/browse/CASSANDRA-2499
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.8
Reporter: Tyler Hobbs
Assignee: Eric Evans
Fix For: 0.8
With bash version 4.1.5, the section of cassandra-env that tries to match the
JDK distribution seems to have some kind of syntax error. I get the
following message when running bin/cassandra:
{noformat}
bin/../conf/cassandra-env.sh: 99: [[: not found
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2513) r/m unnecessary AbstractType getInstance methods
[ https://issues.apache.org/jira/browse/CASSANDRA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2513: -- Attachment: 2513.txt r/m unnecessary AbstractType getInstance methods Key: CASSANDRA-2513 URL: https://issues.apache.org/jira/browse/CASSANDRA-2513 Project: Cassandra Issue Type: Improvement Components: Core, Hadoop Affects Versions: 0.7.5 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.7.5 Attachments: 2513.txt, 2513.txt, 2513.txt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r1095250 - in /cassandra/branches/cassandra-0.7: contrib/pig/src/java/org/apache/cassandra/hadoop/pig/ src/java/org/apache/cassandra/db/marshal/ src/java/org/apache/cassandra/utils/
Author: jbellis
Date: Wed Apr 20 01:50:06 2011
New Revision: 1095250
URL: http://svn.apache.org/viewvc?rev=1095250view=rev
Log:
r/m AT.getInstance methods
patch by jbellis; reviewed by jhanna for CASSANDRA-2513
Modified:
cassandra/branches/cassandra-0.7/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/AsciiType.java
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/BytesType.java
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/IntegerType.java
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/LexicalUUIDType.java
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/LongType.java
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/TimeUUIDType.java
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/UTF8Type.java
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/utils/FBUtilities.java
Modified:
cassandra/branches/cassandra-0.7/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java?rev=1095250r1=1095249r2=1095250view=diff
==
---
cassandra/branches/cassandra-0.7/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
(original)
+++
cassandra/branches/cassandra-0.7/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
Wed Apr 20 01:50:06 2011
@@ -179,8 +179,8 @@ public class CassandraStorage extends Lo
AbstractType default_validator = null;
try
{
-comparator = FBUtilities.getInstance(cfDef.comparator_type,
comparator);
-default_validator =
FBUtilities.getInstance(cfDef.default_validation_class, validator);
+comparator = FBUtilities.getComparator(cfDef.comparator_type);
+default_validator =
FBUtilities.getComparator(cfDef.default_validation_class);
}
catch (ConfigurationException e)
{
@@ -202,7 +202,7 @@ public class CassandraStorage extends Lo
AbstractType validator = null;
try
{
-validator =
FBUtilities.getInstance(cd.getValidation_class(), validator);
+validator =
FBUtilities.getComparator(cd.getValidation_class());
validators.put(cd.name, validator);
}
catch (ConfigurationException e)
Modified:
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/AsciiType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/AsciiType.java?rev=1095250r1=1095249r2=1095250view=diff
==
---
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/AsciiType.java
(original)
+++
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/AsciiType.java
Wed Apr 20 01:50:06 2011
@@ -32,11 +32,6 @@ public class AsciiType extends AbstractT
{
public static final AsciiType instance = new AsciiType();
-public static AsciiType getInstance()
-{
-return instance;
-}
-
AsciiType() {} // singleton
public String compose(ByteBuffer bytes)
Modified:
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/BytesType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/BytesType.java?rev=1095250r1=1095249r2=1095250view=diff
==
---
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/BytesType.java
(original)
+++
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/BytesType.java
Wed Apr 20 01:50:06 2011
@@ -29,11 +29,6 @@ public class BytesType extends AbstractT
{
public static final BytesType instance = new BytesType();
-public static BytesType getInstance()
-{
-return instance;
-}
-
BytesType() {} // singleton
public ByteBuffer compose(ByteBuffer bytes)
Modified:
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/IntegerType.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/IntegerType.java?rev=1095250r1=1095249r2=1095250view=diff
==
---
cassandra/branches/cassandra-0.7/src/java/org/apache/cassandra/db/marshal/IntegerType.java
(original)
+++
svn commit: r1095251 - in /cassandra/branches/cassandra-0.8: ./ contrib/ contrib/pig/src/java/org/apache/cassandra/hadoop/pig/ interface/thrift/gen-java/org/apache/cassandra/thrift/ src/java/org/apach
Author: jbellis
Date: Wed Apr 20 01:51:46 2011
New Revision: 1095251
URL: http://svn.apache.org/viewvc?rev=1095251view=rev
Log:
merge from 0.7
Modified:
cassandra/branches/cassandra-0.8/ (props changed)
cassandra/branches/cassandra-0.8/contrib/ (props changed)
cassandra/branches/cassandra-0.8/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java
(props changed)
cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Column.java
(props changed)
cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/InvalidRequestException.java
(props changed)
cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/NotFoundException.java
(props changed)
cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/SuperColumn.java
(props changed)
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/AsciiType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/BytesType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/IntegerType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/LexicalUUIDType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/LongType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/TimeUUIDType.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/marshal/UTF8Type.java
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/utils/FBUtilities.java
Propchange: cassandra/branches/cassandra-0.8/
--
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Apr 20 01:51:46 2011
@@ -1,5 +1,5 @@
/cassandra/branches/cassandra-0.6:922689-1052356,1052358-1053452,1053454,1053456-1081914,1083000
-/cassandra/branches/cassandra-0.7:1026516-1094195,1094604,1094647,1094796,1094809,1094818,1094831
+/cassandra/branches/cassandra-0.7:1026516-1094195,1094604,1094647,1094796,1094809,1094818,1094831,1095250
/cassandra/branches/cassandra-0.7.0:1053690-1055654
/cassandra/tags/cassandra-0.7.0-rc3:1051699-1053689
/cassandra/trunk:1090978-1090979
Propchange: cassandra/branches/cassandra-0.8/contrib/
--
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Apr 20 01:51:46 2011
@@ -1,5 +1,5 @@
/cassandra/branches/cassandra-0.6/contrib:922689-1052356,1052358-1053452,1053454,1053456-1068009
-/cassandra/branches/cassandra-0.7/contrib:1026516-1094195,1094604,1094647,1094796,1094809,1094818,1094831
+/cassandra/branches/cassandra-0.7/contrib:1026516-1094195,1094604,1094647,1094796,1094809,1094818,1094831,1095250
/cassandra/branches/cassandra-0.7.0/contrib:1053690-1055654
/cassandra/tags/cassandra-0.7.0-rc3/contrib:1051699-1053689
/cassandra/trunk/contrib:1090978-1090979
Modified:
cassandra/branches/cassandra-0.8/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java?rev=1095251r1=1095250r2=1095251view=diff
==
---
cassandra/branches/cassandra-0.8/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
(original)
+++
cassandra/branches/cassandra-0.8/contrib/pig/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
Wed Apr 20 01:51:46 2011
@@ -179,8 +179,8 @@ public class CassandraStorage extends Lo
AbstractType default_validator = null;
try
{
-comparator = FBUtilities.getInstance(cfDef.comparator_type,
comparator);
-default_validator =
FBUtilities.getInstance(cfDef.default_validation_class, validator);
+comparator = FBUtilities.getComparator(cfDef.comparator_type);
+default_validator =
FBUtilities.getComparator(cfDef.default_validation_class);
}
catch (ConfigurationException e)
{
@@ -202,7 +202,7 @@ public class CassandraStorage extends Lo
AbstractType validator = null;
try
{
-validator =
FBUtilities.getInstance(cd.getValidation_class(), validator);
+validator =
FBUtilities.getComparator(cd.getValidation_class());
validators.put(cd.name, validator);
}
catch (ConfigurationException e)
Propchange:
cassandra/branches/cassandra-0.8/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java
[jira] [Created] (CASSANDRA-2516) Allow LOCAL_QUORUM, EACH_QUORUM CLs to work w/ any Strategy class
Allow LOCAL_QUORUM, EACH_QUORUM CLs to work w/ any Strategy class - Key: CASSANDRA-2516 URL: https://issues.apache.org/jira/browse/CASSANDRA-2516 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.7.5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2516) Allow LOCAL_QUORUM, EACH_QUORUM CLs to work w/ any Strategy class
[ https://issues.apache.org/jira/browse/CASSANDRA-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2516: -- Attachment: 2516.txt Allow LOCAL_QUORUM, EACH_QUORUM CLs to work w/ any Strategy class - Key: CASSANDRA-2516 URL: https://issues.apache.org/jira/browse/CASSANDRA-2516 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.7.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.7.5 Attachments: 2516.txt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2513) r/m unnecessary AbstractType getInstance methods
[ https://issues.apache.org/jira/browse/CASSANDRA-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021906#comment-13021906 ] Hudson commented on CASSANDRA-2513: --- Integrated in Cassandra-0.7 #449 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/449/]) r/m AT.getInstance methods patch by jbellis; reviewed by jhanna for CASSANDRA-2513 r/m unnecessary AbstractType getInstance methods Key: CASSANDRA-2513 URL: https://issues.apache.org/jira/browse/CASSANDRA-2513 Project: Cassandra Issue Type: Improvement Components: Core, Hadoop Affects Versions: 0.7.5 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.7.5 Attachments: 2513.txt, 2513.txt, 2513.txt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
