r/and hinted-handoff,
would the original timestamp (the timestamp generated by the coordinator at the
first insert/update) be used or the server will generate another one using its
algorithm, it may explain the behavior.
On Wed, Nov 25, 2015 at 9:36 PM, Ngoc Minh VO
mailto:ngo
value multiplied x2 in multi-datacenter environment
Be sire to include your actual insert statement. Also, what consistency level
was used for the insert (all, quorum, local quorum, one, or...)?
-- Jack Krupansky
On Wed, Nov 25, 2015 at 11:43 AM, Ngoc Minh VO
mailto:ngocminh...@bnpparibas.com
sound like a bug though, worthy of a Jira ticket.
-- Jack Krupansky
On Wed, Nov 25, 2015 at 4:05 AM, Ngoc Minh VO
mailto:ngocminh...@bnpparibas.com>> wrote:
Hello all,
We encounter an issue on our Production environment that cannot be reproduced
on Test environment: list (T = double
015 at 4:05 AM, Ngoc Minh VO
mailto:ngocminh...@bnpparibas.com>> wrote:
Hello all,
We encounter an issue on our Production environment that cannot be reproduced
on Test environment: list (T = double or text) value is randomly
“multiplied” by 2 (i.e. value sent to C*= [a, b, c], value st
Hello all,
We encounter an issue on our Production environment that cannot be reproduced
on Test environment: list (T = double or text) value is randomly
"multiplied" by 2 (i.e. value sent to C*= [a, b, c], value stored in C* = [a,
b, c, a, b, c]).
I know that it sounds weird but we just want
Hello,
The problem with your approach is: you will need to specify all the 30 filters
(in the pre-defined order in PK) when querying.
I would go for this data model:
CREATE TABLE t (
name text,
filter_name1 text, filter_value1 text,
filter_name2 text, filter_value2 text,
filter_n
. Mozdzen [mailto:jmozd...@nde.ag]
Sent: vendredi 16 janvier 2015 17:56
To: user@cassandra.apache.org
Subject: Re: ODBC driver for C* 2.0.xx
Hi Minh,
Zitat von Ngoc Minh VO :
> Hello,
>
> We are trying to connect some BI tools (eg. Tableau) to our NoSQL
> database running C* v2.0.6.
>
Hello,
We are trying to connect some BI tools (eg. Tableau) to our NoSQL database
running C* v2.0.6.
It seems that the latest Datastax's ODBC driver is not compatible with
Cassandra v2.xx (but only with v1.xx, i.e. prior CQL3 era):
http://www.datastax.com/download#dl-datastax-drivers
http://www
Thanks a lot for your answers!
What we plan to do is:
- auto_snapshot = true
- if the human errors happened on D-5:
o we will bring the cluster offline
o purge all data
o import snapshots prior D-5 (and delete snapshots after D-5)
o upload all missing data between D
Hello all,
We are looking for a solution to backup data in our C* cluster (v2.0.x, 16
nodes, 4 x 500GB SSD, RF = 6 over 2 datacenters).
The main purpose is to protect us from human errors (eg. unexpected
manipulations: delete, drop tables, …).
We are thinking of:
- Backup: add a 2TB H
's the price to pay to avoid tombstones and avoid heavy compaction
Regards
Duy Hai DOAN
On Fri, May 2, 2014 at 11:40 AM, Ngoc Minh VO
mailto:ngocminh...@bnpparibas.com>> wrote:
Hello all,
I don’t know whether it is the right place to discuss about data modeling with
Cassandra.
We
Hello all,
I don't know whether it is the right place to discuss about data modeling with
Cassandra.
We would like to have your feedbacks/recommendations on our schema modeling:
1. Our data are stored in a CF by their unique key (K)
2. Data type could be one of the following: Doubl
12 matches
Mail list logo
