In this week's webinar, DataStax Enterprise 5.1: 3X the operational analytics speed, help for multi-tenant SaaS apps, & other shiny things, our awesome Technical Evangelist, David Gilardi and I had the opportunity to give a sneak peek at what's in store in our upcoming April 4th release of DataStax Enterprise 5.1, DataStax OpsCenter 6.1, and DataStax Studio 2.0. Here are the answers to your webinar questions.
The DataStax Graph Loader is an important tool in the development of a DataStax Graph use case. While its primary function is to bulk load data into DSE Graph, it can be a great tool to help you familiarize yourself with some of the in’s and out’s (pun intended) of the DSE Graph.
The previous post introduced DSE Graph and summarized some key considerations related to dealing with large graphs. This post aims to:
describe the tooling available to load large data sets to DSE Graph
point out tips, tricks, and key learnings for bulk loading with DSE Graph Loader
provide code samples to simplify your bulk loading process into DSE Graph
DSE Graph Loader (DGL) is a powerful tool for loading graph data into DSE Graph.
This post is an intro to DSE Graph with a focus on the strategies that should be used to load large graphs with billions of vertices and edges.
Today we released version 3.8.0 of the DataStax Python driver for Apache Cassandra. This release is primarily a bugfix release with no specific area of focus.
I’d love to get your feedback on how you’re either using or planning to use DSE Security. Thanks in advance for the help!
Every now and then we receive the question of why shared storage isn’t recommended for Apache Cassandra™. The conversation usually goes like this:
Customer/User – “We have an awesome SAN and would like to use it for Cassandra.”
DataStax – “We don’t recommend shared storage for Cassandra.”
Customer/User – “Why not.”
DataStax – “Two reasons really.
I’m excited to announce that we added support for promises in the latest version of the DataStax drivers, while continuing to support callback-based execution.