[jira] [Commented] (CASSANDRA-4245) Provide a locale/collation-aware text comparator
[
https://issues.apache.org/jira/browse/CASSANDRA-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743616#comment-13743616
]
Sylvain Lebresne commented on CASSANDRA-4245:
-
I'll note that for the comparator itself, this should be pretty simple using
[Collator|http://docs.oracle.com/javase/6/docs/api/java/text/Collator.html].
Comparator can already take arguments, so one could imagine those arguments to
be the ones from
[Locale|http://docs.oracle.com/javase/6/docs/api/java/util/Locale.html] ctor
(we could allow a value-less version that take the current locale but I'm
personally against it as using the system locale is always a crappy idea imo).
There still would be the question of whether we want to add some CQL syntax
shortcut to define such types (something like {{text(local=ES)}} or some
variation), but that can even be left to a followup ticket since even without
it you can use fully qualified comparator names using double quotes anyway.
Provide a locale/collation-aware text comparator
Key: CASSANDRA-4245
URL: https://issues.apache.org/jira/browse/CASSANDRA-4245
Project: Cassandra
Issue Type: New Feature
Reporter: Ertio Lew
Assignee: amorton
Priority: Minor
It is a common use case to use a bunch of entity names as column names then
use the row as a search index, using search by range. For such use cases
others, it is useful to have a UTF8 comparator that provides case insensitive
ordering of columns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5138) Provide a better CQL error when table data does not conform to CQL metadata.
[ https://issues.apache.org/jira/browse/CASSANDRA-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743660#comment-13743660 ] Sylvain Lebresne commented on CASSANDRA-5138: - It is not allowed to insert cells (thrift columns if you will) that do not correspond to a declared CQL3 column no. But that's something that would qualify as wrong from a CQL3 point of view anyway so that does is intentional. Now from your description, it's hard to say if you were doing it wrong or if the added validation is indeed too restrictive, but at least looking quickly at the patch again I don't see anything wrong. Maybe can you give a simple example of what you're trying to do and doesn't work (the CQL3 schema of the CF and and example of insertion that doesn't work with cassandra-cli for instance)? Provide a better CQL error when table data does not conform to CQL metadata. Key: CASSANDRA-5138 URL: https://issues.apache.org/jira/browse/CASSANDRA-5138 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.2.0 Environment: Mac OS X running 1.2 Reporter: Brian ONeill Assignee: Sylvain Lebresne Priority: Minor Fix For: 2.0 Attachments: 5138-2.txt, 5138.txt, northpole.cql When you create a table via CQL, then insert into it via Thrift. If you inadvertently leave out a component of the column name, in CQL you receive a: TSocket read 0 bytes Server-side the following exception is logged: ERROR 15:19:18,016 Error occurred during processing of message. java.lang.ArrayIndexOutOfBoundsException: 3 at org.apache.cassandra.cql3.statements.ColumnGroupMap.add(ColumnGroupMap.java:43) at org.apache.cassandra.cql3.statements.ColumnGroupMap.access$200(ColumnGroupMap.java:31) at org.apache.cassandra.cql3.statements.ColumnGroupMap$Builder.add(ColumnGroupMap.java:138) at org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:805) at org.apache.cassandra.cql3.statements.SelectStatement.processResults(SelectStatement.java:145) at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:134) at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:61) at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:132) at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:140) at org.apache.cassandra.thrift.CassandraServer.execute_cql3_query(CassandraServer.java:1686) at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(Cassandra.java:4074) at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(Cassandra.java:4062) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34) at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:199) 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:680) I'll submit a schema, and steps to reproduce. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5881) Need describe cluster; functionality in nodetool or cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lyuben Todorov updated CASSANDRA-5881: -- Attachment: 5881_v3.patch SP#describeShemaVersion is accessed via JMX, added accessors for the node's partitioner, schema name and snitch to StorageProxy so output in the nodetool isn't full of logger info. Need describe cluster; functionality in nodetool or cqlsh --- Key: CASSANDRA-5881 URL: https://issues.apache.org/jira/browse/CASSANDRA-5881 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Jeremiah Jordan Assignee: Lyuben Todorov Fix For: 1.2.9 Attachments: 5881_draft.patch, 5881.patch, 5881_v3.patch In order to be able to completely get rid of cassandra-cli we still need something like describe cluster; callable from nodetool or cqlsh. Describe cluster is different from just querying the system tables in cqlsh in that it actually contacts each node. Having a command which does that is useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CASSANDRA-5881) Need describe cluster; functionality in nodetool or cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743752#comment-13743752 ] Lyuben Todorov edited comment on CASSANDRA-5881 at 8/19/13 12:07 PM: - SP#describeShemaVersion is accessed via JMX, added accessors for the node's partitioner, schema name and snitch to StorageProxy so output in the nodetool isn't full of logger info. Sample output: https://gist.github.com/lyubent/6268351 was (Author: lyubent): SP#describeShemaVersion is accessed via JMX, added accessors for the node's partitioner, schema name and snitch to StorageProxy so output in the nodetool isn't full of logger info. Need describe cluster; functionality in nodetool or cqlsh --- Key: CASSANDRA-5881 URL: https://issues.apache.org/jira/browse/CASSANDRA-5881 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Jeremiah Jordan Assignee: Lyuben Todorov Fix For: 1.2.9 Attachments: 5881_draft.patch, 5881.patch, 5881_v3.patch In order to be able to completely get rid of cassandra-cli we still need something like describe cluster; callable from nodetool or cqlsh. Describe cluster is different from just querying the system tables in cqlsh in that it actually contacts each node. Having a command which does that is useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-5899) Sends all interface in native protocol notification when rpc_address=0.0.0.0
Sylvain Lebresne created CASSANDRA-5899:
---
Summary: Sends all interface in native protocol notification when
rpc_address=0.0.0.0
Key: CASSANDRA-5899
URL: https://issues.apache.org/jira/browse/CASSANDRA-5899
Project: Cassandra
Issue Type: Bug
Reporter: Sylvain Lebresne
Priority: Minor
Fix For: 2.0
For the native protocol notifications, when we send a new node notification, we
send the rpc_address of that new node. For this to be actually useful, that
address sent should be publicly accessible by the driver it is destined to.
The problem is when rpc_address=0.0.0.0. Currently, we send the listen_address,
which is correct in the sense that we do are bind on it but might not be
accessible by client nodes.
In fact, one of the good reason to use 0.0.0.0 rpc_address would be if you
have a private network for internode communication and another for
client-server communinations, but still want to be able to issue query from the
private network for debugging. In that case, the current behavior to send
listen_address doesn't really help.
So one suggestion would be to instead send all the addresses on which the
(native protocol) server is bound to (which would still leave to the driver the
task to pick the right one, but at least it has something to pick from).
That's relatively trivial to do in practice, but it does require a minor binary
protocol break to return a list instead of just one IP, which is why I'm
tentatively marking this 2.0. Maybe we can shove that tiny change in the final
(in the protocol v2 only)? Povided we agree it's a good idea of course.
Now to be complete, for the same reasons, we would also need to store all the
addresses we are bound to in the peers table. That's also fairly simple and the
backward compatibility story is maybe a tad simpler: we could add a new
{{rpc_addresses}} column that would be a list and deprecate {{rpc_address}} (to
be removed in 2.1 for instance).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5891) Scrub disk footprint needs to be reduced
[ https://issues.apache.org/jira/browse/CASSANDRA-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lyuben Todorov updated CASSANDRA-5891: -- Attachment: 5891.patch Added a -no-snapshot parameter to the nodetool scrub command. When supplied, the parameter tells scrub to skip snapshot creation and saves disk space: The below is for the size of the var/lib/cassandra directory ./nodetool scrub with -no-snapshot: cassandra dir size before scrub: 4.1G, after scrub 4.1G ./nodetool scrub (without -no-snapshot): cassandra dir size before scrub: 4.1G, after scrub 7.1G Scrub disk footprint needs to be reduced Key: CASSANDRA-5891 URL: https://issues.apache.org/jira/browse/CASSANDRA-5891 Project: Cassandra Issue Type: Bug Components: Core Reporter: sankalp kohli Assignee: Lyuben Todorov Priority: Minor Attachments: 5891.patch Currently scrub creates a snapshot at the beginning of the scrub. This causes the disk used to be doubled after the scrub. If the disk utilization is more than 50%, scrub wont work. It would be nice to have an overriding option to disable snapshot. Something like --no-snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5899) Sends all interface in native protocol notification when rpc_address=0.0.0.0
[
https://issues.apache.org/jira/browse/CASSANDRA-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5899:
Fix Version/s: (was: 2.0)
2.1
Sends all interface in native protocol notification when rpc_address=0.0.0.0
Key: CASSANDRA-5899
URL: https://issues.apache.org/jira/browse/CASSANDRA-5899
Project: Cassandra
Issue Type: Bug
Reporter: Sylvain Lebresne
Priority: Minor
Fix For: 2.1
For the native protocol notifications, when we send a new node notification,
we send the rpc_address of that new node. For this to be actually useful,
that address sent should be publicly accessible by the driver it is destined
to.
The problem is when rpc_address=0.0.0.0. Currently, we send the
listen_address, which is correct in the sense that we do are bind on it but
might not be accessible by client nodes.
In fact, one of the good reason to use 0.0.0.0 rpc_address would be if you
have a private network for internode communication and another for
client-server communinations, but still want to be able to issue query from
the private network for debugging. In that case, the current behavior to send
listen_address doesn't really help.
So one suggestion would be to instead send all the addresses on which the
(native protocol) server is bound to (which would still leave to the driver
the task to pick the right one, but at least it has something to pick from).
That's relatively trivial to do in practice, but it does require a minor
binary protocol break to return a list instead of just one IP, which is why
I'm tentatively marking this 2.0. Maybe we can shove that tiny change in the
final (in the protocol v2 only)? Povided we agree it's a good idea of course.
Now to be complete, for the same reasons, we would also need to store all the
addresses we are bound to in the peers table. That's also fairly simple and
the backward compatibility story is maybe a tad simpler: we could add a new
{{rpc_addresses}} column that would be a list and deprecate {{rpc_address}}
(to be removed in 2.1 for instance).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5899) Sends all interface in native protocol notification when rpc_address=0.0.0.0
[
https://issues.apache.org/jira/browse/CASSANDRA-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743864#comment-13743864
]
Sylvain Lebresne commented on CASSANDRA-5899:
-
Actually, we can't easily implement that suggestion. Protocol notifications for
new nodes are not send from the new nodes themselves, so we have no way to
actually retrieve the list of all interfaces the nodes is bound to (same
problem for the peers table). That is, we would have to gossip that list, and
that's probably more than is reasonable to shove in 2.0 at this point. So well,
let me push that to 2.1 and give some more though to that.
Sends all interface in native protocol notification when rpc_address=0.0.0.0
Key: CASSANDRA-5899
URL: https://issues.apache.org/jira/browse/CASSANDRA-5899
Project: Cassandra
Issue Type: Bug
Reporter: Sylvain Lebresne
Priority: Minor
Fix For: 2.0
For the native protocol notifications, when we send a new node notification,
we send the rpc_address of that new node. For this to be actually useful,
that address sent should be publicly accessible by the driver it is destined
to.
The problem is when rpc_address=0.0.0.0. Currently, we send the
listen_address, which is correct in the sense that we do are bind on it but
might not be accessible by client nodes.
In fact, one of the good reason to use 0.0.0.0 rpc_address would be if you
have a private network for internode communication and another for
client-server communinations, but still want to be able to issue query from
the private network for debugging. In that case, the current behavior to send
listen_address doesn't really help.
So one suggestion would be to instead send all the addresses on which the
(native protocol) server is bound to (which would still leave to the driver
the task to pick the right one, but at least it has something to pick from).
That's relatively trivial to do in practice, but it does require a minor
binary protocol break to return a list instead of just one IP, which is why
I'm tentatively marking this 2.0. Maybe we can shove that tiny change in the
final (in the protocol v2 only)? Povided we agree it's a good idea of course.
Now to be complete, for the same reasons, we would also need to store all the
addresses we are bound to in the peers table. That's also fairly simple and
the backward compatibility story is maybe a tad simpler: we could add a new
{{rpc_addresses}} column that would be a list and deprecate {{rpc_address}}
(to be removed in 2.1 for instance).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-5900) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions
J.B. Langston created CASSANDRA-5900: Summary: Setting bloom filter fp chance to 1.0 causes ClassCastExceptions Key: CASSANDRA-5900 URL: https://issues.apache.org/jira/browse/CASSANDRA-5900 Project: Cassandra Issue Type: Bug Components: Core Reporter: J.B. Langston In 1.2, we introduced the ability to turn SSTables off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to one the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5138) Provide a better CQL error when table data does not conform to CQL metadata.
[ https://issues.apache.org/jira/browse/CASSANDRA-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743872#comment-13743872 ] Elvis Pranskevichus commented on CASSANDRA-5138: I understand that columns not declared in CQL3 are supposed to fail validation. The problem is that even _defined_ columns in non-compact tables fail now. Something as simple as CREATE TABLE test ( id text, attr text, value text, PRIMARY KEY (id, attr) ); It is no longer possible to write into value from Thrift, because it's not a part of the clustering key, which is apparently what CFMetadata.columns is populated from and against what the check is done. Provide a better CQL error when table data does not conform to CQL metadata. Key: CASSANDRA-5138 URL: https://issues.apache.org/jira/browse/CASSANDRA-5138 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.2.0 Environment: Mac OS X running 1.2 Reporter: Brian ONeill Assignee: Sylvain Lebresne Priority: Minor Fix For: 2.0 Attachments: 5138-2.txt, 5138.txt, northpole.cql When you create a table via CQL, then insert into it via Thrift. If you inadvertently leave out a component of the column name, in CQL you receive a: TSocket read 0 bytes Server-side the following exception is logged: ERROR 15:19:18,016 Error occurred during processing of message. java.lang.ArrayIndexOutOfBoundsException: 3 at org.apache.cassandra.cql3.statements.ColumnGroupMap.add(ColumnGroupMap.java:43) at org.apache.cassandra.cql3.statements.ColumnGroupMap.access$200(ColumnGroupMap.java:31) at org.apache.cassandra.cql3.statements.ColumnGroupMap$Builder.add(ColumnGroupMap.java:138) at org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:805) at org.apache.cassandra.cql3.statements.SelectStatement.processResults(SelectStatement.java:145) at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:134) at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:61) at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:132) at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:140) at org.apache.cassandra.thrift.CassandraServer.execute_cql3_query(CassandraServer.java:1686) at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(Cassandra.java:4074) at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(Cassandra.java:4062) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34) at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:199) 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:680) I'll submit a schema, and steps to reproduce. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5900) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.B. Langston updated CASSANDRA-5900: - Description: In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to one the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) was: In 1.2, we introduced the ability to turn SSTables off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to one the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions Key: CASSANDRA-5900 URL: https://issues.apache.org/jira/browse/CASSANDRA-5900 Project: Cassandra Issue Type: Bug Components: Core Reporter: J.B. Langston In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to one the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5900) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.B. Langston updated CASSANDRA-5900: - Description: In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to 1.0 the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) was: In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to one the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions Key: CASSANDRA-5900 URL: https://issues.apache.org/jira/browse/CASSANDRA-5900 Project: Cassandra Issue Type: Bug Components: Core Reporter: J.B. Langston In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to 1.0 the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
git commit: Update versions for 2.0.0 RC2 release
Updated Branches: refs/heads/cassandra-2.0.0 1a2208ad1 - 3e516a328 Update versions for 2.0.0 RC2 release Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3e516a32 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3e516a32 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3e516a32 Branch: refs/heads/cassandra-2.0.0 Commit: 3e516a3287606421a3f400e801bb429029b5598c Parents: 1a2208a Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:01:20 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:01:20 2013 +0200 -- build.xml| 2 +- debian/changelog | 8 +++- 2 files changed, 8 insertions(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3e516a32/build.xml -- diff --git a/build.xml b/build.xml index a72adf4..ede74a9 100644 --- a/build.xml +++ b/build.xml @@ -25,7 +25,7 @@ property name=debuglevel value=source,lines,vars/ !-- default version and SCM information -- -property name=base.version value=2.0.0-rc1/ +property name=base.version value=2.0.0-rc2/ property name=scm.connection value=scm:git://git.apache.org/cassandra.git/ property name=scm.developerConnection value=scm:git://git.apache.org/cassandra.git/ property name=scm.url value=http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=tree/ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3e516a32/debian/changelog -- diff --git a/debian/changelog b/debian/changelog index 236f5c2..589930a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,14 @@ +cassandra (2.0.0~rc2) unstable; urgency=low + + * New release candidate + + -- Sylvain Lebresne slebre...@apache.org Mon, 19 Aug 2013 16:58:03 +0200 + cassandra (2.0.0~rc1) unstable; urgency=low * New release candidate - -- Eric Evans eev...@apache.org, 05 Aug 2013 10:11:43 -0500 + -- Eric Evans eev...@apache.org Mon, 05 Aug 2013 10:11:43 -0500 cassandra (2.0.0~beta2) unstable; urgency=low
Git Push Summary
Updated Tags: refs/tags/2.0.0-rc2-tentative [created] 3e516a328
[1/2] git commit: Comment that 0.0.0.0 may confuse some client drivers
Updated Branches: refs/heads/cassandra-2.0.0 3e516a328 - 5bf1fc13f Comment that 0.0.0.0 may confuse some client drivers Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1d5ecab2 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1d5ecab2 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1d5ecab2 Branch: refs/heads/cassandra-2.0.0 Commit: 1d5ecab2faac0718f9f3c89f9e8daab0d37ba863 Parents: 3529ac7 Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:20:32 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:20:32 2013 +0200 -- conf/cassandra.yaml | 12 1 file changed, 8 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d5ecab2/conf/cassandra.yaml -- diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 75ef331..49e9874 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -348,12 +348,16 @@ native_transport_port: 9042 # Whether to start the thrift rpc server. start_rpc: true -# The address to bind the Thrift RPC service to -- clients connect -# here. Unlike ListenAddress above, you _can_ specify 0.0.0.0 here if -# you want Thrift to listen on all interfaces. -# +# The address to bind the Thrift RPC service and native transport +# server -- clients connect here. +# # Leaving this blank has the same effect it does for ListenAddress, # (i.e. it will be based on the configured hostname of the node). +# +# Note that unlike ListenAddress above, it is allowed to specify 0.0.0.0 +# here if you want to listen on all interfaces but is not best practice +# as it is known to confuse the node auto-discovery features of some +# client drivers. rpc_address: localhost # port for Thrift to listen for clients on rpc_port: 9160
git commit: Comment that 0.0.0.0 may confuse some client drivers
Updated Branches: refs/heads/cassandra-1.2 3529ac711 - 1d5ecab2f Comment that 0.0.0.0 may confuse some client drivers Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1d5ecab2 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1d5ecab2 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1d5ecab2 Branch: refs/heads/cassandra-1.2 Commit: 1d5ecab2faac0718f9f3c89f9e8daab0d37ba863 Parents: 3529ac7 Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:20:32 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:20:32 2013 +0200 -- conf/cassandra.yaml | 12 1 file changed, 8 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d5ecab2/conf/cassandra.yaml -- diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 75ef331..49e9874 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -348,12 +348,16 @@ native_transport_port: 9042 # Whether to start the thrift rpc server. start_rpc: true -# The address to bind the Thrift RPC service to -- clients connect -# here. Unlike ListenAddress above, you _can_ specify 0.0.0.0 here if -# you want Thrift to listen on all interfaces. -# +# The address to bind the Thrift RPC service and native transport +# server -- clients connect here. +# # Leaving this blank has the same effect it does for ListenAddress, # (i.e. it will be based on the configured hostname of the node). +# +# Note that unlike ListenAddress above, it is allowed to specify 0.0.0.0 +# here if you want to listen on all interfaces but is not best practice +# as it is known to confuse the node auto-discovery features of some +# client drivers. rpc_address: localhost # port for Thrift to listen for clients on rpc_port: 9160
[2/2] git commit: Merge branch 'cassandra-1.2' into cassandra-2.0.0
Merge branch 'cassandra-1.2' into cassandra-2.0.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5bf1fc13 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5bf1fc13 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/5bf1fc13 Branch: refs/heads/cassandra-2.0.0 Commit: 5bf1fc13fd1d2aaa6f08784c8810558bf1b58ce9 Parents: 3e516a3 1d5ecab Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:21:06 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:21:06 2013 +0200 -- conf/cassandra.yaml | 12 1 file changed, 8 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/5bf1fc13/conf/cassandra.yaml --
[1/4] git commit: Update versions for 2.0.0 RC2 release
Updated Branches: refs/heads/cassandra-2.0 c3993be8b - dc2c0e786 Update versions for 2.0.0 RC2 release Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3e516a32 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3e516a32 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3e516a32 Branch: refs/heads/cassandra-2.0 Commit: 3e516a3287606421a3f400e801bb429029b5598c Parents: 1a2208a Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:01:20 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:01:20 2013 +0200 -- build.xml| 2 +- debian/changelog | 8 +++- 2 files changed, 8 insertions(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3e516a32/build.xml -- diff --git a/build.xml b/build.xml index a72adf4..ede74a9 100644 --- a/build.xml +++ b/build.xml @@ -25,7 +25,7 @@ property name=debuglevel value=source,lines,vars/ !-- default version and SCM information -- -property name=base.version value=2.0.0-rc1/ +property name=base.version value=2.0.0-rc2/ property name=scm.connection value=scm:git://git.apache.org/cassandra.git/ property name=scm.developerConnection value=scm:git://git.apache.org/cassandra.git/ property name=scm.url value=http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=tree/ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3e516a32/debian/changelog -- diff --git a/debian/changelog b/debian/changelog index 236f5c2..589930a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,14 @@ +cassandra (2.0.0~rc2) unstable; urgency=low + + * New release candidate + + -- Sylvain Lebresne slebre...@apache.org Mon, 19 Aug 2013 16:58:03 +0200 + cassandra (2.0.0~rc1) unstable; urgency=low * New release candidate - -- Eric Evans eev...@apache.org, 05 Aug 2013 10:11:43 -0500 + -- Eric Evans eev...@apache.org Mon, 05 Aug 2013 10:11:43 -0500 cassandra (2.0.0~beta2) unstable; urgency=low
[2/4] git commit: Comment that 0.0.0.0 may confuse some client drivers
Comment that 0.0.0.0 may confuse some client drivers Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1d5ecab2 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1d5ecab2 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1d5ecab2 Branch: refs/heads/cassandra-2.0 Commit: 1d5ecab2faac0718f9f3c89f9e8daab0d37ba863 Parents: 3529ac7 Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:20:32 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:20:32 2013 +0200 -- conf/cassandra.yaml | 12 1 file changed, 8 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d5ecab2/conf/cassandra.yaml -- diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 75ef331..49e9874 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -348,12 +348,16 @@ native_transport_port: 9042 # Whether to start the thrift rpc server. start_rpc: true -# The address to bind the Thrift RPC service to -- clients connect -# here. Unlike ListenAddress above, you _can_ specify 0.0.0.0 here if -# you want Thrift to listen on all interfaces. -# +# The address to bind the Thrift RPC service and native transport +# server -- clients connect here. +# # Leaving this blank has the same effect it does for ListenAddress, # (i.e. it will be based on the configured hostname of the node). +# +# Note that unlike ListenAddress above, it is allowed to specify 0.0.0.0 +# here if you want to listen on all interfaces but is not best practice +# as it is known to confuse the node auto-discovery features of some +# client drivers. rpc_address: localhost # port for Thrift to listen for clients on rpc_port: 9160
[3/4] git commit: Merge branch 'cassandra-1.2' into cassandra-2.0.0
Merge branch 'cassandra-1.2' into cassandra-2.0.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5bf1fc13 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5bf1fc13 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/5bf1fc13 Branch: refs/heads/cassandra-2.0 Commit: 5bf1fc13fd1d2aaa6f08784c8810558bf1b58ce9 Parents: 3e516a3 1d5ecab Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:21:06 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:21:06 2013 +0200 -- conf/cassandra.yaml | 12 1 file changed, 8 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/5bf1fc13/conf/cassandra.yaml --
[5/5] git commit: Merge branch 'cassandra-2.0' into trunk
Merge branch 'cassandra-2.0' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/883ed60e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/883ed60e Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/883ed60e Branch: refs/heads/trunk Commit: 883ed60ef40c875b0e83a58c825a5e1bcc6d3c81 Parents: 8de7c1f dc2c0e7 Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:21:50 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:21:50 2013 +0200 -- build.xml | 2 +- conf/cassandra.yaml | 12 debian/changelog| 8 +++- 3 files changed, 16 insertions(+), 6 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/883ed60e/build.xml --
[4/4] git commit: Merge branch 'cassandra-2.0.0' into cassandra-2.0
Merge branch 'cassandra-2.0.0' into cassandra-2.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/dc2c0e78 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dc2c0e78 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dc2c0e78 Branch: refs/heads/cassandra-2.0 Commit: dc2c0e786a6b72134b35c25173bd73b43bef65a1 Parents: c3993be 5bf1fc1 Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:21:31 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:21:31 2013 +0200 -- build.xml | 2 +- conf/cassandra.yaml | 12 debian/changelog| 8 +++- 3 files changed, 16 insertions(+), 6 deletions(-) --
[4/5] git commit: Merge branch 'cassandra-2.0.0' into cassandra-2.0
Merge branch 'cassandra-2.0.0' into cassandra-2.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/dc2c0e78 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dc2c0e78 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dc2c0e78 Branch: refs/heads/trunk Commit: dc2c0e786a6b72134b35c25173bd73b43bef65a1 Parents: c3993be 5bf1fc1 Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:21:31 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:21:31 2013 +0200 -- build.xml | 2 +- conf/cassandra.yaml | 12 debian/changelog| 8 +++- 3 files changed, 16 insertions(+), 6 deletions(-) --
[2/5] git commit: Comment that 0.0.0.0 may confuse some client drivers
Comment that 0.0.0.0 may confuse some client drivers Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1d5ecab2 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1d5ecab2 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1d5ecab2 Branch: refs/heads/trunk Commit: 1d5ecab2faac0718f9f3c89f9e8daab0d37ba863 Parents: 3529ac7 Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:20:32 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:20:32 2013 +0200 -- conf/cassandra.yaml | 12 1 file changed, 8 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d5ecab2/conf/cassandra.yaml -- diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 75ef331..49e9874 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -348,12 +348,16 @@ native_transport_port: 9042 # Whether to start the thrift rpc server. start_rpc: true -# The address to bind the Thrift RPC service to -- clients connect -# here. Unlike ListenAddress above, you _can_ specify 0.0.0.0 here if -# you want Thrift to listen on all interfaces. -# +# The address to bind the Thrift RPC service and native transport +# server -- clients connect here. +# # Leaving this blank has the same effect it does for ListenAddress, # (i.e. it will be based on the configured hostname of the node). +# +# Note that unlike ListenAddress above, it is allowed to specify 0.0.0.0 +# here if you want to listen on all interfaces but is not best practice +# as it is known to confuse the node auto-discovery features of some +# client drivers. rpc_address: localhost # port for Thrift to listen for clients on rpc_port: 9160
[1/5] git commit: Update versions for 2.0.0 RC2 release
Updated Branches: refs/heads/trunk 8de7c1f5d - 883ed60ef Update versions for 2.0.0 RC2 release Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3e516a32 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3e516a32 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3e516a32 Branch: refs/heads/trunk Commit: 3e516a3287606421a3f400e801bb429029b5598c Parents: 1a2208a Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:01:20 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:01:20 2013 +0200 -- build.xml| 2 +- debian/changelog | 8 +++- 2 files changed, 8 insertions(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3e516a32/build.xml -- diff --git a/build.xml b/build.xml index a72adf4..ede74a9 100644 --- a/build.xml +++ b/build.xml @@ -25,7 +25,7 @@ property name=debuglevel value=source,lines,vars/ !-- default version and SCM information -- -property name=base.version value=2.0.0-rc1/ +property name=base.version value=2.0.0-rc2/ property name=scm.connection value=scm:git://git.apache.org/cassandra.git/ property name=scm.developerConnection value=scm:git://git.apache.org/cassandra.git/ property name=scm.url value=http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=tree/ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3e516a32/debian/changelog -- diff --git a/debian/changelog b/debian/changelog index 236f5c2..589930a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,14 @@ +cassandra (2.0.0~rc2) unstable; urgency=low + + * New release candidate + + -- Sylvain Lebresne slebre...@apache.org Mon, 19 Aug 2013 16:58:03 +0200 + cassandra (2.0.0~rc1) unstable; urgency=low * New release candidate - -- Eric Evans eev...@apache.org, 05 Aug 2013 10:11:43 -0500 + -- Eric Evans eev...@apache.org Mon, 05 Aug 2013 10:11:43 -0500 cassandra (2.0.0~beta2) unstable; urgency=low
[3/5] git commit: Merge branch 'cassandra-1.2' into cassandra-2.0.0
Merge branch 'cassandra-1.2' into cassandra-2.0.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5bf1fc13 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5bf1fc13 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/5bf1fc13 Branch: refs/heads/trunk Commit: 5bf1fc13fd1d2aaa6f08784c8810558bf1b58ce9 Parents: 3e516a3 1d5ecab Author: Sylvain Lebresne sylv...@datastax.com Authored: Mon Aug 19 17:21:06 2013 +0200 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Mon Aug 19 17:21:06 2013 +0200 -- conf/cassandra.yaml | 12 1 file changed, 8 insertions(+), 4 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/5bf1fc13/conf/cassandra.yaml --
[jira] [Commented] (CASSANDRA-4131) Integrate Hive support to be in core cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743937#comment-13743937 ] Cyril Scetbon commented on CASSANDRA-4131: -- For the performance issue I suppose it's simply inherent to Hadoop internals which are designed for lot of data and not for a few rows. Integrate Hive support to be in core cassandra -- Key: CASSANDRA-4131 URL: https://issues.apache.org/jira/browse/CASSANDRA-4131 Project: Cassandra Issue Type: Improvement Reporter: Jeremy Hanna Assignee: Edward Capriolo Labels: hadoop, hive The standalone hive support (at https://github.com/riptano/hive) would be great to have in-tree so that people don't have to go out to github to download it and wonder if it's a left-for-dead external shim. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5891) Scrub disk footprint needs to be reduced
[ https://issues.apache.org/jira/browse/CASSANDRA-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5891: -- Reviewer: dbrosius Component/s: (was: Core) Tools Fix Version/s: 1.2.9 Scrub disk footprint needs to be reduced Key: CASSANDRA-5891 URL: https://issues.apache.org/jira/browse/CASSANDRA-5891 Project: Cassandra Issue Type: Bug Components: Tools Reporter: sankalp kohli Assignee: Lyuben Todorov Priority: Minor Fix For: 1.2.9 Attachments: 5891.patch Currently scrub creates a snapshot at the beginning of the scrub. This causes the disk used to be doubled after the scrub. If the disk utilization is more than 50%, scrub wont work. It would be nice to have an overriding option to disable snapshot. Something like --no-snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CASSANDRA-5867) The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection types
[
https://issues.apache.org/jira/browse/CASSANDRA-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742689#comment-13742689
]
Alex Liu edited comment on CASSANDRA-5867 at 8/19/13 6:46 PM:
--
To store data to CQL3 table, we supports the following prepared statements
{code}
List
e.g.
UPDATE users SET top_places = ?
UPDATE users SET top_places = [ 'rivendell', 'rohan' ] WHERE user_id =
'frodo';
UPDATE users SET top_places = ? + top_places
UPDATE users SET top_places = [ 'the shire' ] + top_places WHERE user_id =
'frodo';
UPDATE users SET top_places = top_places - ?;
UPDATE users SET top_places = top_places - ['riddermark'] WHERE user_id =
'frodo';
Set statements are similar to List
Map
UPDATE users SET todo = ?
UPDATE users
SET todo = { '2012-9-24' : 'enter mordor',
'2012-10-2 12:00' : 'throw ring into mount doom' }
WHERE user_id = 'frodo';
The following queries are handled as a regular value instead of tuples
UPDATE users SET top_places[2] = ?
UPDATE users SET top_places[2] = 'riddermark' WHERE user_id = 'frodo';
DELETE top_places[3] FROM users;
DELETE top_places[3] FROM users WHERE user_id = 'frodo';
UPDATE users SET todo[?] = ?
UPDATE users SET todo['2012-10-2 12:10'] = 'die' WHERE user_id = 'frodo';
{code}
The output schema for collections is as following
{code}
(((name, value), (name, value)), (value ... value), (value...value)
If a value of tuple (value...value) is a tuple of (inner_value ...inner_value)
and the first inner_value is the collection type.
it is either set, list or map.
e.g. (value ... value) as (value1, value2, (set, riddermark, tom))
map (value1, value2, (map, (sfo, 12), (ny, 34))
{code}
was (Author: alexliu68):
To store data to CQL3 table, we supports the following prepared statements
{code}
List
e.g.
UPDATE users SET top_places = ?
UPDATE users SET top_places = [ 'rivendell', 'rohan' ] WHERE user_id =
'frodo';
UPDATE users SET top_places = ? + top_places
UPDATE users SET top_places = [ 'the shire' ] + top_places WHERE user_id =
'frodo';
UPDATE users SET top_places[2] = ?
UPDATE users SET top_places[2] = 'riddermark' WHERE user_id = 'frodo';
DELETE top_places[3] FROM users;
DELETE top_places[3] FROM users WHERE user_id = 'frodo';
UPDATE users SET top_places = top_places - ?;
UPDATE users SET top_places = top_places - ['riddermark'] WHERE user_id =
'frodo';
Set statements are similar to Set
Map
UPDATE users SET todo[?] = ?
UPDATE users SET todo['2012-10-2 12:10'] = 'die' WHERE user_id = 'frodo';
UPDATE users SET todo = ?
UPDATE users
SET todo = { '2012-9-24' : 'enter mordor',
'2012-10-2 12:00' : 'throw ring into mount doom' }
WHERE user_id = 'frodo';
{code}
The output schema for collections is as following
{code}
(((name, value), (name, value)), (value ... value), (value...value)
If a value of tuple (value...value) is a tuple of (inner_value ...inner_value)
and the first inner_value is the collection type.
it is either set, list or map.
e.g. (value ... value) as (value1, value2, (set, riddermark, tom))
map (value1, value2, (map, (sfo, 12), (ny, 34))
{code}
The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection
types
-
Key: CASSANDRA-5867
URL: https://issues.apache.org/jira/browse/CASSANDRA-5867
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Jeremy Hanna
Assignee: Alex Liu
Labels: pig
Attachments: 5867-1.2-branch.txt, 5867-2-1.2-branch.txt
The CqlStorage class gets the Pig data type for values from the
AbstractCassandraStorage class, in the getPigType method. If it isn't a
known data type, it makes the value into a ByteArray. Currently there aren't
any cases there for lists, maps, and sets.
https://github.com/apache/cassandra/blob/cassandra-1.2.8/src/java/org/apache/cassandra/hadoop/pig/AbstractCassandraStorage.java#L336
See this describe output from the grunt shell:
{code}
grunt describe listdata ;
listdata: {id: (name: chararray,value: int),alist: (name: chararray,value:
bytearray),amap: (name: chararray,value: bytearray),aset: (name:
chararray,value: bytearray)}
{code}
where the cql data structures had this schema:
{code}
CREATE TABLE alltypes (
id int PRIMARY KEY,
alist listtext,
amap maptext, text,
aset settext
{code}
It turns out that if you cast the map in grunt to a pig map, then it sort of
works, but I don't think we should probably use a pig map. Lists don't
appear to work at all, as there is no Pig analogue.
[jira] [Commented] (CASSANDRA-5867) The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection types
[
https://issues.apache.org/jira/browse/CASSANDRA-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744105#comment-13744105
]
Alex Holmansky commented on CASSANDRA-5867:
---
I am out of the office from 8/19 through 8/21. I will try to respond to your
message as soon as possible after I return on 8/22.
Regards,
Alex Holmansky
Software Architect
Cartera Commerce, Inc.
The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection
types
-
Key: CASSANDRA-5867
URL: https://issues.apache.org/jira/browse/CASSANDRA-5867
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Jeremy Hanna
Assignee: Alex Liu
Labels: pig
Attachments: 5867-1.2-branch.txt, 5867-2-1.2-branch.txt
The CqlStorage class gets the Pig data type for values from the
AbstractCassandraStorage class, in the getPigType method. If it isn't a
known data type, it makes the value into a ByteArray. Currently there aren't
any cases there for lists, maps, and sets.
https://github.com/apache/cassandra/blob/cassandra-1.2.8/src/java/org/apache/cassandra/hadoop/pig/AbstractCassandraStorage.java#L336
See this describe output from the grunt shell:
{code}
grunt describe listdata ;
listdata: {id: (name: chararray,value: int),alist: (name: chararray,value:
bytearray),amap: (name: chararray,value: bytearray),aset: (name:
chararray,value: bytearray)}
{code}
where the cql data structures had this schema:
{code}
CREATE TABLE alltypes (
id int PRIMARY KEY,
alist listtext,
amap maptext, text,
aset settext
{code}
It turns out that if you cast the map in grunt to a pig map, then it sort of
works, but I don't think we should probably use a pig map. Lists don't
appear to work at all, as there is no Pig analogue. I *think* you could
probably just do a UDF to cast these things, but we already have all of the
type information, so we just need to change them to tuples or bags or
whatever.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5898) nodetool cleanup interacting badly with LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744122#comment-13744122
]
Jonathan Ellis commented on CASSANDRA-5898:
---
Does it repro in 1.2 as well?
nodetool cleanup interacting badly with LCS
---
Key: CASSANDRA-5898
URL: https://issues.apache.org/jira/browse/CASSANDRA-5898
Project: Cassandra
Issue Type: Bug
Reporter: Jeremiah Jordan
Assignee: Yuki Morishita
Attachments: system.log
Then run cassandra-stress read, cassandra-stress write and nodetool cleanup
all at the same time, a few times, it can cause overlapping row errors.
{noformat}
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-245-Data.db')
[DecoratedKey(204853724659241194183955214890519, 30303132343830),
DecoratedKey(69227335985728660912035125310473966323, 30393537373332)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-243-Data.db')
[DecoratedKey(217896711032704014921095870827202, 30333635363932),
DecoratedKey(71430242198281555888954138354238066233, 30333035343132)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-213-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-247-Data.db')
[DecoratedKey(71430378028108400200608251408083114019, 30383133313937),
DecoratedKey(142788557025615975974639291059795386925, 30353437373934)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,175 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-249-Data.db')
[DecoratedKey(138495280291659088173025258556445559667, 30313039353935),
DecoratedKey(170139918483433930784261689358244392849, 30313336303439)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-252-Data.db')
[DecoratedKey(142788613459989682219570222310727294191, 30383031333839),
DecoratedKey(17014089091606942020945601475083221, 30333731303535)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:22:28,912 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-271-Data.db')
[DecoratedKey(68545052253582928820015773344685671746, 30303739313938),
DecoratedKey(119320297902762425433209003370359962009, 30373137323238)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-270-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
{noformat}
Steps to repro:
# Run cassandra-stress -Z LeveledCompactionStrategy
# Run nodetool cleanup
# While cleanup is still running, run cassandra-stress -o write and
cassandra-stress -o read at the same time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5900) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5900: -- Attachment: 5900.txt Patch attached. Note that this only affects nodetool cfstats as well as calling the affected method directly; no internal code calls this method. Setting bloom filter fp chance to 1.0 causes ClassCastExceptions Key: CASSANDRA-5900 URL: https://issues.apache.org/jira/browse/CASSANDRA-5900 Project: Cassandra Issue Type: Bug Components: Core Reporter: J.B. Langston Attachments: 5900.txt In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to 1.0 the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5900) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5900: -- Reviewer: yukim Component/s: (was: Core) Tools Priority: Minor (was: Major) Fix Version/s: 1.2.9 Assignee: Jonathan Ellis Setting bloom filter fp chance to 1.0 causes ClassCastExceptions Key: CASSANDRA-5900 URL: https://issues.apache.org/jira/browse/CASSANDRA-5900 Project: Cassandra Issue Type: Bug Components: Tools Reporter: J.B. Langston Assignee: Jonathan Ellis Priority: Minor Fix For: 1.2.9 Attachments: 5900.txt In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to 1.0 the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5898) nodetool cleanup interacting badly with LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744135#comment-13744135
]
Jeremiah Jordan commented on CASSANDRA-5898:
I wasn't able to repro in 1.2. Once difference I noticed was that in 1.1
compactionstats I would see the cleanup and regular compactions running in
concurrently, but I never saw that in 1.2.
nodetool cleanup interacting badly with LCS
---
Key: CASSANDRA-5898
URL: https://issues.apache.org/jira/browse/CASSANDRA-5898
Project: Cassandra
Issue Type: Bug
Reporter: Jeremiah Jordan
Assignee: Yuki Morishita
Attachments: system.log
Then run cassandra-stress read, cassandra-stress write and nodetool cleanup
all at the same time, a few times, it can cause overlapping row errors.
{noformat}
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-245-Data.db')
[DecoratedKey(204853724659241194183955214890519, 30303132343830),
DecoratedKey(69227335985728660912035125310473966323, 30393537373332)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-243-Data.db')
[DecoratedKey(217896711032704014921095870827202, 30333635363932),
DecoratedKey(71430242198281555888954138354238066233, 30333035343132)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-213-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-247-Data.db')
[DecoratedKey(71430378028108400200608251408083114019, 30383133313937),
DecoratedKey(142788557025615975974639291059795386925, 30353437373934)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,175 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-249-Data.db')
[DecoratedKey(138495280291659088173025258556445559667, 30313039353935),
DecoratedKey(170139918483433930784261689358244392849, 30313336303439)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-252-Data.db')
[DecoratedKey(142788613459989682219570222310727294191, 30383031333839),
DecoratedKey(17014089091606942020945601475083221, 30333731303535)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:22:28,912 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-271-Data.db')
[DecoratedKey(68545052253582928820015773344685671746, 30303739313938),
DecoratedKey(119320297902762425433209003370359962009, 30373137323238)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-270-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
{noformat}
Steps to repro:
# Run cassandra-stress -Z LeveledCompactionStrategy
# Run nodetool cleanup
# While cleanup is still running, run cassandra-stress -o write and
cassandra-stress -o read at the same time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Deleted] (CASSANDRA-5867) The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection types
[
https://issues.apache.org/jira/browse/CASSANDRA-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-5867:
Comment: was deleted
(was: I am out of the office from 8/19 through 8/21. I will try to respond to
your message as soon as possible after I return on 8/22.
Regards,
Alex Holmansky
Software Architect
Cartera Commerce, Inc.
)
The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection
types
-
Key: CASSANDRA-5867
URL: https://issues.apache.org/jira/browse/CASSANDRA-5867
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Jeremy Hanna
Assignee: Alex Liu
Labels: pig
Attachments: 5867-1.2-branch.txt, 5867-2-1.2-branch.txt
The CqlStorage class gets the Pig data type for values from the
AbstractCassandraStorage class, in the getPigType method. If it isn't a
known data type, it makes the value into a ByteArray. Currently there aren't
any cases there for lists, maps, and sets.
https://github.com/apache/cassandra/blob/cassandra-1.2.8/src/java/org/apache/cassandra/hadoop/pig/AbstractCassandraStorage.java#L336
See this describe output from the grunt shell:
{code}
grunt describe listdata ;
listdata: {id: (name: chararray,value: int),alist: (name: chararray,value:
bytearray),amap: (name: chararray,value: bytearray),aset: (name:
chararray,value: bytearray)}
{code}
where the cql data structures had this schema:
{code}
CREATE TABLE alltypes (
id int PRIMARY KEY,
alist listtext,
amap maptext, text,
aset settext
{code}
It turns out that if you cast the map in grunt to a pig map, then it sort of
works, but I don't think we should probably use a pig map. Lists don't
appear to work at all, as there is no Pig analogue. I *think* you could
probably just do a UDF to cast these things, but we already have all of the
type information, so we just need to change them to tuples or bags or
whatever.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
sankalp kohli created CASSANDRA-5901: Summary: Bootstrap should also make the data consistent on the new node Key: CASSANDRA-5901 URL: https://issues.apache.org/jira/browse/CASSANDRA-5901 Project: Cassandra Issue Type: Improvement Components: Core Reporter: sankalp kohli Priority: Minor Currently when we are bootstrapping a new node, it might bootstrap from a node which does not have most upto date data. Because of this, we need to run a repair after that. Most people will always run the repair so it would help if we can provide a parameter to bootstrap to run the repair once the bootstrap has finished. It can also stop the node from responding to reads till repair has finished. This could be another param as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5867) The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection types
[
https://issues.apache.org/jira/browse/CASSANDRA-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Liu updated CASSANDRA-5867:
Attachment: 5867-3-1.2-branch.txt
5867-3-1.2-branch.txt is attached to support storing collections to Cassandra
The Pig CqlStorage/AbstractCassandraStorage classes don't handle collection
types
-
Key: CASSANDRA-5867
URL: https://issues.apache.org/jira/browse/CASSANDRA-5867
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Jeremy Hanna
Assignee: Alex Liu
Labels: pig
Attachments: 5867-1.2-branch.txt, 5867-2-1.2-branch.txt,
5867-3-1.2-branch.txt
The CqlStorage class gets the Pig data type for values from the
AbstractCassandraStorage class, in the getPigType method. If it isn't a
known data type, it makes the value into a ByteArray. Currently there aren't
any cases there for lists, maps, and sets.
https://github.com/apache/cassandra/blob/cassandra-1.2.8/src/java/org/apache/cassandra/hadoop/pig/AbstractCassandraStorage.java#L336
See this describe output from the grunt shell:
{code}
grunt describe listdata ;
listdata: {id: (name: chararray,value: int),alist: (name: chararray,value:
bytearray),amap: (name: chararray,value: bytearray),aset: (name:
chararray,value: bytearray)}
{code}
where the cql data structures had this schema:
{code}
CREATE TABLE alltypes (
id int PRIMARY KEY,
alist listtext,
amap maptext, text,
aset settext
{code}
It turns out that if you cast the map in grunt to a pig map, then it sort of
works, but I don't think we should probably use a pig map. Lists don't
appear to work at all, as there is no Pig analogue. I *think* you could
probably just do a UDF to cast these things, but we already have all of the
type information, so we just need to change them to tuples or bags or
whatever.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-5898) nodetool cleanup interacting badly with LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita resolved CASSANDRA-5898.
---
Resolution: Won't Fix
Fix Version/s: 1.2.0
LCS in 1.1 does not check what's compacting(this includes clean up) when
searching for candidates.
This behavior is fixed in CASSANDRA-4310 in 1.2 release.
nodetool cleanup interacting badly with LCS
---
Key: CASSANDRA-5898
URL: https://issues.apache.org/jira/browse/CASSANDRA-5898
Project: Cassandra
Issue Type: Bug
Reporter: Jeremiah Jordan
Assignee: Yuki Morishita
Fix For: 1.2.0
Attachments: system.log
Then run cassandra-stress read, cassandra-stress write and nodetool cleanup
all at the same time, a few times, it can cause overlapping row errors.
{noformat}
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-245-Data.db')
[DecoratedKey(204853724659241194183955214890519, 30303132343830),
DecoratedKey(69227335985728660912035125310473966323, 30393537373332)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-243-Data.db')
[DecoratedKey(217896711032704014921095870827202, 30333635363932),
DecoratedKey(71430242198281555888954138354238066233, 30333035343132)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-213-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-247-Data.db')
[DecoratedKey(71430378028108400200608251408083114019, 30383133313937),
DecoratedKey(142788557025615975974639291059795386925, 30353437373934)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,175 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-249-Data.db')
[DecoratedKey(138495280291659088173025258556445559667, 30313039353935),
DecoratedKey(170139918483433930784261689358244392849, 30313336303439)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-252-Data.db')
[DecoratedKey(142788613459989682219570222310727294191, 30383031333839),
DecoratedKey(17014089091606942020945601475083221, 30333731303535)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:22:28,912 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-271-Data.db')
[DecoratedKey(68545052253582928820015773344685671746, 30303739313938),
DecoratedKey(119320297902762425433209003370359962009, 30373137323238)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-270-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
{noformat}
Steps to repro:
# Run cassandra-stress -Z LeveledCompactionStrategy
# Run nodetool cleanup
# While cleanup is still running, run cassandra-stress -o write and
cassandra-stress -o read at the same time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5898) nodetool cleanup interacting badly with LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744202#comment-13744202
]
Jeremiah Jordan commented on CASSANDRA-5898:
Just to clarify, when this does occur, it just means some data gets sent back
to L0, and there is not a time incorrect data will be returned. Correct?
nodetool cleanup interacting badly with LCS
---
Key: CASSANDRA-5898
URL: https://issues.apache.org/jira/browse/CASSANDRA-5898
Project: Cassandra
Issue Type: Bug
Reporter: Jeremiah Jordan
Assignee: Yuki Morishita
Fix For: 1.2.0
Attachments: system.log
Then run cassandra-stress read, cassandra-stress write and nodetool cleanup
all at the same time, a few times, it can cause overlapping row errors.
{noformat}
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-245-Data.db')
[DecoratedKey(204853724659241194183955214890519, 30303132343830),
DecoratedKey(69227335985728660912035125310473966323, 30393537373332)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-243-Data.db')
[DecoratedKey(217896711032704014921095870827202, 30333635363932),
DecoratedKey(71430242198281555888954138354238066233, 30333035343132)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-213-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-247-Data.db')
[DecoratedKey(71430378028108400200608251408083114019, 30383133313937),
DecoratedKey(142788557025615975974639291059795386925, 30353437373934)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,175 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-249-Data.db')
[DecoratedKey(138495280291659088173025258556445559667, 30313039353935),
DecoratedKey(170139918483433930784261689358244392849, 30313336303439)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-252-Data.db')
[DecoratedKey(142788613459989682219570222310727294191, 30383031333839),
DecoratedKey(17014089091606942020945601475083221, 30333731303535)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:22:28,912 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-271-Data.db')
[DecoratedKey(68545052253582928820015773344685671746, 30303739313938),
DecoratedKey(119320297902762425433209003370359962009, 30373137323238)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-270-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
{noformat}
Steps to repro:
# Run cassandra-stress -Z LeveledCompactionStrategy
# Run nodetool cleanup
# While cleanup is still running, run cassandra-stress -o write and
cassandra-stress -o read at the same time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5900) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744206#comment-13744206 ] Yuki Morishita commented on CASSANDRA-5900: --- +1 Setting bloom filter fp chance to 1.0 causes ClassCastExceptions Key: CASSANDRA-5900 URL: https://issues.apache.org/jira/browse/CASSANDRA-5900 Project: Cassandra Issue Type: Bug Components: Tools Reporter: J.B. Langston Assignee: Jonathan Ellis Priority: Minor Fix For: 1.2.9 Attachments: 5900.txt In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to 1.0 the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5898) nodetool cleanup interacting badly with LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744215#comment-13744215
]
Brandon Williams commented on CASSANDRA-5898:
-
Correct.
nodetool cleanup interacting badly with LCS
---
Key: CASSANDRA-5898
URL: https://issues.apache.org/jira/browse/CASSANDRA-5898
Project: Cassandra
Issue Type: Bug
Reporter: Jeremiah Jordan
Assignee: Yuki Morishita
Fix For: 1.2.0
Attachments: system.log
Then run cassandra-stress read, cassandra-stress write and nodetool cleanup
all at the same time, a few times, it can cause overlapping row errors.
{noformat}
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-245-Data.db')
[DecoratedKey(204853724659241194183955214890519, 30303132343830),
DecoratedKey(69227335985728660912035125310473966323, 30393537373332)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-243-Data.db')
[DecoratedKey(217896711032704014921095870827202, 30333635363932),
DecoratedKey(71430242198281555888954138354238066233, 30333035343132)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-213-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-247-Data.db')
[DecoratedKey(71430378028108400200608251408083114019, 30383133313937),
DecoratedKey(142788557025615975974639291059795386925, 30353437373934)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,175 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-249-Data.db')
[DecoratedKey(138495280291659088173025258556445559667, 30313039353935),
DecoratedKey(170139918483433930784261689358244392849, 30313336303439)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-252-Data.db')
[DecoratedKey(142788613459989682219570222310727294191, 30383031333839),
DecoratedKey(17014089091606942020945601475083221, 30333731303535)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:22:28,912 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-271-Data.db')
[DecoratedKey(68545052253582928820015773344685671746, 30303739313938),
DecoratedKey(119320297902762425433209003370359962009, 30373137323238)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-270-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
{noformat}
Steps to repro:
# Run cassandra-stress -Z LeveledCompactionStrategy
# Run nodetool cleanup
# While cleanup is still running, run cassandra-stress -o write and
cassandra-stress -o read at the same time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5898) nodetool cleanup interacting badly with LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744216#comment-13744216
]
Yuki Morishita commented on CASSANDRA-5898:
---
Correct. They are just sent back to L0.
As you can see in the attached log, SSTables sent back are all from clean up
during compaction.
LCS checks overlap at the end, and if SSTables from other operation like
cleanup are added during compaction, that ERROR shows up, but no harm.
nodetool cleanup interacting badly with LCS
---
Key: CASSANDRA-5898
URL: https://issues.apache.org/jira/browse/CASSANDRA-5898
Project: Cassandra
Issue Type: Bug
Reporter: Jeremiah Jordan
Assignee: Yuki Morishita
Fix For: 1.2.0
Attachments: system.log
Then run cassandra-stress read, cassandra-stress write and nodetool cleanup
all at the same time, a few times, it can cause overlapping row errors.
{noformat}
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-245-Data.db')
[DecoratedKey(204853724659241194183955214890519, 30303132343830),
DecoratedKey(69227335985728660912035125310473966323, 30393537373332)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-243-Data.db')
[DecoratedKey(217896711032704014921095870827202, 30333635363932),
DecoratedKey(71430242198281555888954138354238066233, 30333035343132)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,174 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-213-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-247-Data.db')
[DecoratedKey(71430378028108400200608251408083114019, 30383133313937),
DecoratedKey(142788557025615975974639291059795386925, 30353437373934)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:20:26,175 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-249-Data.db')
[DecoratedKey(138495280291659088173025258556445559667, 30313039353935),
DecoratedKey(170139918483433930784261689358244392849, 30313336303439)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-252-Data.db')
[DecoratedKey(142788613459989682219570222310727294191, 30383031333839),
DecoratedKey(17014089091606942020945601475083221, 30333731303535)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
ERROR [CompactionExecutor:3] 2013-08-16 19:22:28,912 LeveledManifest.java
(line 223) At level 1,
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-271-Data.db')
[DecoratedKey(68545052253582928820015773344685671746, 30303739313938),
DecoratedKey(119320297902762425433209003370359962009, 30373137323238)]
overlaps
SSTableReader(path='/raid0/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-hf-270-Data.db')
[DecoratedKey(69231122848869715605691825585281602523, 30303236343834),
DecoratedKey(138494249350583165433071928358975719316, 30393733303134)]. This
is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0. If you
have not yet run scrub, you should do so since you may also have rows
out-of-order within an sstable
{noformat}
Steps to repro:
# Run cassandra-stress -Z LeveledCompactionStrategy
# Run nodetool cleanup
# While cleanup is still running, run cassandra-stress -o write and
cassandra-stress -o read at the same time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[10/10] git commit: Merge branch 'cassandra-2.0' into trunk
Merge branch 'cassandra-2.0' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/88a39006 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/88a39006 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/88a39006 Branch: refs/heads/trunk Commit: 88a390064425171c617b66280a0a5961b234599b Parents: 883ed60 83feb94 Author: Jonathan Ellis jbel...@apache.org Authored: Mon Aug 19 18:04:31 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Mon Aug 19 18:04:31 2013 -0500 -- CHANGES.txt | 5 + src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++ 2 files changed, 7 insertions(+) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/88a39006/CHANGES.txt --
[02/10] git commit: Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter patch by jbellis; reviewed by yukim for CASSANDRA-5900
Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter
patch by jbellis; reviewed by yukim for CASSANDRA-5900
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/bc98886d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/bc98886d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/bc98886d
Branch: refs/heads/cassandra-2.0.0
Commit: bc98886d4bbb15eec28f2e8f059dddbd4785
Parents: 1d5ecab
Author: Jonathan Ellis jbel...@apache.org
Authored: Mon Aug 19 18:01:57 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Aug 19 18:01:57 2013 -0500
--
CHANGES.txt | 1 +
src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++
2 files changed, 3 insertions(+)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/bc98886d/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 60e5cdc..bc3f2c6 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.2.9
+ * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
* migrate 1.1 schema_columnfamilies.key_alias column to key_aliases
(CASSANDRA-5800)
* add --migrate option to sstableupgrade and sstablescrub (CASSANDRA-5831)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/bc98886d/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
--
diff --git a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
index 8efa4f1..06b1739 100644
--- a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
@@ -593,6 +593,8 @@ public class SSTableReader extends SSTable
public long getBloomFilterSerializedSize()
{
+if (bf instanceof AlwaysPresentFilter)
+return 0;
return FilterFactory.serializedSize(bf, descriptor.version.filterType);
}
[07/10] git commit: merge from 1.2
merge from 1.2
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/df9d61c9
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/df9d61c9
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/df9d61c9
Branch: refs/heads/trunk
Commit: df9d61c98ff007e26e9a7dcd793e13e056e696c8
Parents: 5bf1fc1 bc98886
Author: Jonathan Ellis jbel...@apache.org
Authored: Mon Aug 19 18:03:51 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Aug 19 18:03:51 2013 -0500
--
CHANGES.txt | 5 +
src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++
2 files changed, 7 insertions(+)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df9d61c9/CHANGES.txt
--
diff --cc CHANGES.txt
index 5c2b924,bc3f2c6..83966d7
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,29 -1,8 +1,34 @@@
-1.2.9
++2.0.0
++Merged from 1.2:
+ * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
- * migrate 1.1 schema_columnfamilies.key_alias column to key_aliases
- (CASSANDRA-5800)
- * add --migrate option to sstableupgrade and sstablescrub (CASSANDRA-5831)
++
++
+2.0.0-rc2
+ * enable vnodes by default (CASSANDRA-5869)
+ * fix CAS contention timeout (CASSANDRA-5830)
+ * fix HsHa to respect max frame size (CASSANDRA-4573)
+ * Fix (some) 2i on composite components omissions (CASSANDRA-5851)
+ * cqlsh: add DESCRIBE FULL SCHEMA variant (CASSANDRA-5880)
+Merged from 1.2:
+ * Correctly validate sparse composite cells in scrub (CASSANDRA-5855)
+ * Add KeyCacheHitRate metric to CF metrics (CASSANDRA-5868)
+ * cqlsh: add support for multiline comments (CASSANDRA-5798)
+ * Handle CQL3 SELECT duplicate IN restrictions on clustering columns
+ (CASSANDRA-5856)
+
+
+2.0.0-rc1
+ * improve DecimalSerializer performance (CASSANDRA-5837)
+ * fix potential spurious wakeup in AsyncOneResponse (CASSANDRA-5690)
+ * fix schema-related trigger issues (CASSANDRA-5774)
+ * Better validation when accessing CQL3 table from thrift (CASSANDRA-5138)
+ * Fix assertion error during repair (CASSANDRA-5801)
+ * Fix range tombstone bug (CASSANDRA-5805)
+ * DC-local CAS (CASSANDRA-5797)
+ * Add a native_protocol_version column to the system.local table
(CASSANRDA-5819)
+ * Use index_interval from cassandra.yaml when upgraded (CASSANDRA-5822)
+ * Fix buffer underflow on socket close (CASSANDRA-5792)
+Merged from 1.2:
* fix bulk-loading compressed sstables (CASSANDRA-5820)
* (Hadoop) fix quoting in CqlPagingRecordReader and CqlRecordWriter
(CASSANDRA-5824)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df9d61c9/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
--
diff --cc src/java/org/apache/cassandra/io/sstable/SSTableReader.java
index 4a62d85,06b1739..814790a
--- a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
@@@ -590,7 -593,9 +590,9 @@@ public class SSTableReader extends SSTa
public long getBloomFilterSerializedSize()
{
+ if (bf instanceof AlwaysPresentFilter)
+ return 0;
-return FilterFactory.serializedSize(bf,
descriptor.version.filterType);
+return FilterFactory.serializedSize(bf);
}
/**
[08/10] git commit: merge from 2.0.0
merge from 2.0.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/83feb94e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/83feb94e Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/83feb94e Branch: refs/heads/trunk Commit: 83feb94e7e0f2cb0f611b1c7cc306cda5d3ce01c Parents: dc2c0e7 df9d61c Author: Jonathan Ellis jbel...@apache.org Authored: Mon Aug 19 18:04:17 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Mon Aug 19 18:04:17 2013 -0500 -- CHANGES.txt | 5 + src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++ 2 files changed, 7 insertions(+) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/83feb94e/CHANGES.txt -- diff --cc CHANGES.txt index c652961,83966d7..d66f18e --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,13 -1,8 +1,18 @@@ +2.0.1 + * Notify indexer of columns shadowed by range tombstones (CASSANDRA-5614) + * Log Merkle tree stats (CASSANDRA-2698) + * Switch from crc32 to adler32 for compressed sstable checksums (CASSANDRA-5862) + * Improve offheap memcpy performance (CASSANDRA-5884) + * Use a range aware scanner for cleanup (CASSANDRA-2524) + * Cleanup doesn't need to inspect sstables that contain only local data + (CASSANDRA-5722) + + + 2.0.0 + Merged from 1.2: + * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900) + + 2.0.0-rc2 * enable vnodes by default (CASSANDRA-5869) * fix CAS contention timeout (CASSANDRA-5830) http://git-wip-us.apache.org/repos/asf/cassandra/blob/83feb94e/src/java/org/apache/cassandra/io/sstable/SSTableReader.java --
[04/10] git commit: Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter patch by jbellis; reviewed by yukim for CASSANDRA-5900
Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter
patch by jbellis; reviewed by yukim for CASSANDRA-5900
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/bc98886d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/bc98886d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/bc98886d
Branch: refs/heads/trunk
Commit: bc98886d4bbb15eec28f2e8f059dddbd4785
Parents: 1d5ecab
Author: Jonathan Ellis jbel...@apache.org
Authored: Mon Aug 19 18:01:57 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Aug 19 18:01:57 2013 -0500
--
CHANGES.txt | 1 +
src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++
2 files changed, 3 insertions(+)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/bc98886d/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 60e5cdc..bc3f2c6 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.2.9
+ * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
* migrate 1.1 schema_columnfamilies.key_alias column to key_aliases
(CASSANDRA-5800)
* add --migrate option to sstableupgrade and sstablescrub (CASSANDRA-5831)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/bc98886d/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
--
diff --git a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
index 8efa4f1..06b1739 100644
--- a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
@@ -593,6 +593,8 @@ public class SSTableReader extends SSTable
public long getBloomFilterSerializedSize()
{
+if (bf instanceof AlwaysPresentFilter)
+return 0;
return FilterFactory.serializedSize(bf, descriptor.version.filterType);
}
[05/10] git commit: merge from 1.2
merge from 1.2
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/df9d61c9
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/df9d61c9
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/df9d61c9
Branch: refs/heads/cassandra-2.0
Commit: df9d61c98ff007e26e9a7dcd793e13e056e696c8
Parents: 5bf1fc1 bc98886
Author: Jonathan Ellis jbel...@apache.org
Authored: Mon Aug 19 18:03:51 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Aug 19 18:03:51 2013 -0500
--
CHANGES.txt | 5 +
src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++
2 files changed, 7 insertions(+)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df9d61c9/CHANGES.txt
--
diff --cc CHANGES.txt
index 5c2b924,bc3f2c6..83966d7
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,29 -1,8 +1,34 @@@
-1.2.9
++2.0.0
++Merged from 1.2:
+ * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
- * migrate 1.1 schema_columnfamilies.key_alias column to key_aliases
- (CASSANDRA-5800)
- * add --migrate option to sstableupgrade and sstablescrub (CASSANDRA-5831)
++
++
+2.0.0-rc2
+ * enable vnodes by default (CASSANDRA-5869)
+ * fix CAS contention timeout (CASSANDRA-5830)
+ * fix HsHa to respect max frame size (CASSANDRA-4573)
+ * Fix (some) 2i on composite components omissions (CASSANDRA-5851)
+ * cqlsh: add DESCRIBE FULL SCHEMA variant (CASSANDRA-5880)
+Merged from 1.2:
+ * Correctly validate sparse composite cells in scrub (CASSANDRA-5855)
+ * Add KeyCacheHitRate metric to CF metrics (CASSANDRA-5868)
+ * cqlsh: add support for multiline comments (CASSANDRA-5798)
+ * Handle CQL3 SELECT duplicate IN restrictions on clustering columns
+ (CASSANDRA-5856)
+
+
+2.0.0-rc1
+ * improve DecimalSerializer performance (CASSANDRA-5837)
+ * fix potential spurious wakeup in AsyncOneResponse (CASSANDRA-5690)
+ * fix schema-related trigger issues (CASSANDRA-5774)
+ * Better validation when accessing CQL3 table from thrift (CASSANDRA-5138)
+ * Fix assertion error during repair (CASSANDRA-5801)
+ * Fix range tombstone bug (CASSANDRA-5805)
+ * DC-local CAS (CASSANDRA-5797)
+ * Add a native_protocol_version column to the system.local table
(CASSANRDA-5819)
+ * Use index_interval from cassandra.yaml when upgraded (CASSANDRA-5822)
+ * Fix buffer underflow on socket close (CASSANDRA-5792)
+Merged from 1.2:
* fix bulk-loading compressed sstables (CASSANDRA-5820)
* (Hadoop) fix quoting in CqlPagingRecordReader and CqlRecordWriter
(CASSANDRA-5824)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df9d61c9/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
--
diff --cc src/java/org/apache/cassandra/io/sstable/SSTableReader.java
index 4a62d85,06b1739..814790a
--- a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
@@@ -590,7 -593,9 +590,9 @@@ public class SSTableReader extends SSTa
public long getBloomFilterSerializedSize()
{
+ if (bf instanceof AlwaysPresentFilter)
+ return 0;
-return FilterFactory.serializedSize(bf,
descriptor.version.filterType);
+return FilterFactory.serializedSize(bf);
}
/**
[01/10] git commit: Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter patch by jbellis; reviewed by yukim for CASSANDRA-5900
Updated Branches:
refs/heads/cassandra-1.2 1d5ecab2f - bc98886d4
refs/heads/cassandra-2.0 dc2c0e786 - 83feb94e7
refs/heads/cassandra-2.0.0 5bf1fc13f - df9d61c98
refs/heads/trunk 883ed60ef - 88a390064
Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter
patch by jbellis; reviewed by yukim for CASSANDRA-5900
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/bc98886d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/bc98886d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/bc98886d
Branch: refs/heads/cassandra-1.2
Commit: bc98886d4bbb15eec28f2e8f059dddbd4785
Parents: 1d5ecab
Author: Jonathan Ellis jbel...@apache.org
Authored: Mon Aug 19 18:01:57 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Aug 19 18:01:57 2013 -0500
--
CHANGES.txt | 1 +
src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++
2 files changed, 3 insertions(+)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/bc98886d/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 60e5cdc..bc3f2c6 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.2.9
+ * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
* migrate 1.1 schema_columnfamilies.key_alias column to key_aliases
(CASSANDRA-5800)
* add --migrate option to sstableupgrade and sstablescrub (CASSANDRA-5831)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/bc98886d/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
--
diff --git a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
index 8efa4f1..06b1739 100644
--- a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
@@ -593,6 +593,8 @@ public class SSTableReader extends SSTable
public long getBloomFilterSerializedSize()
{
+if (bf instanceof AlwaysPresentFilter)
+return 0;
return FilterFactory.serializedSize(bf, descriptor.version.filterType);
}
[06/10] git commit: merge from 1.2
merge from 1.2
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/df9d61c9
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/df9d61c9
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/df9d61c9
Branch: refs/heads/cassandra-2.0.0
Commit: df9d61c98ff007e26e9a7dcd793e13e056e696c8
Parents: 5bf1fc1 bc98886
Author: Jonathan Ellis jbel...@apache.org
Authored: Mon Aug 19 18:03:51 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Aug 19 18:03:51 2013 -0500
--
CHANGES.txt | 5 +
src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++
2 files changed, 7 insertions(+)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df9d61c9/CHANGES.txt
--
diff --cc CHANGES.txt
index 5c2b924,bc3f2c6..83966d7
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,29 -1,8 +1,34 @@@
-1.2.9
++2.0.0
++Merged from 1.2:
+ * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
- * migrate 1.1 schema_columnfamilies.key_alias column to key_aliases
- (CASSANDRA-5800)
- * add --migrate option to sstableupgrade and sstablescrub (CASSANDRA-5831)
++
++
+2.0.0-rc2
+ * enable vnodes by default (CASSANDRA-5869)
+ * fix CAS contention timeout (CASSANDRA-5830)
+ * fix HsHa to respect max frame size (CASSANDRA-4573)
+ * Fix (some) 2i on composite components omissions (CASSANDRA-5851)
+ * cqlsh: add DESCRIBE FULL SCHEMA variant (CASSANDRA-5880)
+Merged from 1.2:
+ * Correctly validate sparse composite cells in scrub (CASSANDRA-5855)
+ * Add KeyCacheHitRate metric to CF metrics (CASSANDRA-5868)
+ * cqlsh: add support for multiline comments (CASSANDRA-5798)
+ * Handle CQL3 SELECT duplicate IN restrictions on clustering columns
+ (CASSANDRA-5856)
+
+
+2.0.0-rc1
+ * improve DecimalSerializer performance (CASSANDRA-5837)
+ * fix potential spurious wakeup in AsyncOneResponse (CASSANDRA-5690)
+ * fix schema-related trigger issues (CASSANDRA-5774)
+ * Better validation when accessing CQL3 table from thrift (CASSANDRA-5138)
+ * Fix assertion error during repair (CASSANDRA-5801)
+ * Fix range tombstone bug (CASSANDRA-5805)
+ * DC-local CAS (CASSANDRA-5797)
+ * Add a native_protocol_version column to the system.local table
(CASSANRDA-5819)
+ * Use index_interval from cassandra.yaml when upgraded (CASSANDRA-5822)
+ * Fix buffer underflow on socket close (CASSANDRA-5792)
+Merged from 1.2:
* fix bulk-loading compressed sstables (CASSANDRA-5820)
* (Hadoop) fix quoting in CqlPagingRecordReader and CqlRecordWriter
(CASSANDRA-5824)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df9d61c9/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
--
diff --cc src/java/org/apache/cassandra/io/sstable/SSTableReader.java
index 4a62d85,06b1739..814790a
--- a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
@@@ -590,7 -593,9 +590,9 @@@ public class SSTableReader extends SSTa
public long getBloomFilterSerializedSize()
{
+ if (bf instanceof AlwaysPresentFilter)
+ return 0;
-return FilterFactory.serializedSize(bf,
descriptor.version.filterType);
+return FilterFactory.serializedSize(bf);
}
/**
[09/10] git commit: merge from 2.0.0
merge from 2.0.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/83feb94e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/83feb94e Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/83feb94e Branch: refs/heads/cassandra-2.0 Commit: 83feb94e7e0f2cb0f611b1c7cc306cda5d3ce01c Parents: dc2c0e7 df9d61c Author: Jonathan Ellis jbel...@apache.org Authored: Mon Aug 19 18:04:17 2013 -0500 Committer: Jonathan Ellis jbel...@apache.org Committed: Mon Aug 19 18:04:17 2013 -0500 -- CHANGES.txt | 5 + src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++ 2 files changed, 7 insertions(+) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/83feb94e/CHANGES.txt -- diff --cc CHANGES.txt index c652961,83966d7..d66f18e --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,13 -1,8 +1,18 @@@ +2.0.1 + * Notify indexer of columns shadowed by range tombstones (CASSANDRA-5614) + * Log Merkle tree stats (CASSANDRA-2698) + * Switch from crc32 to adler32 for compressed sstable checksums (CASSANDRA-5862) + * Improve offheap memcpy performance (CASSANDRA-5884) + * Use a range aware scanner for cleanup (CASSANDRA-2524) + * Cleanup doesn't need to inspect sstables that contain only local data + (CASSANDRA-5722) + + + 2.0.0 + Merged from 1.2: + * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900) + + 2.0.0-rc2 * enable vnodes by default (CASSANDRA-5869) * fix CAS contention timeout (CASSANDRA-5830) http://git-wip-us.apache.org/repos/asf/cassandra/blob/83feb94e/src/java/org/apache/cassandra/io/sstable/SSTableReader.java --
[03/10] git commit: Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter patch by jbellis; reviewed by yukim for CASSANDRA-5900
Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter
patch by jbellis; reviewed by yukim for CASSANDRA-5900
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/bc98886d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/bc98886d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/bc98886d
Branch: refs/heads/cassandra-2.0
Commit: bc98886d4bbb15eec28f2e8f059dddbd4785
Parents: 1d5ecab
Author: Jonathan Ellis jbel...@apache.org
Authored: Mon Aug 19 18:01:57 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Aug 19 18:01:57 2013 -0500
--
CHANGES.txt | 1 +
src/java/org/apache/cassandra/io/sstable/SSTableReader.java | 2 ++
2 files changed, 3 insertions(+)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/bc98886d/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 60e5cdc..bc3f2c6 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
1.2.9
+ * Fix getBloomFilterDiskSpaceUsed for AlwaysPresentFilter (CASSANDRA-5900)
* migrate 1.1 schema_columnfamilies.key_alias column to key_aliases
(CASSANDRA-5800)
* add --migrate option to sstableupgrade and sstablescrub (CASSANDRA-5831)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/bc98886d/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
--
diff --git a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
index 8efa4f1..06b1739 100644
--- a/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
@@ -593,6 +593,8 @@ public class SSTableReader extends SSTable
public long getBloomFilterSerializedSize()
{
+if (bf instanceof AlwaysPresentFilter)
+return 0;
return FilterFactory.serializedSize(bf, descriptor.version.filterType);
}
[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744484#comment-13744484 ] Jonathan Ellis commented on CASSANDRA-5901: --- I'm don't think I understand the reasoning here. Cassandra is designed to tolerate individual replicas having temporarily stale data. If a bootstrapped node streams such stale data from an existing replica, the bootstrap operation does not change the staleness! You had stale data pre-bootstrap, and you still do post-bootstrap. So why would you panic-repair the post-bootstrap node but not pre-bootstrap? Bootstrap should also make the data consistent on the new node -- Key: CASSANDRA-5901 URL: https://issues.apache.org/jira/browse/CASSANDRA-5901 Project: Cassandra Issue Type: Improvement Components: Core Reporter: sankalp kohli Priority: Minor Currently when we are bootstrapping a new node, it might bootstrap from a node which does not have most upto date data. Because of this, we need to run a repair after that. Most people will always run the repair so it would help if we can provide a parameter to bootstrap to run the repair once the bootstrap has finished. It can also stop the node from responding to reads till repair has finished. This could be another param as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5900) Setting bloom filter fp chance to 1.0 causes ClassCastExceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744495#comment-13744495 ] Jonathan Ellis commented on CASSANDRA-5900: --- committed Setting bloom filter fp chance to 1.0 causes ClassCastExceptions Key: CASSANDRA-5900 URL: https://issues.apache.org/jira/browse/CASSANDRA-5900 Project: Cassandra Issue Type: Bug Components: Tools Reporter: J.B. Langston Assignee: Jonathan Ellis Priority: Minor Fix For: 1.2.9 Attachments: 5900.txt In 1.2, we introduced the ability to turn bloom filters off completely by setting fp chance to 1.0. It looks like there is a bug with this though. When it's set to 1.0 the following errors occur because AlwaysPresentFilter is not present in the switch statement here at https://github.com/apache/cassandra/blob/cassandra-1.2/src/java/org/apache/cassandra/utils/FilterFactory.java#L91, and we default to Murmur3BloomFilter for an unknown type. Exception in thread main java.lang.ClassCastException: org.apache.cassandra.utils.AlwaysPresentFilter cannot be cast to org.apache.cassandra.utils.Murmur3BloomFilter at org.apache.cassandra.utils.FilterFactory.serializedSize(FilterFactory.java:91) at org.apache.cassandra.io.sstable.SSTableReader.getBloomFilterSerializedSize(SSTableReader.java:531) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:273) at org.apache.cassandra.metrics.ColumnFamilyMetrics$15.value(ColumnFamilyMetrics.java:268) at org.apache.cassandra.db.ColumnFamilyStore.getBloomFilterDiskSpaceUsed(ColumnFamilyStore.java:1825) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744500#comment-13744500 ] sankalp kohli commented on CASSANDRA-5901: -- If you have stale data in one node before replacing another node, now the new node will bootstrap from the node having stale data. This will cause now 2 nodes to have stale data rather than one. And if you replace another node, the third one will also have stale data. You can even lose data this way in extreme cases. Bootstrap should also make the data consistent on the new node -- Key: CASSANDRA-5901 URL: https://issues.apache.org/jira/browse/CASSANDRA-5901 Project: Cassandra Issue Type: Improvement Components: Core Reporter: sankalp kohli Priority: Minor Currently when we are bootstrapping a new node, it might bootstrap from a node which does not have most upto date data. Because of this, we need to run a repair after that. Most people will always run the repair so it would help if we can provide a parameter to bootstrap to run the repair once the bootstrap has finished. It can also stop the node from responding to reads till repair has finished. This could be another param as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744506#comment-13744506 ] Jonathan Ellis commented on CASSANDRA-5901: --- That said, there is a corner case with bootstrap and hints that I've described in CASSANDRA-5902. Bootstrap should also make the data consistent on the new node -- Key: CASSANDRA-5901 URL: https://issues.apache.org/jira/browse/CASSANDRA-5901 Project: Cassandra Issue Type: Improvement Components: Core Reporter: sankalp kohli Priority: Minor Currently when we are bootstrapping a new node, it might bootstrap from a node which does not have most upto date data. Because of this, we need to run a repair after that. Most people will always run the repair so it would help if we can provide a parameter to bootstrap to run the repair once the bootstrap has finished. It can also stop the node from responding to reads till repair has finished. This could be another param as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-5902) Dealing with hints after a topology change
Jonathan Ellis created CASSANDRA-5902: - Summary: Dealing with hints after a topology change Key: CASSANDRA-5902 URL: https://issues.apache.org/jira/browse/CASSANDRA-5902 Project: Cassandra Issue Type: Bug Reporter: Jonathan Ellis Priority: Minor Hints are stored and delivered by destination node id. This allows them to survive IP changes in the target, while making scan all the hints for a given destination an efficient operation. However, we do not detect and handle new node assuming responsibility for the hinted row via bootstrap before it can be delivered. I think we have to take a performance hit in this case -- we need to deliver such a hint to *all* replicas, since we don't know which is the new one. This happens infrequently enough, however -- requiring first the target node to be down to create the hint, then the hint owner to be down long enough for the target to both recover and stream to a new node -- that this should be okay. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744522#comment-13744522 ] sankalp kohli commented on CASSANDRA-5901: -- Hinted Handoff is best effort I guess, giving an option to repair wont hurt and make things easier to replace a node. Bootstrap should also make the data consistent on the new node -- Key: CASSANDRA-5901 URL: https://issues.apache.org/jira/browse/CASSANDRA-5901 Project: Cassandra Issue Type: Improvement Components: Core Reporter: sankalp kohli Priority: Minor Currently when we are bootstrapping a new node, it might bootstrap from a node which does not have most upto date data. Because of this, we need to run a repair after that. Most people will always run the repair so it would help if we can provide a parameter to bootstrap to run the repair once the bootstrap has finished. It can also stop the node from responding to reads till repair has finished. This could be another param as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4536) Ability for CQL3 to list partition keys
[
https://issues.apache.org/jira/browse/CASSANDRA-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-4536:
-
Attachment: 4536.txt
Ability for CQL3 to list partition keys
---
Key: CASSANDRA-4536
URL: https://issues.apache.org/jira/browse/CASSANDRA-4536
Project: Cassandra
Issue Type: New Feature
Components: API
Affects Versions: 1.1.0
Reporter: Jonathan Ellis
Assignee: Aleksey Yeschenko
Priority: Minor
Labels: cql3
Fix For: 2.0.1
Attachments: 4536.txt, cassandra-4536_1.1.0.patch,
cassandra-4536_1.2.2.patch, cassandra-4536_1.2.5.patch
It can be useful to know the set of in-use partition keys (storage engine row
keys). One example given to me was where application data was modeled as a
few 10s of 1000s of wide rows, where the app required presenting these rows
to the user sorted based on information in the partition key. The partition
count is small enough to do the sort client-side in memory, which is what the
app did with the Thrift API--a range slice with an empty columns list.
This was a problem when migrating to CQL3. {{SELECT mykey FROM mytable}}
includes all the logical rows, which makes the resultset too large to make
this a reasonable approach, even with paging.
One way to add support would be to allow DISTINCT in the special case of
{{SELECT DISTINCT mykey FROM mytable}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-5891) Scrub disk footprint needs to be reduced
[ https://issues.apache.org/jira/browse/CASSANDRA-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744695#comment-13744695 ] Dave Brosius commented on CASSANDRA-5891: - patch seems fine, but does not apply cleanly to the cassandra-1.2 branch, can you please rebase? nit: it seems awkward that the disableSnapshot parm is between keyspace and columnfamilies, (understood that varargs gets in the way) perhaps it should be first? Scrub disk footprint needs to be reduced Key: CASSANDRA-5891 URL: https://issues.apache.org/jira/browse/CASSANDRA-5891 Project: Cassandra Issue Type: Bug Components: Tools Reporter: sankalp kohli Assignee: Lyuben Todorov Priority: Minor Fix For: 1.2.9 Attachments: 5891.patch Currently scrub creates a snapshot at the beginning of the scrub. This causes the disk used to be doubled after the scrub. If the disk utilization is more than 50%, scrub wont work. It would be nice to have an overriding option to disable snapshot. Something like --no-snapshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
