SELECT JSON timestamp lacks timezone information

Hello all, When I select a timestamp as JSON from Cassandra, the string representation lacks the timezone information, both via CQLSH and the Java Driver: cqlsh:events> select toJson(created_at) AS created_at from event_by_patient_timestamp ; created_at --- "2016-01-0

Re: SELECT JSON timestamp lacks timezone information

Hello Ralf, First of all, Cassandra stores timestamps without timezone information, so it's not possible to retrieve the original timezone used when inserting the value. CQLSH uses the python driver behind the scenes, and my guess is that the timestamp formatting is being done driver-side – hence

Re: SELECT JSON timestamp lacks timezone information

Hi Alexandre. I wrote to ‘user@cassandra.apache.org’. Re the actual problem: I am aware of the fact that C* does not store (need not store) the timezone as it is persisted as a Unix epoche timestamp. Not delivering a timezone in the JSON text representation would be OKish if the text represent

Re: SELECT JSON timestamp lacks timezone information

Sorry, I mistakenly thought that we were on the Java driver mailing list, my apologies. I also think you should definitely file a Jira ticket and ask JSON timestamps generated server-side to be 1) formatted with a format that mentions the timezone and 2) formatted preferably with UTC, not the JVM

On-disk size comparison test steps

Hi, I'm trying to compare the on-disk storage required for a column storing the same content but with two data types (text and blob) for key and value. These are defined in separate tables and same data is inserted to both. The table with blob has STCS and SnappyCompressor, while the one with text

[RELEASE] Apache Cassandra 2.1.13 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.1.13. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

Re: [RELEASE] Apache Cassandra 2.1.13 released

Apologies I send the wrong changelog and news links. Here are the correct ones for 2.1.13 http://goo.gl/9ZPnNX (CHANGES.txt) http://goo.gl/5cR7eh (NEWS.txt) On Mon, Feb 8, 2016 at 9:19 AM, Jake Luciani wrote: > The Cassandra team is pleased to announce the release of Apache Cassandra > versi

[RELEASE] Apache Cassandra 2.2.5 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.5. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

RE: [RELEASE] Apache Cassandra 2.2.5 released

@Kishore to unsubscribe, mail to : dev-unsubscr...@cassandra.apache.org -Message d'origine- De : Kishore babu [mailto:kish...@suntelematics.com] Envoyé : lundi 8 février 2016 16:35 À : d...@cassandra.apache.org; Jake Luciani; user; d...@cassandra.apache.org Objet : Re: [RELEASE] Apache

specifying listen_address

Hi, I downloaded and expanded DSE 4.8.4 When I specify the following in resources/dse/conf/dse.yaml : listen_address: XX.YY I got: INFO 17:43:10 Loading settings from file:/home/cassandra/dse-4.8.4/resources/dse/conf/dse.yaml Exception in thread "main" java.lang.ExceptionInInitializerError at

Re: specifying listen_address

Hi Ted, Are you sure the path to yaml is correct? For me(DSE 4.8.4) it is /etc/dse/cassandra/cassandra.yaml On Mon, Feb 8, 2016 at 11:22 PM, Ted Yu wrote: > Hi, > I downloaded and expanded DSE 4.8.4 > > When I specify the following in resources/dse/conf/dse.yaml : > > listen_address: XX.YY > >

Re: specifying listen_address

I didn't start cassandra as service. I am starting as stand-alone process. Is multiple node setup not supported in stand-alone mode ? Caused by: org.yaml.snakeyaml.error.YAMLException: Unable to find property 'cluster_name' on class: com.datastax.bdp.config.Config at org.yaml.snakeyaml.introspect

Scenarios which need Repair

Hi, Setup: We are on 2.0.14. We have some deployments with just one DC(RF:3) while others with two DCs (RF:3,RF:3). We ALWAYS use LOCAL_QUORUM for both Reads and Writes. Scenario: - We used to run nodetool repair on all tables every gc_grace_seconds. Recently, we decided to id

Re: specifying listen_address

In either case, these properties should be placed in cassandra.yaml file rather than dse.yaml. You can find it in /resources/cassandra/conf directory. On Mon, Feb 8, 2016 at 11:41 PM, Ted Yu wrote: > I didn't start cassandra as service. > > I am starting as stand-alone process. Is multiple node

