DataStax 1.2 on Windows: A guided tour

DataStax 1.2 on Windows: A guided tour

Summary: Getting the DataStax Community distribution of Cassandra up and running on your local PC is a snap. In this gallery, you'll see that for yourself.

SHARE:
TOPICS: Big Data
1

 |  Image 10 of 19

  • Thumbnail 1
  • Thumbnail 2
  • Thumbnail 3
  • Thumbnail 4
  • Thumbnail 5
  • Thumbnail 6
  • Thumbnail 7
  • Thumbnail 8
  • Thumbnail 9
  • Thumbnail 10
  • Thumbnail 11
  • Thumbnail 12
  • Thumbnail 13
  • Thumbnail 14
  • Thumbnail 15
  • Thumbnail 16
  • Thumbnail 17
  • Thumbnail 18
  • Thumbnail 19
  • OpsCenter Dashboard

    One value-add you get with DataStax Community (versus the vanilla Apache Cassandra bits) is the OpsCenter utility.  Bring it up on your machine by firing up your browser (as long as it's not Internet Explorer, which is unsupported) and navigating to http://localhost:8888.

    Look around the dashboard and then, when you're ready to create a database, click the "DATA MODELING" link on the left nav bar (highlighted).

  • Keyspace inventory

    Keyspaces are the units of replication in Cassandra, but you can also think of them as the rough equivalent of databases.  The Data Modeling screen lists all existing keyspaces and provides an "Add Keyspace" button (highlighted) to add a new one.  Click it now.

  • Add keyspace

    The Add a Keyspace dialog should now pop up.  Enter a name for for your new keyspace, then click the "I would like to create a column family" checkbox (a column family is Cassandra's rough equivalent of a table) and click the "Save Keyspace" button.

Topic: Big Data

Andrew Brust

About Andrew Brust

Andrew J. Brust has worked in the software industry for 25 years as a developer, consultant, entrepreneur and CTO, specializing in application development, databases and business intelligence technology.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories

Talkback

1 comment
Log in or register to join the discussion
  • How Do You Keep It All Up-To-Date?

    Having to run a separate GUI installer for every single package sounds like a scalability nightmare. Including your DBMS, Web server, load balancer, memory cache, scripting languages, scripting language add-ons, Web server add-ons, library dependencies ... that could easily mount up to hundreds of separate installers, which means hundreds of separate updates needing to be managed. On a Linux system, keeping it all-to-date involves little more than typing "apt-get update && apt-get upgrade".
    ldo17