It is still there, but we took it out of the sample config because
people think it affects normal writes which it does not.
On Thu, Mar 17, 2011 at 11:48 AM, A J wrote:
> I don't see binary_memtable_throughput_in_mb parameter in
> cassandra.yaml anymore.
> What is it replaced by ?
>
> thanks.
>
>
I don't see binary_memtable_throughput_in_mb parameter in
cassandra.yaml anymore.
What is it replaced by ?
thanks.
On Tue, Mar 15, 2011 at 11:32 PM, Eric Evans wrote:
> On Tue, 2011-03-15 at 22:19 -0500, Eric Evans wrote:
>> On Tue, 2011-03-15 at 14:26 -0700, Mark wrote:
>> > Still not seeing 0.
On Tue, 2011-03-15 at 22:19 -0500, Eric Evans wrote:
> On Tue, 2011-03-15 at 14:26 -0700, Mark wrote:
> > Still not seeing 0.7.4 as a download option on the main site?
>
> Something about the site's pubsub isn't working; I'll contact INFRA.
https://issues.apache.org/jira/browse/INFRA-3520
--
Er
On Tue, 2011-03-15 at 14:26 -0700, Mark wrote:
> Still not seeing 0.7.4 as a download option on the main site?
Something about the site's pubsub isn't working; I'll contact INFRA.
--
Eric Evans
eev...@rackspace.com
On Tue, Mar 15, 2011 at 4:26 PM, Mark wrote:
> Still not seeing 0.7.4 as a download option on the main site?
Artifacts are probably still syncing, try
http://www.apache.org/dyn/closer.cgi?path=/cassandra/0.7.4/apache-cassandra-0.7.4-bin.tar.gz
until
one of them works.
-Brandon
Still not seeing 0.7.4 as a download option on the main site?
On 3/15/11 9:20 AM, Eric Evans wrote:
Hot on the heals of 0.7.3, I'm pleased to announce 0.7.4, with bugs
fixed, optimizations made, and features added[1].
Upgrading from 0.7.3 is a snap, but if you're upgrading from an earlier
versi
Hot on the heals of 0.7.3, I'm pleased to announce 0.7.4, with bugs
fixed, optimizations made, and features added[1].
Upgrading from 0.7.3 is a snap, but if you're upgrading from an earlier
version, do pay special attention to the release notes[2].
If you spot any problems, let us know[3], and i
