[VOTE] Release Apache Cassandra 2.0.0-beta1
Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt)
org.apache.cassandra.cli.CliTest:testCli is failing
Hi, I checked out fresh sources from git. I am trying to run unit tests by executing $ant test but the CliTest is failing. The log trace is attached below. Can someone help me if i am missing any configs. Thank you. ERROR [FlushWriter:1] 2013-07-09 15:03:28,428 SSTable.java (line 306) Missing component: build/test/cassandra/data/system/IndexInfo/system-IndexInfo-tmp-ja-6-Summary.db ERROR [FlushWriter:1] 2013-07-09 15:03:28,429 SSTable.java (line 306) Missing component: build/test/cassandra/data/system/IndexInfo/system-IndexInfo-tmp-ja-6-Statistics.db ERROR [FlushWriter:1] 2013-07-09 15:03:28,430 SSTable.java (line 306) Missing component: build/test/cassandra/data/system/IndexInfo/system-IndexInfo-tmp-ja-6-CompressionInfo.db ERROR [FlushWriter:1] 2013-07-09 15:03:28,430 SSTable.java (line 306) Missing component: build/test/cassandra/data/system/IndexInfo/system-IndexInfo-tmp-ja-6-Data.db DEBUG [FlushWriter:1] 2013-07-09 15:03:28,430 FileUtils.java (line 113) Deleting system-IndexInfo-tmp-ja-6-TOC.txt DEBUG [FlushWriter:1] 2013-07-09 15:03:28,430 FileUtils.java (line 113) Deleting system-IndexInfo-tmp-ja-6-Index.db DEBUG [FlushWriter:1] 2013-07-09 15:03:28,430 FileUtils.java (line 113) Deleting system-IndexInfo-tmp-ja-6-Filter.db DEBUG [FlushWriter:1] 2013-07-09 15:03:28,431 SSTable.java (line 153) Deleted build/test/cassandra/data/system/IndexInfo/system-IndexInfo-tmp-ja-6 ERROR [FlushWriter:1] 2013-07-09 15:03:28,433 CassandraDaemon.java (line 196) Exception in thread Thread[FlushWriter:1,5,main] java.lang.AssertionError at org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:130) at org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:125) at org.apache.cassandra.io.sstable.SSTableWriter.rename(SSTableWriter.java:363) at org.apache.cassandra.io.sstable.SSTableWriter.rename(SSTableWriter.java:355) at org.apache.cassandra.io.sstable.SSTableWriter.closeAndOpenReader(SSTableWriter.java:314) at org.apache.cassandra.io.sstable.SSTableWriter.closeAndOpenReader(SSTableWriter.java:296) at org.apache.cassandra.db.Memtable$FlushRunnable.writeSortedContents(Memtable.java:427) at org.apache.cassandra.db.Memtable$FlushRunnable.runWith(Memtable.java:381) at org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48) at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724)
Re: [VOTE] Release Apache Cassandra 2.0.0-beta1
+1 On Tue, Jul 9, 2013 at 2:50 PM, Sylvain Lebresne sylv...@datastax.comwrote: Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt) -- Thanks, Murali 99025-5
Re: [VOTE] Release Apache Cassandra 2.0.0-beta1
+1 On Tue, Jul 9, 2013 at 5:20 AM, Sylvain Lebresne sylv...@datastax.comwrote: Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 2.0.0-beta1
+1. Woo-hoo! On Tue, Jul 9, 2013 at 4:45 AM, Carl Yeksigian c...@yeksigian.com wrote: +1 On Tue, Jul 9, 2013 at 5:20 AM, Sylvain Lebresne sylv...@datastax.com wrote: Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt)
Configuration of network connectors
Hello, First of all I would like to say hello to cassandra user and developer community. :) I write because we are using Cassandra in our unit tests and we have some troubles with network connectivity. We ca not run multiple cassandra instances during tests because we would need to randomize configuration of port and so on. For now if we try to fork our tests we get address already in use on one from two ports - native or thrift. In other apache projects we can VM connectors (ActiveMQ, Camel, Mina) based on in-memory queue. I took some time to see how CassandraDaemon starts servers and it's kinda of hardcoded. I thought about changing configuration to be more like: servers: - class org.apache.cassandra.thrift.ThriftServer - class org.apache.cassandra.transport.Server Then we will be able to disable these servers for unit tests: servers: - class org.apache.cassandra.vm.VmServer This requires some small changes in daemon code and client libraries. I'm not really deeply involved in cassandra stuff so I don't know the internal architecture and implications thus I look forward for you to discuss this topic. Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org
Re: Configuration of network connectors
Have you seen https://github.com/pcmanus/ccm as described in http://www.datastax.com/dev/blog/ccm-a-development-tool-for-creating-local-cassandra-clusters or does that not fit your use case? On 9 Jul 2013, at 14:02, Łukasz Dywicki l...@code-house.org wrote: Hello, First of all I would like to say hello to cassandra user and developer community. :) I write because we are using Cassandra in our unit tests and we have some troubles with network connectivity. We ca not run multiple cassandra instances during tests because we would need to randomize configuration of port and so on. For now if we try to fork our tests we get address already in use on one from two ports - native or thrift. In other apache projects we can VM connectors (ActiveMQ, Camel, Mina) based on in-memory queue. I took some time to see how CassandraDaemon starts servers and it's kinda of hardcoded. I thought about changing configuration to be more like: servers: - class org.apache.cassandra.thrift.ThriftServer - class org.apache.cassandra.transport.Server Then we will be able to disable these servers for unit tests: servers: - class org.apache.cassandra.vm.VmServer This requires some small changes in daemon code and client libraries. I'm not really deeply involved in cassandra stuff so I don't know the internal architecture and implications thus I look forward for you to discuss this topic. Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org
Re: [VOTE] Release Apache Cassandra 2.0.0-beta1
+1 On Jul 9, 2013 4:21 AM, Sylvain Lebresne sylv...@datastax.com wrote: Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 2.0.0-beta1
[ Sylvain Lebresne ] Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). +1 [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt) -- Eric Evans eev...@sym-link.com
Composite Key Overload
Hi Everyone, I have a CF which currently has a large composite key. Let's say it has 5 components, A,B,C,D,E. I know I need to be able to query and find all rows where A,B,C equal a certain value. And I also need to query when A,B,C,D are a certain value. Traditionally what is the best approach for this? * Composite key? Is it possible to query on components of the composite key? * Duplicate the fields I want to query on and create a secondary index * Expand the data into supercolumns for horizontal traversal * Create lookup tables and suffer having to do reads before being able to write updates Thanks
Re: Configuration of network connectors
Jeremy,
Sadly it does not cover our case. We have unit tests and we want to test really
basic things like mappings of data contained in cassandra to our model. For
that we don't need cluster at all because in unit tests we don't want to test
data distribution. We also would like to run everything in JVM, thus CCM
written in Python is not really what we need.
What we are looking for is minimal cassandra set up which could be embedded and
used concurrently multiple times. For example we now use CassandraUnit:
@Rule
public CassandraUnit unit = new CassandraUnit(new EmptyDataSet(),
embedded-cassandra.yaml);
@Test
public void fistTest() {
// do something with data
}
@Test
public void secondTest() {
// do something else
}
In this set up JUnit will launch new CassandraDaemon for every test. If we set
FORK_MODE per test then we may have two cassandra instances running at the same
time. First test which launch CassandraDaemon will pass, second may fail due
port usage conflict. That's why we thought about testing without network layer.
This can save some time. It would be great because for some older hardware used
by our developers it takes up to 9 minutes to run build with all unit tests.
Some of this time is consumed by startup and shutdown of cassandra.
Cheers,
Łukasz Dywicki
--
l...@code-house.org
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org
Wiadomość napisana przez Jeremy Hanna jeremy.hanna1...@gmail.com w dniu 9 lip
2013, o godz. 15:22:
Have you seen https://github.com/pcmanus/ccm as described in
http://www.datastax.com/dev/blog/ccm-a-development-tool-for-creating-local-cassandra-clusters
or does that not fit your use case?
On 9 Jul 2013, at 14:02, Łukasz Dywicki l...@code-house.org wrote:
Hello,
First of all I would like to say hello to cassandra user and developer
community. :)
I write because we are using Cassandra in our unit tests and we have some
troubles with network connectivity. We ca not run multiple cassandra
instances during tests because we would need to randomize configuration of
port and so on. For now if we try to fork our tests we get address already
in use on one from two ports - native or thrift. In other apache projects
we can VM connectors (ActiveMQ, Camel, Mina) based on in-memory queue. I
took some time to see how CassandraDaemon starts servers and it's kinda of
hardcoded. I thought about changing configuration to be more like:
servers:
- class org.apache.cassandra.thrift.ThriftServer
- class org.apache.cassandra.transport.Server
Then we will be able to disable these servers for unit tests:
servers:
- class org.apache.cassandra.vm.VmServer
This requires some small changes in daemon code and client libraries. I'm
not really deeply involved in cassandra stuff so I don't know the internal
architecture and implications thus I look forward for you to discuss this
topic.
Cheers,
Łukasz Dywicki
--
l...@code-house.org
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org
Re: Configuration of network connectors
You'd still end up needing to fork tests because of the singleton problem.
(Google that one.)
I say this without trying, but it shouldn't be terribly hard for you to
code up some fixture classes that allow you to test the storage layer, so
long as you can tolerate each test running in a forked VM. Same goes for
the ports, with the exception of JMX iirc.
Gary.
On Tuesday, July 9, 2013, Łukasz Dywicki wrote:
Jeremy,
Sadly it does not cover our case. We have unit tests and we want to test
really basic things like mappings of data contained in cassandra to our
model. For that we don't need cluster at all because in unit tests we don't
want to test data distribution. We also would like to run everything in
JVM, thus CCM written in Python is not really what we need.
What we are looking for is minimal cassandra set up which could be
embedded and used concurrently multiple times. For example we now use
CassandraUnit:
@Rule
public CassandraUnit unit = new CassandraUnit(new EmptyDataSet(),
embedded-cassandra.yaml);
@Test
public void fistTest() {
// do something with data
}
@Test
public void secondTest() {
// do something else
}
In this set up JUnit will launch new CassandraDaemon for every test. If we
set FORK_MODE per test then we may have two cassandra instances running at
the same time. First test which launch CassandraDaemon will pass, second
may fail due port usage conflict. That's why we thought about testing
without network layer. This can save some time. It would be great because
for some older hardware used by our developers it takes up to 9 minutes to
run build with all unit tests. Some of this time is consumed by startup and
shutdown of cassandra.
Cheers,
Łukasz Dywicki
--
l...@code-house.org javascript:;
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org
Wiadomość napisana przez Jeremy Hanna
jeremy.hanna1...@gmail.comjavascript:;
w dniu 9 lip 2013, o godz. 15:22:
Have you seen https://github.com/pcmanus/ccm as described in
http://www.datastax.com/dev/blog/ccm-a-development-tool-for-creating-local-cassandra-clustersor
does that not fit your use case?
On 9 Jul 2013, at 14:02, Łukasz Dywicki l...@code-house.orgjavascript:;
wrote:
Hello,
First of all I would like to say hello to cassandra user and developer
community. :)
I write because we are using Cassandra in our unit tests and we have
some troubles with network connectivity. We ca not run multiple cassandra
instances during tests because we would need to randomize configuration of
port and so on. For now if we try to fork our tests we get address already
in use on one from two ports - native or thrift. In other apache projects
we can VM connectors (ActiveMQ, Camel, Mina) based on in-memory queue. I
took some time to see how CassandraDaemon starts servers and it's kinda of
hardcoded. I thought about changing configuration to be more like:
servers:
- class org.apache.cassandra.thrift.ThriftServer
- class org.apache.cassandra.transport.Server
Then we will be able to disable these servers for unit tests:
servers:
- class org.apache.cassandra.vm.VmServer
This requires some small changes in daemon code and client libraries.
I'm not really deeply involved in cassandra stuff so I don't know the
internal architecture and implications thus I look forward for you to
discuss this topic.
Cheers,
Łukasz Dywicki
--
l...@code-house.org javascript:;
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org
Re: [VOTE] Release Apache Cassandra 2.0.0-beta1
+1 On Tue, Jul 9, 2013 at 4:20 AM, Sylvain Lebresne sylv...@datastax.comwrote: Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 2.0.0-beta1
+1 On Jul 9, 2013 3:21 AM, Sylvain Lebresne sylv...@datastax.com wrote: Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 2.0.0-beta1
+1 On Tue, Jul 9, 2013 at 11:20 AM, Sylvain Lebresne sylv...@datastax.comwrote: Cassandra 2.0 is coming along but we now need wider testing. So I propose the following artifacts for release as 2.0.0-beta1. Let it be clear that it is only a beta (and the first one at that), so we know it's not perfect, but the current goal is first and foremost to get better testing. sha1: fcdb39384e8570cf38c027f38b799181da06d56d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.0-beta1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-117/org/apache/cassandra/apache-cassandra/2.0.0-beta1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-117/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/LorY5 (CHANGES.txt) [2]: http://goo.gl/zEt5i (NEWS.txt)
