Re: SASI index creation assertion error

2016-11-04 Thread Jonathan Haddad
Can you file a Jira for this? Would be good to make sure 3.10 doesn't get released with this bug. On Fri, Nov 4, 2016 at 6:11 PM Voytek Jarnot wrote: > Thought I'd follow-up to myself, in case anyone else comes across this > problem. I found a reasonably easy test case

Re: SASI index creation assertion error

2016-11-04 Thread Voytek Jarnot
Thought I'd follow-up to myself, in case anyone else comes across this problem. I found a reasonably easy test case to reproduce the problem: This works in 3.9, but doesn't work in 3.10-snapshot: CREATE KEYSPACE vjtest WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '1'};

SASI index creation assertion error

2016-11-04 Thread Voytek Jarnot
Wondering if anyone has encountered the same... Full story and stacktraces below, short version is that creating a SASI index fails for me when running a 3.10-SNAPSHOT build. One caveat: creating the index on an empty table doesn't fail; however, soon after I start pumping data into the table

Can I monitor Read Repair from the logs

2016-11-04 Thread James Rothering
What should I grep for in the logs to see if read repair is happening on a table?

Re: Commercial Support Providers?

2016-11-04 Thread SmartCat - Scott Hirleman
Other one I've run across is Insight In Data . Pretty flexible and cost effective. Can't speak to how knowledgeable they are but in my small amount of dealings with them, they are easy to work with. On Thu, Nov 3, 2016 at 9:13 PM, Ben Slater

Re: Cassandra on Cloud platforms experience

2016-11-04 Thread Oskar Kjellin
It is good enough if you do not care about automation. If you care about automation (and you really should), GossipPropertyFileSnitch is not good enough as it has to be manually updated. Same with availability set, fault domain isn't available for the instance as metadata as it is on AWS. You

Re: Cassandra on Cloud platforms experience

2016-11-04 Thread Vladimir Yudovin
Hi, 1. No native snitch It's not great problem. GossipPropertyFileSnitch is good enough. 2. No concept of availability zones. Azure does have such concept - Availability Set. It provides three fault domain (availability zone in Amazon terms) and 20 updates domains. 4. Even running SSDs

Re: Using Instants for timestamps in Java mappings?

2016-11-04 Thread Ali Akhtar
This should be added to core On Fri, Nov 4, 2016 at 2:37 PM, DuyHai Doan wrote: > You can: > > 1) Define your own codec : http://datastax.github.io/ > java-driver/manual/custom_codecs/ > 2) Use the InstantCodec from Java drive extra module: https://github.com/ >

Re: Using Instants for timestamps in Java mappings?

2016-11-04 Thread DuyHai Doan
You can: 1) Define your own codec : http://datastax.github.io/java-driver/manual/custom_codecs/ 2) Use the InstantCodec from Java drive extra module: https://github.com/datastax/java-driver/blob/3.x/driver-extras/src/main/java/com/datastax/driver/extras/codecs/jdk8/InstantCodec.java On Fri, Nov

Re: Cassandra on Cloud platforms experience

2016-11-04 Thread Oskar Kjellin
Also, if you're running it on azure you should have a look at Netflix Priam. That really helped us automate stuff. Dynamo db works well if you don't want to spend hours in running your cluster. If I were to have the option to run on AWS I would use Dynamo when possible. Sent from my iPhone

Re: Cassandra on Cloud platforms experience

2016-11-04 Thread Oskar Kjellin
So I've run Cassandra on both Aws and azure. I would strongly suggest that if you have the option, run as far away from azure as you can. Here's a list of issues I have running Cassandra on azure: 1. No native snitch 2. No concept of availability zones. This makes it impossible for Cassandra

Using Instants for timestamps in Java mappings?

2016-11-04 Thread Ali Akhtar
Is it possible to use Instants to represent timestamp columns in java mappings of cassandra tables? (Using the official java driver)

Re: failure node rejoin

2016-11-04 Thread Yuji Ito
Thanks Ben, When I added `nodetool flush` on all nodes after step 2, the problem didn't happen. Did replay from old commit logs delete rows? Perhaps, the flush operation just detected that some nodes were down in step 2 (just after truncating tables). (Insertion and check in step2 would succeed

RE: Backup restore with a different name

2016-11-04 Thread Michael Laws
Hi Jens – I put together a couple of simple scripts a couple of years ago that might do exactly what you need. These leverage nodetool snapshot and sstableloader to create keyspace snapshots, collect up all the necessary SSTable files in an easy-to-move file, rename the keyspace, restore it to