CASSANDRA-8072

Hi, I am trying to setup a cluster with DSE 4.8.4 I added the following in resources/cassandra/conf/cassandra.yaml : cluster_name: 'cass' which resulted in: http://pastebin.com/27adxKTM This seems to be resolved by CASSANDRA-8072 My question is whether there is workaround ? If not, when can I

Writing a large blob returns WriteTimeoutException

Hi to all, I'm trying to put a large binary file (> 500MB) on a C* cluster as fast as I can but I get some (many) WriteTimeoutExceptions. I created a small POC that isolates the problem I'm facing. Here you will find the code: https://github.com/giampaolotrapasso/cassandratest, *Main details abo

Re: CASSANDRA-8072

Hi Ted, Have you specified the listen_address and rpc_address? What addresses are there in the seed list? Have you started seed first and after waiting for 30 seconds started other nodes? On Tue, Feb 9, 2016 at 12:14 AM, Ted Yu wrote: > Hi, > I am trying to setup a cluster with DSE 4.8.4 > >

Re: CASSANDRA-8072

The issue I described was observed on the seed node. Both rpc_address and listen_address point to localhost. bq. What addresses are there in the seed list? The IP of the seed node. I haven't come to starting non-seed node(s) yet. Thanks for the quick response. On Mon, Feb 8, 2016 at 10:50 AM,

Re: CASSANDRA-8072

could you paste your cassandra.yaml here, except for commented out lines? On Tue, Feb 9, 2016 at 12:30 AM, Ted Yu wrote: > The issue I described was observed on the seed node. > > Both rpc_address and listen_address point to localhost. > > bq. What addresses are there in the seed list? > > The I

Re: CASSANDRA-8072

Here it is: http://pastebin.com/QEdjtAj6 XX.YY is localhost in this case. On Mon, Feb 8, 2016 at 11:03 AM, Bhuvan Rawal wrote: > could you paste your cassandra.yaml here, except for commented out lines? > > On Tue, Feb 9, 2016 at 12:30 AM, Ted Yu wrote: > >> The issue I described was observed

Can we set TTL on individual fields (columns) using the Datastax java-driver

Something like :: ## class A { @Id @Column (name = "pojo_key") int key; @Ttl(10) @Column (name = "pojo_temporary_guest") String guest; } ## When I persist, let's say value "ajay" in guest-field (pojo_

Re: CASSANDRA-8072

Your config looks fine to me, i tried reproducing the scenario by setting localhost in listen_address,rpc_address and seed list, and it worked fine, I had earlier the node local ip in the 3 fields and it was working fine. Looks like there is some other issue here. On Tue, Feb 9, 2016 at 12:49 AM

Latest stable release

We are starting a new project in Cassandra. Is 3.2 stable enough to be used in production. If not, which is the most stable version in 2.x. thanks.

Re: Can we set TTL on individual fields (columns) using the Datastax java-driver

I think you should direct your request to the java driver mailing list: https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user To answer your question, no, there is no @Ttl annotation on the driver-mapping module, even in the latest release: https://github.com/datastax/java-

Re: Latest stable release

I honestly go with 2.1.13 unless you need the features on 2.2.x. I would not recommend 3.x for now (unless you need the features). Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Linked

Re: Latest stable release

We're having good luck running 3.2.1 in production, but ours is a small cluster and we're very new at this. :) ___ Will Hayworth Developer, Engagement Engine Atlassian My pronoun is "they". On Mon, Feb 8, 2016 at

Re: CASSANDRA-8072

If I apply the fix from CASSANDRA-8072 onto a 2.1.12 cluster, which files should I replace ? Thanks On Mon, Feb 8, 2016 at 1:07 PM, Bhuvan Rawal wrote: > Your config looks fine to me, i tried reproducing the scenario by setting > localhost in listen_address,rpc_address and seed list, and it wo

Re: Latest stable release

2.1.x and 2.2.x are certainly stable, but... they will only be supported until November. The new tick-tock release strategy is designed to ensure stability. 3.3, which is (non-critical) bug fixes to 3.2, should be out shortly (vote in progress.) 3.4, with features such as SASI, will probably be out

