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 Superco
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 cli
+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 (CASS
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 cli
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
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 of
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
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
+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
+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: 2f187c92033b5
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:
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, 201
> 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 en
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 i
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
15 matches
Mail list logo
