Re: SASI index creation assertion error

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 to reproduce the problem:

Re: SASI index creation assertion error

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'}; us

SASI index creation assertion error

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 simi

Can I monitor Read Repair from the logs

What should I grep for in the logs to see if read repair is happening on a table?

Re: Commercial Support Providers?

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 wrote: > I can confirm that

Re: Cassandra on Cloud platforms experience

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 stil

Re: Cassandra on Cloud platforms experience

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 SS

Re: Using Instants for timestamps in Java mappings?

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/ > datastax/java-driver/blob/3.x/dri

Re: Using Instants for timestamps in Java mappings?

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 4

Re: Cassandra on Cloud platforms experience

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

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 to

Using Instants for timestamps in Java mappings?

Is it possible to use Instants to represent timestamp columns in java mappings of cassandra tables? (Using the official java driver)