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.

TOPICS: Big Data

 |  Image 14 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
  • Keyspace added

    Now the dialogs disappear and your keyspace should appear in the list.  At this point we're ready to enter data, but we're going to do that from another tool: the CLI (command line interface) client.

  • The almighty bin folder

    Open up a File Explorer window and head over to the bin folder.  The default location for this folder on a 64-bit Windows machine is C:\Program Files (x86)\DataStax Community\apache-cassandra\bin.  A bunch of important files are here, including the cassandra-cli.bat file, which runs the CLI client, and the cqlsh Python script, which runs the Cassandra Query Language (CQL) Shell.

    Double-click the cassandra-cli.bat file to load the CLI client now.

  • The CLI client

    The CLI client lets you run such commands as USE (to address a specific keyspace) and CREATE COLUMN FAMILY (which is self-explanatory), both of which are shown here.  Make sure to end all commands with a semi-colon.  When you're done, type "exit;" at the prompt (without the quotes) and tap the Enter key.

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


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".