Thank Alok,
I checked in Java and Cassandra handle correctly the case.
But in Java following types are need for this behavior:
java.sql.Timestamp
java.math.BigInteger
com.datastax.driver.core.LocalDate (because java.util.Date and java.sql.Date
not work correctly ...)
Calendar c = new GregorianC
I think this jira
https://issues.apache.org/jira/browse/CASSANDRA-9895
Answer my question
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Fri, Apr 12, 2019 at 10:04 AM Jean Carlo
wrote:
> Hello Sean
>
> Well this is a little bit confusing. After digging
You should be able to use timestamp or date for dates before 1970. Here is an
example
CREATE TABLE test_ts_date (id int, ts timestamp, dt date, value text, PRIMARY
KEY (id, ts));
INSERT INTO test_ts_date (id, ts, dt, value) VALUES (1, '2019-04-11 01:20:30',
'2019-04-11', 'value1');
INSERT INTO
Hi Thomas,
The process you suggested to get around the issue should work with the
system.keyspaces table.
Make sure to backup the original *system.keyspaces* table files on the node
that fails to start. Then, copy only the *system.keyspaces *table files
from a working node into the *system/schema
Hello Sean
Well this is a little bit confusing. After digging into the doc, I found
this old documentation of Datastax that says
"First, we can dynamically adjust behavior depending on the cluster size
and arrangement. Cassandra prefers to perform batchlog writes to two
different replicas in the s
