I've seen now that the DataStax PHP driver (version 1.0.0, the only available
on github) it's only partially compatible with Cassandra 2.1, I used it until
2.2.3, in fact in this one I can't use useful data type like FROZEN or TUPLE.
On the DataStax developer blog that talk about a new beta versi
Thank you Alex for answering.
Yes the columns are dynamic.
The scenario is like this
1) Initial create table with id uuid, name text and insert some data into these
fields
2) Parse an XML from which we retrieve one or more new column names from this
XML
3) check the system.schema_columns if thes
Dear Lorina,
Thank you very much for your answer and to your support team.
I understand why you won't document the special case RF = N = 3. Thank
you for clarifying this special case.
I've found this answer from Marcus Eriksson stating that autocompaction
should be reenabled after the migrati
we want deploy one more data-center for data safe.
As we rebuild one node's data from the old DC, after some hours rebuild failure
due to network fault.
I can restart rebuild surely,but I'm afraid restart rebuild,
is it rebuild all rang of tokens which belong to the node or just rebuild the
rest
Hi Enrico,
As Tyler mentioned, Cassandra 3.0 introduced some major changes to the
system tables, which are critical to the way DataStax drivers work, that
prevented drivers to connect. We are addressing these changes as fast as we
can, but for the PHP driver we need to firstly update the underlyin
> 3) check the system.schema_columns if these column_name(s) exist in the
table
> 4) If the column don't exist in the table "ALTER table tablename add new
column_name text"
Unless you have some external control on this so that you know two
processors will never attempt the same operation within a
Hello,
I have a generic question. How can I initiate a triggering deletion in
cassandra? I mean I need to delete few rows/Partition itself from other tables
based on a status change in another table.
Thanks & Regards,Hari
Hi,
1. What would be the reason for hints getting timed out? None of the nodes
went down. using the storage_port as 7000. System.log displays the below
information:
INFO [HintedHandoff:1] 2015-11-20 14:40:39,400
HintedHandOffManager.java:350 - Started hinted handoff for host:
e57e87c0-b8bf-478
