Does the last_update_date constraint filter out a lot of rows? In that
case the server may be reading a large number of rows, only to throw
them away since they get filtered out.
If you apply the filter on the client side, you shouldn't see timeouts
(but overall the process will be slower sin
Hello Alaa,
Over time, people who tried seems to have failed to do a live migration
from windows to linux (and probably the other way around). It appears to be
something unsupported:
http://grokbase.com/t/cassandra/user/13anrd7qv1/mixed-linux-windows-cluster-
in-cassandra-1-2
http://grokbase.com/
Thanks Alain, yes, I saw some of these, but I was hoping that there are new
experiments.
This is useful, now I need to find new HW to test these options.
Thanks for your help..
Alaa
On Sat, Jan 27, 2018 at 9:04 AM, Alain RODRIGUEZ wrote:
> Hello Alaa,
>
> Over time, people who tried seems to hav
Hi All,
What happens if multiple processes send create table if not exist statement
to cassandra? will there be any data corruption or any other issues if I
send "create table if not exist" request often?
I dont see any entry in system.paxos table so is it fair to say "IF NOT
EXISTS" doesn't auto
It’s not LWT. Don’t do programmatic schema changes that can race, it’s likely
to cause problems
--
Jeff Jirsa
> On Jan 27, 2018, at 10:19 AM, Kant Kodali wrote:
>
> Hi All,
>
> What happens if multiple processes send create table if not exist statement
> to cassandra? will there be any da
Don't do that. Worst case you might get different schemas in flight and no
agreement on your cluster. If you are already doing that, check "nodetool
describecluster" after you do that.
Like Jeff said, it is likely to cause problems.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax C
Schema changes I assume you guys are talking about different create table or
alter table statements. What if multiple threads issue same exact create table
if not exists statement? Will that cause issues?
Sent from my iPhone
> On Jan 27, 2018, at 11:41 AM, Carlos Rolo wrote:
>
> Don't do that
Yes it causes issues
--
Jeff Jirsa
> On Jan 27, 2018, at 12:17 PM, Kant Kodali wrote:
>
> Schema changes I assume you guys are talking about different create table or
> alter table statements. What if multiple threads issue same exact create
> table if not exists statement? Will that cause
May I know why?
Sent from my iPhone
> On Jan 27, 2018, at 12:36 PM, Jeff Jirsa wrote:
>
> Yes it causes issues
>
>
> --
> Jeff Jirsa
>
>
>> On Jan 27, 2018, at 12:17 PM, Kant Kodali wrote:
>>
>> Schema changes I assume you guys are talking about different create table or
>> alter table
Originally we would make tables based on keyspace name / table name pairs,
which was fine unless you dropped a table and recreated it, which could happen
while one node was offline / split network / gc pause. The recreation scenario
could allow data to be resurrected after a drop.
So we augmen
10 matches
Mail list logo