Hi Rob,
Thanks for sharing the link. I have gone through it and few other documents as
well. Still I am confused. It seems, if we use vnodes and
NetworkTopologyStrategy, we should use a single rack configuration in
Cassandra. Or, it can create hotspots in the ring. Not sure if my understanding
Hi all
As a user of Cassandra, sometimes there are some bugs in my cluster and I
hope someone can fix them (Of course, if I can fix them myself I'll try to
contribute my code :) ). For each bug, there is a JIRA ticket to tracking
it and users can know if the bug is fixed.
However, there is a lag
Hi,
My earlier question was whether it is safe to cache PreparedStatement
(using Java driver) in the client side for which I got it confirmed by
Olivier.
Now the question is do we really need to cache the PreparedStatement in the
client side?.
Lets take a scenario as below:
1) Client fires a RE
As far as I know, the main thing about using NetworkTopologyStrategy
and different racks is replica placement throughout your cluster. That
strategy favours different racks when it comes to choosing where a
row's replica will be placed. So, if you have different numbers of
nodes in each rack, you w
As far as I know there is no such thing. You could make that value a single
PK for the table therefore guaranteeing uniqueness and check on insert with
`IF NOT EXISTS` to prevent dups. Of course that works just for one value,
if you have multiple values a compound PK will still let dups in for a
gi
Hate to be the one to point this out, but that is not the ideal use case
for Cassandra.
If you really want to brute force it and "make it fit" cassandra, the
easiest way is to create a class called Index. The index class would have
name, phone and address fields. The hashcode and equals method wou
I agree with Peter. I typically keep in Cassandra just the data that will
benefit from it's distribution and replication capabilities. Most of the
applications in which I use Cassandra also use a relational DB, so best
tool for the job type of approach.
And for the PK it's implied; some identifier
i second UUID they're your friend
On Sat, Feb 28, 2015 at 10:56 AM, Brian Sam-Bodden wrote:
> I agree with Peter. I typically keep in Cassandra just the data that will
> benefit from it's distribution and replication capabilities. Most of the
> applications in which I use Cassandra also use a re
Thanks a lot for pointing this out! Yes, a workaround would be very much
appreciated, or also an ETA for 2.0.13, so that I could decide whether or
not going for an officially unsupported 2.0.12 to 2.0.11 downgrade, since I
really need that cleanup.
Thanks
On Feb 27, 2015 10:53 PM, "Jeff Wehrwein"
Hi Rob, sorry for the late response, festive season here. cassandra version
is 1.0.8 and thank you, I will read on the READ_STAGE threads.
Jason
On Wed, Feb 18, 2015 at 3:33 AM, Robert Coli wrote:
> On Fri, Feb 13, 2015 at 7:45 PM, Jason Wee wrote:
>
>> I trigger user defined compaction to big
10 matches
Mail list logo
