[VOTE] Release Apache Cassandra 1.2.0-rc1
We've fixed pretty much all know issues since beta2 (remains 2 issues tagged 1.2.0 but none are really critical if they don't make it anyway) so so I propose the following artifacts for release as 1.2.0-rc1. sha1: 2f187c92033b5b3f689d75375308dbf4dbac515f Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.0-rc1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-100/org/apache/cassandra/apache-cassandra/1.2.0-rc1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-100/ 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/8RW6q (CHANGES.txt) [2]: http://goo.gl/ltVIw (NEWS.txt)
[VOTE SUCCESS] Release Apache Cassandra 1.1.7
Including my own, I'm counting 5 binding +1's, one other +1 and no -1's, the vote passes. I'll get the artifacts published. -- Sylvain On Tue, Nov 27, 2012 at 7:41 PM, Brandon Williams wrote: > +1 > > On Tue, Nov 27, 2012 at 3:29 AM, Sylvain Lebresne > wrote: > > A fair amount of fixes went in since 1.1.6, so I propose the following > > artifacts for release as 1.1.7. > > > > sha1: 2f4b6d8c61d81ac4c878a4399a3634221deeb075 > > Git: > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.7-tentative > > Artifacts: > > > https://repository.apache.org/content/repositories/orgapachecassandra-082/org/apache/cassandra/apache-cassandra/1.1.7/ > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachecassandra-082/ > > > > 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/tYcFp (CHANGES.txt) > > [2]: http://goo.gl/dllaz (NEWS.txt) >
Re: Removing 2-phase compaction question
> I'm finding myself modifying row serialization stuff in > ColumnFamilySerializer, RowIndexEntry, SSTableReader/Writer, > SimpleSliceReader, and others. That mostly sound about right. As said in the ticket, if we stop writing the size at the beginning of the rows, we need to have marker of the end of row to know when to stop reading. So this will change the file format somewhat and should have an impact on quite a bit of files. The only one I'm not sure I see why you need modification is RowIndexEntry (maybe there is a good reason, just saying that a priori I'm not seeing which one). > and that I haven't gone off the deep end Feel free to put a wip branch somewhere if you want some feedback on the approach, even if said branch is not even compiling. -- Sylvain
Re: Removing 2-phase compaction question
Sylvain, Thanks for the feedback! You're probably right about the RIE, but as this is my first 'really deep' ticket into the bowels of c*, I'm learning the role/purpose of everything as I'm going. As for the WIP branch, I may take the community up on that :). Thanks, -Jason On Fri, Nov 30, 2012 at 2:33 AM, Sylvain Lebresne wrote: > > I'm finding myself modifying row serialization stuff in > > ColumnFamilySerializer, RowIndexEntry, SSTableReader/Writer, > > SimpleSliceReader, and others. > > That mostly sound about right. As said in the ticket, if we stop writing > the > size at the beginning of the rows, we need to have marker of the end of row > to > know when to stop reading. So this will change the file format somewhat and > should have an impact on quite a bit of files. The only one I'm not sure I > see > why you need modification is RowIndexEntry (maybe there is a good reason, > just > saying that a priori I'm not seeing which one). > > > and that I haven't gone off the deep end > > Feel free to put a wip branch somewhere if you want some feedback on the > approach, even if said branch is not even compiling. > > -- > Sylvain >
Secondary Index seen as empty
Hi,
We got an issue here with cassandra 1.1.6 where a secondary index seems to be
seen as empty. For example, If I try to see what are the first 10 values I have
:
cqlsh:pns_fr> select mailendwnd from syndic limit 10;
mailendwnd
--
2012-11-29 23:30:00+
2012-11-29 02:35:00+
2012-11-29 06:35:00+
2012-11-29 00:30:00+
2012-11-29 07:10:00+
2012-11-29 02:10:00+
2012-11-29 01:55:00+
2012-11-29 23:45:00+
2012-11-29 07:25:00+
2012-11-29 06:55:00+
However, even if there is a secondary index on mailendwnd, we can't get any
record :
cqlsh:pns_fr> select mailendwnd from syndic where mailendwnd = '2012-11-29
02:35:00+' limit 1000;
fyi, It's resolved by repairing the index and it happened a few times. I
launched cassandra in debug mode and noticed that it thinks there is no data in
the index :
DEBUG [Thrift:14] 2012-11-30 08:35:20,756 CassandraServer.java (line 1232)
execute_cql_query
DEBUG [Thrift:14] 2012-11-30 08:35:20,758 QueryProcessor.java (line 445) CQL
statement type: SELECT
DEBUG [Thrift:14] 2012-11-30 08:35:20,777 StorageProxy.java (line 842)
Command/ConsistencyLevel is RangeSliceCommand{keyspace='pns_fr',
column_family='syndic', super_column=null,
predicate=SlicePredicate(column_names:[java.nio.HeapByteBuffer[pos=0 lim=10
cap=10]]), range=[min(-1),m
in(-1)], row_filter =[IndexExpression(column_name:6D 61 69 6C 65 6E 64 77 6E
64, op:EQ, value:00 00 01 3B 4A 04 64 20)], maxResults=1,
maxIsColumns=false}/ONE
DEBUG [Thrift:14] 2012-11-30 08:35:20,778 StorageProxy.java (line 1073)
restricted ranges for query [min(-1),min(-1)] are [[min(-1),max(0)],
(max(0),max(21267647932558653966460912964485513216)],
(max(21267647932558653966460912964485513216),max(42535295865117307932921825928971026432
)],
(max(42535295865117307932921825928971026432),max(63802943797675961899382738893456539648)],
(max(63802943797675961899382738893456539648),max(85070591730234615865843651857942052864)],
(max(85070591730234615865843651857942052864),max(106338239662793269832304564822427566080)],
(max
(106338239662793269832304564822427566080),max(127605887595351923798765477786913079296)],
(max(127605887595351923798765477786913079296),max(148873535527910577765226390751398592512)],
(max(148873535527910577765226390751398592512),min(-1)]]
DEBUG [Thrift:14] 2012-11-30 08:35:20,779 NetworkTopologyStrategy.java (line
125) /10.244.136.105,/10.244.137.238,/10.244.130.226 endpoints in datacenter
us-west-2 for token 0
DEBUG [Thrift:14] 2012-11-30 08:35:20,780 StorageProxy.java (line 869) local
range slice
DEBUG [Thrift:14] 2012-11-30 08:35:20,782 ExtendedFilter.java (line 181) adding
columns to original Filter to cover additional expressions
DEBUG [Thrift:14] 2012-11-30 08:35:20,782 KeysSearcher.java (line 99) Primary
scan clause is mailendwnd
DEBUG [Thrift:14] 2012-11-30 08:35:20,783 ColumnFamilyStore.java (line 1449)
Filtering org.apache.cassandra.db.index.keys.KeysSearcher$1@60ce274e for rows
matching
org.apache.cassandra.db.filter.ExtendedFilter$FilterWithClauses@7e76a388
DEBUG [Thrift:14] 2012-11-30 08:35:20,784 KeysSearcher.java (line 135) Scanning
index 'syndic.mailendwnd EQ 2012-11-29 02:35:00+' starting with
DEBUG [Thrift:14] 2012-11-30 08:35:20,784 CollationController.java (line 227)
collectAllData
DEBUG [Thrift:14] 2012-11-30 08:35:20,784 KeysSearcher.java(line 145) fetched
null
DEBUG [Thrift:14] 2012-11-30 08:35:20,784 KeysSearcher.java (line 148) no data,
all done <- THIS IS WHAT IT SAYS HERE
I tried to remotely debug cassandra from eclipse but I wasn't able to do it.
Whenever it tries to connect to the dt_socket it fails and the port is closed
on the server :( I tried locally without any issue but I havent the data (can I
copy data from one node to mine and debug it locally, is it possible ?). I'm
investigating network issues concerning that to help you. If you have input
concerning the issue before I can debug it, welcome !
Regards
Cyril SCETBON
Re: [VOTE] Release Apache Cassandra 1.2.0-rc1
+1 On Fri, Nov 30, 2012 at 7:17 PM, Sylvain Lebresne wrote: > We've fixed pretty much all know issues since beta2 (remains 2 issues tagged > 1.2.0 but none are really critical if they don't make it anyway) so so I > propose the following artifacts for release as 1.2.0-rc1. > > sha1: 2f187c92033b5b3f689d75375308dbf4dbac515f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.0-rc1-tentative > Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-100/org/apache/cassandra/apache-cassandra/1.2.0-rc1/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-100/ > > 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/8RW6q (CHANGES.txt) > [2]: http://goo.gl/ltVIw (NEWS.txt) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: [VOTE] Release Apache Cassandra 1.2.0-rc1
+1 Regards, On Fri, Nov 30, 2012 at 2:17 AM, Sylvain Lebresne wrote: > We've fixed pretty much all know issues since beta2 (remains 2 issues > tagged > 1.2.0 but none are really critical if they don't make it anyway) so so I > propose the following artifacts for release as 1.2.0-rc1. > > sha1: 2f187c92033b5b3f689d75375308dbf4dbac515f > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.0-rc1-tentative > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-100/org/apache/cassandra/apache-cassandra/1.2.0-rc1/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-100/ > > 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/8RW6q (CHANGES.txt) > [2]: http://goo.gl/ltVIw (NEWS.txt) >
Re: Secondary Index seen as empty
Re remote debugging, see cassandra-env.sh:
# uncomment to have Cassandra JVM listen for remote
debuggers/profilers on port 1414
# JVM_OPTS="$JVM_OPTS -Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1414"
On Sat, Dec 1, 2012 at 1:22 AM, Cyril Scetbon wrote:
> Hi,
>
> We got an issue here with cassandra 1.1.6 where a secondary index seems to be
> seen as empty. For example, If I try to see what are the first 10 values I
> have :
>
> cqlsh:pns_fr> select mailendwnd from syndic limit 10;
> mailendwnd
> --
> 2012-11-29 23:30:00+
> 2012-11-29 02:35:00+
> 2012-11-29 06:35:00+
> 2012-11-29 00:30:00+
> 2012-11-29 07:10:00+
> 2012-11-29 02:10:00+
> 2012-11-29 01:55:00+
> 2012-11-29 23:45:00+
> 2012-11-29 07:25:00+
> 2012-11-29 06:55:00+
>
> However, even if there is a secondary index on mailendwnd, we can't get any
> record :
>
> cqlsh:pns_fr> select mailendwnd from syndic where mailendwnd = '2012-11-29
> 02:35:00+' limit 1000;
>
> fyi, It's resolved by repairing the index and it happened a few times. I
> launched cassandra in debug mode and noticed that it thinks there is no data
> in the index :
>
> DEBUG [Thrift:14] 2012-11-30 08:35:20,756 CassandraServer.java (line 1232)
> execute_cql_query
> DEBUG [Thrift:14] 2012-11-30 08:35:20,758 QueryProcessor.java (line 445) CQL
> statement type: SELECT
> DEBUG [Thrift:14] 2012-11-30 08:35:20,777 StorageProxy.java (line 842)
> Command/ConsistencyLevel is RangeSliceCommand{keyspace='pns_fr',
> column_family='syndic', super_column=null,
> predicate=SlicePredicate(column_names:[java.nio.HeapByteBuffer[pos=0 lim=10
> cap=10]]), range=[min(-1),m
> in(-1)], row_filter =[IndexExpression(column_name:6D 61 69 6C 65 6E 64 77 6E
> 64, op:EQ, value:00 00 01 3B 4A 04 64 20)], maxResults=1,
> maxIsColumns=false}/ONE
> DEBUG [Thrift:14] 2012-11-30 08:35:20,778 StorageProxy.java (line 1073)
> restricted ranges for query [min(-1),min(-1)] are [[min(-1),max(0)],
> (max(0),max(21267647932558653966460912964485513216)],
> (max(21267647932558653966460912964485513216),max(42535295865117307932921825928971026432
> )],
> (max(42535295865117307932921825928971026432),max(63802943797675961899382738893456539648)],
>
> (max(63802943797675961899382738893456539648),max(85070591730234615865843651857942052864)],
>
> (max(85070591730234615865843651857942052864),max(106338239662793269832304564822427566080)],
> (max
> (106338239662793269832304564822427566080),max(127605887595351923798765477786913079296)],
>
> (max(127605887595351923798765477786913079296),max(148873535527910577765226390751398592512)],
> (max(148873535527910577765226390751398592512),min(-1)]]
> DEBUG [Thrift:14] 2012-11-30 08:35:20,779 NetworkTopologyStrategy.java (line
> 125) /10.244.136.105,/10.244.137.238,/10.244.130.226 endpoints in datacenter
> us-west-2 for token 0
> DEBUG [Thrift:14] 2012-11-30 08:35:20,780 StorageProxy.java (line 869) local
> range slice
> DEBUG [Thrift:14] 2012-11-30 08:35:20,782 ExtendedFilter.java (line 181)
> adding columns to original Filter to cover additional expressions
> DEBUG [Thrift:14] 2012-11-30 08:35:20,782 KeysSearcher.java (line 99) Primary
> scan clause is mailendwnd
> DEBUG [Thrift:14] 2012-11-30 08:35:20,783 ColumnFamilyStore.java (line 1449)
> Filtering org.apache.cassandra.db.index.keys.KeysSearcher$1@60ce274e for rows
> matching
> org.apache.cassandra.db.filter.ExtendedFilter$FilterWithClauses@7e76a388
> DEBUG [Thrift:14] 2012-11-30 08:35:20,784 KeysSearcher.java (line 135)
> Scanning index 'syndic.mailendwnd EQ 2012-11-29 02:35:00+' starting with
> DEBUG [Thrift:14] 2012-11-30 08:35:20,784 CollationController.java (line 227)
> collectAllData
> DEBUG [Thrift:14] 2012-11-30 08:35:20,784 KeysSearcher.java(line 145) fetched
> null
> DEBUG [Thrift:14] 2012-11-30 08:35:20,784 KeysSearcher.java (line 148) no
> data, all done <- THIS IS WHAT IT SAYS HERE
>
> I tried to remotely debug cassandra from eclipse but I wasn't able to do it.
> Whenever it tries to connect to the dt_socket it fails and the port is closed
> on the server :( I tried locally without any issue but I havent the data (can
> I copy data from one node to mine and debug it locally, is it possible ?).
> I'm investigating network issues concerning that to help you. If you have
> input concerning the issue before I can debug it, welcome !
>
> Regards
>
> Cyril SCETBON
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder, http://www.datastax.com
@spyced
Re: 2.0
Hi Jonathan, I'm in favor of paying off the technical debt, as well, and I wonder if there is value in removing support for thrift with 2.0? We're currently in 'do as little as possible' mode with thrift, so should we aggressively cast it off and push the binary CQL protocol? Seems like a jump to '2.0', along with the other initiatives, would be a reasonable time/milestone to do so. Thanks, -Jason On Fri, Nov 30, 2012 at 12:12 PM, Jonathan Ellis wrote: > The more I think about it, the more I think we should call 1.2-next, > 2.0. I'd like to spend some time paying off our technical debt: > > - replace supercolumns with composites (CASSANDRA-3237) > - rewrite counters (CASSANDRA-4775) > - improve storage engine support for wide rows > - better stage management to improve latency (disruptor? lightweight > threads? custom executor + queue?) > - improved repair (CASSANDRA-3362, 2699) > > Of course, we're planning some new features as well: > - triggers (CASSANDRA-1311) > - improved query fault tolerance (CASSANDRA-4705) > - row size limits (CASSANDRA-3929) > - cql3 integration for hadoop (CASSANDRA-4421) > - improved caching (CASSANDRA-1956, 2864) > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced >
Re: 2.0
Good idea. Lets remove thrift, CQL3 is still beta, but I am willing to upgrade to a version that removes thrift. Then when all our clients can not connect they will be forced to get with the program. On Fri, Nov 30, 2012 at 5:33 PM, Jason Brown wrote: > Hi Jonathan, > > I'm in favor of paying off the technical debt, as well, and I wonder if > there is value in removing support for thrift with 2.0? We're currently in > 'do as little as possible' mode with thrift, so should we aggressively cast > it off and push the binary CQL protocol? Seems like a jump to '2.0', along > with the other initiatives, would be a reasonable time/milestone to do so. > > Thanks, > > -Jason > > > On Fri, Nov 30, 2012 at 12:12 PM, Jonathan Ellis > wrote: > > > The more I think about it, the more I think we should call 1.2-next, > > 2.0. I'd like to spend some time paying off our technical debt: > > > > - replace supercolumns with composites (CASSANDRA-3237) > > - rewrite counters (CASSANDRA-4775) > > - improve storage engine support for wide rows > > - better stage management to improve latency (disruptor? lightweight > > threads? custom executor + queue?) > > - improved repair (CASSANDRA-3362, 2699) > > > > Of course, we're planning some new features as well: > > - triggers (CASSANDRA-1311) > > - improved query fault tolerance (CASSANDRA-4705) > > - row size limits (CASSANDRA-3929) > > - cql3 integration for hadoop (CASSANDRA-4421) > > - improved caching (CASSANDRA-1956, 2864) > > > > -- > > Jonathan Ellis > > Project Chair, Apache Cassandra > > co-founder, http://www.datastax.com > > @spyced > > >
Re: 2.0
As attractive as it would be to clean house, I think we owe it to our users to keep Thrift around for the forseeable future rather than orphan all Thrift-using applications (which is virtually everyone) on 1.2. On Sat, Dec 1, 2012 at 7:33 AM, Jason Brown wrote: > Hi Jonathan, > > I'm in favor of paying off the technical debt, as well, and I wonder if > there is value in removing support for thrift with 2.0? We're currently in > 'do as little as possible' mode with thrift, so should we aggressively cast > it off and push the binary CQL protocol? Seems like a jump to '2.0', along > with the other initiatives, would be a reasonable time/milestone to do so. > > Thanks, > > -Jason > > > On Fri, Nov 30, 2012 at 12:12 PM, Jonathan Ellis wrote: > >> The more I think about it, the more I think we should call 1.2-next, >> 2.0. I'd like to spend some time paying off our technical debt: >> >> - replace supercolumns with composites (CASSANDRA-3237) >> - rewrite counters (CASSANDRA-4775) >> - improve storage engine support for wide rows >> - better stage management to improve latency (disruptor? lightweight >> threads? custom executor + queue?) >> - improved repair (CASSANDRA-3362, 2699) >> >> Of course, we're planning some new features as well: >> - triggers (CASSANDRA-1311) >> - improved query fault tolerance (CASSANDRA-4705) >> - row size limits (CASSANDRA-3929) >> - cql3 integration for hadoop (CASSANDRA-4421) >> - improved caching (CASSANDRA-1956, 2864) >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder, http://www.datastax.com >> @spyced >> -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: 2.0
My hope is that after 1.2 (i.e. by the time we're 2.0'ing), the binary CQL protocol is out of beta :). On Fri, Nov 30, 2012 at 2:39 PM, Edward Capriolo wrote: > Good idea. Lets remove thrift, CQL3 is still beta, but I am willing to > upgrade to a version that removes thrift. Then when all our clients can not > connect they will be forced to get with the program >
Re: 2.0
+1 Regards, On Fri, Nov 30, 2012 at 12:12 PM, Jonathan Ellis wrote: > The more I think about it, the more I think we should call 1.2-next, > 2.0. I'd like to spend some time paying off our technical debt: > > - replace supercolumns with composites (CASSANDRA-3237) > - rewrite counters (CASSANDRA-4775) > - improve storage engine support for wide rows > - better stage management to improve latency (disruptor? lightweight > threads? custom executor + queue?) > - improved repair (CASSANDRA-3362, 2699) > > Of course, we're planning some new features as well: > - triggers (CASSANDRA-1311) > - improved query fault tolerance (CASSANDRA-4705) > - row size limits (CASSANDRA-3929) > - cql3 integration for hadoop (CASSANDRA-4421) > - improved caching (CASSANDRA-1956, 2864) > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced >
Re: 2.0
I'm not thrilled with Thrift, but I'd like to see and hear more real world use of CQL first (Avro all the things is not that long ago). That said, a major rev /could/ do this - not start the thrift server by default. It's then a hoop jump to enable it via nodetool/yaml, and signals to the client communities and user base, where the project intends to go. Bill On 30/11/12 22:49, Jonathan Ellis wrote: As attractive as it would be to clean house, I think we owe it to our users to keep Thrift around for the forseeable future rather than orphan all Thrift-using applications (which is virtually everyone) on 1.2. On Sat, Dec 1, 2012 at 7:33 AM, Jason Brown wrote: Hi Jonathan, I'm in favor of paying off the technical debt, as well, and I wonder if there is value in removing support for thrift with 2.0? We're currently in 'do as little as possible' mode with thrift, so should we aggressively cast it off and push the binary CQL protocol? Seems like a jump to '2.0', along with the other initiatives, would be a reasonable time/milestone to do so. Thanks, -Jason On Fri, Nov 30, 2012 at 12:12 PM, Jonathan Ellis wrote: The more I think about it, the more I think we should call 1.2-next, 2.0. I'd like to spend some time paying off our technical debt: - replace supercolumns with composites (CASSANDRA-3237) - rewrite counters (CASSANDRA-4775) - improve storage engine support for wide rows - better stage management to improve latency (disruptor? lightweight threads? custom executor + queue?) - improved repair (CASSANDRA-3362, 2699) Of course, we're planning some new features as well: - triggers (CASSANDRA-1311) - improved query fault tolerance (CASSANDRA-4705) - row size limits (CASSANDRA-3929) - cql3 integration for hadoop (CASSANDRA-4421) - improved caching (CASSANDRA-1956, 2864) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: 2.0
I agree, I don't think its a great idea to drop thrift until the back end tools are 100% compatible and have some level of agreement from the major users of Cassandra. Paying off technical dept though I'm all for, and I think its key to the long term success of the application. Right now Supercolumns to someone new coming to the system might think "Hey, these things look great. Lets use them" and in a few months time hate all things that are cassandra. Ray Slakinski On 12/01, Jonathan Ellis wrote: > As attractive as it would be to clean house, I think we owe it to our > users to keep Thrift around for the forseeable future rather than > orphan all Thrift-using applications (which is virtually everyone) on > 1.2. > > On Sat, Dec 1, 2012 at 7:33 AM, Jason Brown wrote: > > Hi Jonathan, > > > > I'm in favor of paying off the technical debt, as well, and I wonder if > > there is value in removing support for thrift with 2.0? We're currently in > > 'do as little as possible' mode with thrift, so should we aggressively cast > > it off and push the binary CQL protocol? Seems like a jump to '2.0', along > > with the other initiatives, would be a reasonable time/milestone to do so. > > > > Thanks, > > > > -Jason > > > > > > On Fri, Nov 30, 2012 at 12:12 PM, Jonathan Ellis wrote: > > > >> The more I think about it, the more I think we should call 1.2-next, > >> 2.0. I'd like to spend some time paying off our technical debt: > >> > >> - replace supercolumns with composites (CASSANDRA-3237) > >> - rewrite counters (CASSANDRA-4775) > >> - improve storage engine support for wide rows > >> - better stage management to improve latency (disruptor? lightweight > >> threads? custom executor + queue?) > >> - improved repair (CASSANDRA-3362, 2699) > >> > >> Of course, we're planning some new features as well: > >> - triggers (CASSANDRA-1311) > >> - improved query fault tolerance (CASSANDRA-4705) > >> - row size limits (CASSANDRA-3929) > >> - cql3 integration for hadoop (CASSANDRA-4421) > >> - improved caching (CASSANDRA-1956, 2864) > >> > >> -- > >> Jonathan Ellis > >> Project Chair, Apache Cassandra > >> co-founder, http://www.datastax.com > >> @spyced > >> > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced
