Everything running smoothly. Ship it! +1
On 10/15/13, 4:44 PM, Gary Dusbabek gdusba...@gmail.com wrote:
+1
On Tuesday, October 15, 2013, Sylvain Lebresne wrote:
The changelog is getting big, I propose the following artifacts for
release
as 1.2.11.
sha1:
First, you should try the users list for your question. Someone there might
know better.
Second, I can't imagine sharing a C* instance with different workloads. If
anything I'd like to split my cluster up in size just for my own use on the
same project.
Third, 1.2 has support for Auth so
+1
This is currently broken.
On Aug 27, 2013, at 5:14 AM, Chris Burroughs chris.burrou...@gmail.com
wrote:
Following up on a discussion in IRC. A caveat on the (not new, but not
fixed) problems with replace_{node,token} would likely be appreciated by
users.
On 08/26/2013 02:53 PM,
No- not required, but there is zero reason not to. Keep as much off heap as
possible.
On Aug 14, 2013, at 12:13 PM, José Elias Queiroga da Costa Araújo
je...@cesar.org.br wrote:
Hi all, I have a question.
In order to activate cassandra row cache is necessary to have JNA
Cassandra memory usage.
When installed and configured, Linux does not swap out the JVM,
and thus avoids related performance issues.
So my question is if Cassandra cache implementation is based ByteBuffer,
there is any real reason to install JNA?
Regards,
2013/8/14 Michael Kjellman mkjell
Should probably use this instead. All benchmarks show it¹s faster than
anything that has ever been written before.
https://issues.apache.org/jira/browse/CASSANDRA-5582
On 8/12/13, 12:47 AM, Radim Kolar h...@filez.com wrote:
thrift, sync
Thrift? Native?
If Thrift- what threading model?
On Aug 11, 2013, at 4:13 PM, Radim Kolar h...@filez.com wrote:
Dne 10.8.2013 21:30, Brandon Williams napsal(a):
Make a conf/triggers directory and that will fix it. We fixed this in trunk
already.
yes, that fixed it.
2.0 is considerably
Why? Please give me 3 reasons why this is good advice to the OP.
The frame based binary protocol will be 100% easier to implement in C than
the never-been-out-of-alpha libc Thrift implementation. I¹ve worked with
that code for a while, it¹s *not* pretty.
I can¹t think of one reason, other than
Absolutely you should reuse prepared statements where possible in your
client code.
On 8/3/13, 5:34 PM, Michael Cohen mcohe...@gmail.com wrote:
More specifically, is it best practice to reuse PreparedStatements,
rather than creating a new one via session.prepare() on each database
access? Is
+1
This late in the release cycle it might really bite some people upgrading for
all the 1.2.x goodness.
On Jul 27, 2013, at 12:40 PM, Jonathan Ellis jbel...@gmail.com wrote:
The fix for range tombstone performance [1] introduced a regression
[2] that breaks slice queries against
Okay, I¹ll take the bait. I apologize if I come off rude here (you
certainly don¹t seem to care though if you do) but if you want production
ready enterprise QA tested code please see Datastax Enterprise. Just
because you didn¹t choose to use what is offered doesn¹t mean it doesn¹t
exist. Much
Better question for the users list, but everything about your cluster is
available in the system column family and accessible with CQL.
On 7/10/13, 11:46 PM, Murali muralidharan@gmail.com wrote:
Hi experts,
Can we use CQL 3.0 to get the partition / cluster information from
cassandra server?
Glad you got it fixed. In the future, if you have other issues using
Cassandra you might want to email the other C* mailing list at
u...@cassandra.apache.org, which has people listening geared to these
types of questions.
On 7/11/13, 12:05 AM, HuS.Andy hushansm...@hotmail.com wrote:
I got a
I know non members aren¹t supposed to comment on these votes, but I was
actually throwing 1.2.6 Strike 2ish into production when 3/4 of the way
thru I got Jason¹s email as I was debugging Gossip issues across the
cluster. It didn¹t appear to just break repair, but it also broke Gossip
(makes since
You will most likely get better answers to your if you try the Cassandra
users group instead for your question.
Best,
Michael
On 5/22/13 5:52 PM, Emalayan Vairavanathan svemala...@yahoo.com wrote:
Hi all,
I am implementing a distributed application which runs on 100s of
machines
Just curious, why would you want to store sstables in HDFS?
On 3/23/13 12:43 PM, Amit Kumar kumarami...@gmail.com wrote:
I am starting some work on an input-format that would let us read
sstables stored in HDFS, I wonder if anyone has worked on something
similar before. I did come across
http://www.datastax.com/docs/1.2/index
http://www.datastax.com/docs/1.2/cql_cli/using/alter
The users list might be a better place for this discussion if you need
further help.
On 3/12/13 10:50 AM, Haithem Jarraya haithem.jarr...@struq.com wrote:
Could you please point me to the right syntax
:53, Michael Kjellman mkjell...@barracuda.com wrote:
http://www.datastax.com/docs/1.2/index
http://www.datastax.com/docs/1.2/cql_cli/using/alter
The users list might be a better place for this discussion if you need
further help.
On 3/12/13 10:50 AM, Haithem Jarraya haithem.jarr...@struq.com
You might have more luck on the users list or client-dev.
Best,
Michael
On Mar 7, 2013, at 2:45 AM, Pushkar Prasad
pushkar.pra...@airtightnetworks.net wrote:
I want to insert a lot of rows from a csv file into Cassandra, and I figured
out copy command would not be fast enough. I want to use
This was due to
https://issues.apache.org/jira/browse/CASSANDRA-4366
Should be safe to remove this when running on a you Raspberry Pi as it is
a performance change for the JVM and I guess not supported on whatever
version is supported on your distro for the Pi.
-mike
On 3/4/13 11:17 AM, Andrew
Might want to create a Jira ticket at issues.apache.org instead of submitting
the bug report thru email.
On Mar 2, 2013, at 3:11 AM, Andrew Prendergast a...@andrewprendergast.com
wrote:
*DESCRIPTION*
When creating a table in all ANSI-SQL compliant RDBMS' the VARCHAR datatype
takes a
https://www.google.com
On 2/25/13 3:24 PM, Anton Prakash anton.prak...@cloudtalk.com wrote:
unsubscribe
On Mon, Feb 25, 2013 at 3:23 PM, Brandon Williams dri...@gmail.com
wrote:
On Mon, Feb 25, 2013 at 5:19 PM, Edward Capriolo edlinuxg...@gmail.com
wrote:
I am curious what you mean when
I can promise you it is not a matter of not being interested in performance
enhancements, but there is a trade off between stability, backwards
comparability, etc. Some of the changes you are proposing have merit but they
fundamentally change some decisions that have been made and Jonathan
+1
On 2/20/13 4:01 PM, Sylvain Lebresne sylv...@datastax.com wrote:
We've fixed a fair amount of important fixes since 1.2.1 so I propose the
following artifacts for release as 1.2.2.
sha1: 068b53dd5de928fd80815b54963af796f51f1c38
Git:
Considering that 1.2.1 is out, and looking at your project very quickly (looks
interesting)/overlaps a bit with CCMBridge no?/ I'd def say +1 :)
From: Stephen Connolly
stephen.alan.conno...@gmail.commailto:stephen.alan.conno...@gmail.com
Reply-To:
Discussed in the users list on 1/23/13
http://mail-archives.apache.org/mod_mbox/incubator-cassandra-user/201301.mb
ox/%3c11d9ef3eb41c401880e02e51269ea...@portico.io%3E
On 2/8/13 2:23 PM, Rahman, Muntasir Raihan mrahm...@illinois.edu wrote:
Thanks. I will start from there.
Muntasir.
There seems to be a lot of confusion on this topic in the C* Community.
Most people look at the Datastax docs that recommend Java 6 and ask why
that recommendation is there. Threads never seem to finish with a clear
definitive answer. There seem to be about 3-4 of these for the past few
months on
+1
On Jan 24, 2013, at 11:54 PM, Sylvain Lebresne sylv...@datastax.com wrote:
That list of changes since 1.2.0 is getting pretty long, time to ship that
to
users. I propose the following artifacts for release as 1.2.1.
sha1: 8540974dbd26989b1cd72608b06e57ebe053bf38
Git:
Yikes. Please would be nice..
Also, Sylvian already said they would update the documentation.
As a developer, who hasn't forgotten to update documentation?
On 1/9/13 8:07 AM, Radim Kolar h...@filez.com wrote:
if this was renamed then update your documentation:
101 - 129 of 129 matches
Mail list logo