Re: Cassandra Collections performance issue

Hello all, Recently we added one of the table fields from as Map in Cassandra 2.1.11. Currently we read every field from Map and overwrite map values. Map is of size 3. We saw that writes are 30-40% slower while reads are 70-80% slower. Please find below some metrics that can help. My question

Re: Writing a large blob returns WriteTimeoutException

You appear to be writing the entire bob on each chunk rather than the slice of the blob. -- Jack Krupansky On Mon, Feb 8, 2016 at 1:45 PM, Giampaolo Trapasso < giampaolo.trapa...@radicalbit.io> wrote: > Hi to all, > > I'm trying to put a large binary file (> 500MB) on a C* cluster as fast as > I

Re: Writing a large blob returns WriteTimeoutException

I write at every step MyConfig.blobsize number of bytes, that I configured to be from 10 to 100. This allows me to "simulate" the writing of a 600Mb file, as configuration on github ( https://github.com/giampaolotrapasso/cassandratest/blob/master/src/main/resources/application.conf *)* G

Re: Writing a large blob returns WriteTimeoutException

The "if not exists" in your INSERT means that you are incurring a performance hit by using Paxos. Do you need that? Have you tried your test without it? Jim

Re: CASSANDRA-8072

CASSANDRA-8072 is not going to help you because the code that fails (checkForEndpointCollision()) should not execute for seeds. I think the problem is that there are no seeds in cassandra.yaml: - seeds: "XX.YY" If listen_address is localhost then try: - seeds: "127.0.0.1" On Tue, Feb 9, 2016

Re: Writing a large blob returns WriteTimeoutException

I'm a little lost now. Where are you specifying chunk size, which is what should be varying, as opposed to blob size? And what exactly is the number of records? Seems like you should be computing number of chunks from blob size divided by chunk size. And it still seems like you are writing the same

Re: Writing a large blob returns WriteTimeoutException

Sorry Jack for my poor description, I write 600 times the same array of 1M of bytes to make my life easier. This allows me to simulate a 600Mb file. It's just a simplification. Instead of generating 600Mb random array (or reading a real 600Mb file), and dividing it into 600 chunks, I write the same

Re: CASSANDRA-8072

Thanks for the help, Stefania. By using "127.0.0.1" , I was able to start Cassandra on that seed node (XX.YY). However, on other nodes, I pointed seed to XX.YY and observed the following ? What did I miss ? INFO [main] 2016-02-08 16:44:56,607 OutboundTcpConnection.java:97 - OutboundTcpConnectio

Re: Writing a large blob returns WriteTimeoutException

Bucket size is not disclosed. My recommendation is that partitions not be more than about 10 MB (some people say 100MB or 50MB.) I think I'd recommend a smaller chunk size, like 128K or 256K. I would note that Mongo's GridFS uses 256K chunks. I don't know enough about the finer nuances of Cassand

Re: SELECT JSON timestamp lacks timezone information

It's cqlsh that converts timestamps to UTC and adds the timezone but for JSON it can't do that because the conversion to JSON is done by Cassandra. I've filed https://issues.apache.org/jira/browse/CASSANDRA-11137 to discuss further. On Mon, Feb 8, 2016 at 7:53 PM, Alexandre Dutra < alexandre.du..

Re: Cassandra Collections performance issue

On Mon, Feb 8, 2016 at 2:10 PM, Agrawal, Pratik wrote: > Recently we added one of the table fields from as Map in > *Cassandra > 2.1.11*. Currently we read every field from Map and overwrite map values. > Map is of size 3. We saw that writes are 30-40% slower while reads are > 70-80% slower. Ple

Re: Writing a large blob returns WriteTimeoutException

"If not exists" was an oversight of a previous test. Removing it solved the problem. Thanks a lot, Jim! giampaolo 2016-02-09 1:21 GMT+01:00 Jim Ancona : > The "if not exists" in your INSERT means that you are incurring a > performance hit by using Paxos. Do you need that? Have you tried your tes

Re: CASSANDRA-8072

Have you checked that you can telnet from one node to the other using the same ip and the internode port? I would put the public IP addresses of the seeds in the seed list and set the listen address to the public IP address for each node. There was a similar discussion