INSERT JSON TimeStamp

If Anyone can help for below as i am getting the error effectiveStartDate and effectiveEndDate are TimeStamp INSERT INTO model.RuleSetSchedule JSON ' { "ruleSetName": "BOSTONRATES", "ruleSetId": "829aa84a-4bba-411f-a4fb-38167a987cda", "scheduleId":1, "effectiveStartDate":

Re: INSERT JSON TimeStamp

That is not a valid date in CQL, and JSON does not enforce a specific date format. A correctly formatted date would look something like “2015-01-01 00:00:00”. From: Ashish Soni Reply-To: Date: Monday, September 28, 2015 at 3:51 PM To:

Re: INSERT JSON TimeStamp

Hi Ashish, Most Json parsers expect either a raw long integer value or some version of an iso-8601 date or timestamp. See https://en.wikipedia.org/wiki/ISO_8601 for a good reference. Steve On Mon, Sep 28, 2015 at 1:08 PM, Russell Bradberry wrote: > That is not a valid

Re: DC's versions compatibility

On Mon, Sep 28, 2015 at 5:29 AM, Carlos Alonso wrote: > I have a very old cassandra cluster 1.2.19 and I'm looking to add a new > datacenter to it for analytics purposes in a newer version, let's say > 2.1.8. Will those DC's communicate properly? > As Jonathan suggests : 1)

Re: How to remove huge files with all expired data sooner?

Thanks, Erick, Ken, and Jeff. Erick, I thought about min_threshold. The document says it "Sets the minimum number of SSTables to trigger a minor compaction." I thought removing those large files would be considered a major compaction, and this parameter may not help. Am I wrong? I also

Re: memory usage problem of Metadata.tokenMap.tokenToHost

Besides the others' advice that 2000+ keyspaces might be too much, the latest Java driver (2.0.11) includes an option to disable the Metadata API http://www.datastax.com/dev/blog/datastax-java-driver-2-0-11-released. I'm not sure at this moment if this has been merged into 2.1 already. On Sun,

Re: How to remove huge files with all expired data sooner?

On Sun, Sep 27, 2015 at 11:59 PM, Erick Ramirez wrote: > You should never run `nodetool compact` since this will result in a > massive SSTable that will almost never get compacted out or take a very > long time to get compacted out. > Respectfully disagree. There are

Re: INSERT JSON TimeStamp

You escape single quotes by doubling them. Eg: "condition": "BoardStation ==''Lowell'' ", That is not double quotes arounf ‘lowel’ but in-fact 4 single-quotes, 2 before and 2 after From: Ashish Soni Reply-To: Date: Monday, September 28, 2015 at 4:32 PM To:

Re: How to remove huge files with all expired data sooner?

There’s a seldom discussed parameter called: unchecked_tombstone_compaction The documentation describes the option as follows: True enables more aggressive than normal tombstone compactions. A single SSTable tombstone compaction runs without checking the likelihood of success. Cassandra 2.0.9

Does Cassandra 2.2.1 works with Java 7?

Hi, All, The latest stable release of Cassandra is 2.2.1 and I notice the following line in the "Requirements" section of README.asc comes with the source codes: Java >=1.7 (OpenJDK and Oracle JVMS have been tested) Does this mean that Cassandra 2.2.1 (binary release) can work with Java 7?

Re: How to remove huge files with all expired data sooner?

Hello, You should never run `nodetool compact` since this will result in a massive SSTable that will almost never get compacted out or take a very long time to get compacted out. You are correct that there needs to be 4 similar-sized SSTables for them to get compacted. If you want the expired

Re: Running Cassandra on Java 8 u60..

We are running OpenJDK7 with G1GC and encountered no issues so far. We took the tuning parameters from the Cassandra 3.0 branch. Kind regards, Nathan On Mon, Sep 28, 2015 at 6:25 AM Kevin Burton wrote: > Possibly for existing apps… we’re running G1 for everything except >

Re: Does Cassandra 2.2.1 works with Java 7?

Yes, the target version for 2.2 is 1.7. 2015-09-28 2:23 GMT-04:00 Lu, Boying : > Hi, All, > > > > The latest stable release of Cassandra is 2.2.1 and I notice the following > line in the “Requirements” section of README.asc comes with the source > codes: > > Java >=1.7

DC's versions compatibility

Hi guys. I have a very old cassandra cluster 1.2.19 and I'm looking to add a new datacenter to it for analytics purposes in a newer version, let's say 2.1.8. Will those DC's communicate properly? Regards Carlos Alonso | Software Engineer | @calonso

Re: How to remove huge files with all expired data sooner?

On Mon, Sep 28, 2015 at 2:59 AM, Erick Ramirez wrote: > have many tables like this, and I'd like to reclaim those spaces sooner. > What would be the best way to do it? Should I run "nodetool compact" when I > see two large files that are 2 weeks old? Is there configuration

Re: INSERT JSON TimeStamp

Thanks a Lot , Also i have single quote in JSON but CQL Doesnt Like it even when i escape it * "condition": "BoardStation =='Lowell' ",* *i tried * * "condition": "BoardStation ==\'Lowell\' ",* INSERT INTO model.RuleSetSchedule JSON ' { "ruleSetName": "BOSTONRATES", "ruleSetId":

Re: Running Cassandra on Java 8 u60..

There are plenty of people running huge clusters on G1. On Mon, Sep 28, 2015 at 12:30 AM Nathan Bijnens wrote: > We are running OpenJDK7 with G1GC and encountered no issues so far. We > took the tuning parameters from the Cassandra 3.0 branch. > > Kind regards, > Nathan > >

Re: DC's versions compatibility

No, they won't. Always run the same version across your cluster. On Mon, Sep 28, 2015 at 5:29 AM Carlos Alonso wrote: > Hi guys. > > I have a very old cassandra cluster 1.2.19 and I'm looking to add a new > datacenter to it for analytics purposes in a newer version, let's