cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Trivial Update of "GettingStarted" by BartonWright
Date Sat, 13 Mar 2010 15:47:53 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "GettingStarted" page has been changed by BartonWright.
The comment on this change is: Minor English fixes..
http://wiki.apache.org/cassandra/GettingStarted?action=diff&rev1=31&rev2=32

--------------------------------------------------

  <<Anchor(picking_a_version)>>
  
  == Step 1: Picking a version ==
- At any given time, there are a number of different versions available for install:
+ At any given time, there are a number of different versions available to install:
  
  === Stable releases ===
  Cassandra stable releases are well tested and reasonably free of serious problems, (or at
least the problems are known and well documented). If you are setting up a production environment,
a stable release is what you want.
@@ -23, +23 @@

  When downloading from a mirror, please be sure to verify the checksums and OpenPGP compatible
signature (see the MD5, SHA1, and PGP links above). The [[http://www.apache.org/dist/incubator/cassandra/KEYS|KEYS]]
file contains the public key(s) used for signing releases.
  
  === Nightly builds ===
- Nightly builds represent the current state of development as of the time of the build. They
contain all of the previous days new features, fixes, and newly introduced bugs. The only
guarantee they come with is that they successfully build and the unit tests pass. Nightly
builds are a handy way of testing recent changes, or accessing the latest features and fixes
not found in beta or release candidates, but there is some risk of them being buggy.
+ Nightly builds represent the current state of development as of the time of the build. They
contain all of the previous day's new features, fixes, and newly introduced bugs. The only
guarantee they come with is that they successfully build and the unit tests pass. Nightly
builds are a handy way of testing recent changes, or accessing the latest features and fixes
not found in beta or release candidates, but there is some risk of them being buggy.
  
  The most recent nightly build can be downloaded [[http://hudson.zones.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/|here]].
  
@@ -37, +37 @@

  == Step 2: Running a single node ==
  Cassandra is meant to run on a cluster of nodes, but will run equally well on a single machine.
This is a handy way of getting familiar with the software while avoiding the complexities
of a larger system.
  
- Since there isn't currently an installation method per se, the easiest solution is to simply
run Cassandra from an extracted archive<<FootNote(Users of Debian or Debian-based derivatives
can install the latest stable release in package form, see DebianPackaging for details)>>
or SVN checkout (see: [[#picking_a_version|Picking a version]]). Also, unless you've downloaded
a binary distribution, you'll need to compile the software by invoking `ant` from the top-level
directory.
+ Since there isn't currently an installation method per se, the easiest solution is to simply
run Cassandra from an extracted archive<<FootNote(Users of Debian or Debian-based derivatives
can install the latest stable release in package form, see DebianPackaging for details.)>>
or SVN checkout (see: [[#picking_a_version|Picking a version]]). Also, unless you've downloaded
a binary distribution, you'll need to compile the software by invoking `ant` from the top-level
directory.
  
  The distribution's sample configuration `conf/storage-conf.xml` contains reasonable defaults
for single node operation, but you will need to make sure that the paths exist for `CommitLogDirectory`,
`DataFileDirectories`, `CalloutLocation`, `BootstrapFileDirectory`, and `StagingFileDirectory`.
Additionally, take a minute now to look over the logging configuration in `conf/log4j.properties`
and make sure that directories exist for the configured log file(s) as well.
  
  Some people running OS X have trouble getting Java 6 to work. If you've kept up with Apple's
updates, Java 6 should already be installed (it comes in Mac OS X 10.5 Update 1). Unfortunately,
Apple does not default to using it. What you have to do is change your `JAVA_HOME` environment
setting to `/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home` and add `/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin`
to the beginning of your `PATH`.
  
- And now for the moment of truth, start up Cassandra by invoking `bin/cassandra -f` from
the command line<<FootNote(To learn more about controlling the behavior of startup scripts,
see RunningCassandra)>>. The service should start in the foreground and log gratuitously
to standard-out. Assuming you don't see messages with scary words like "error", or "fatal",
or anything that looks like a Java stack trace, then chances are you've succeeded. To be certain
though, take some time to try out the examples in CassandraCli and ThriftInterface before
moving on. Also, if you run into problems, Don't Panic, calmly proceed to [[#if_something_goes_wrong|If
Something Goes Wrong]].
+ And now for the moment of truth, start up Cassandra by invoking `bin/cassandra -f` from
the command line<<FootNote(To learn more about controlling the behavior of startup scripts,
see RunningCassandra.)>>. The service should start in the foreground and log gratuitously
to standard-out. Assuming you don't see messages with scary words like "error", or "fatal",
or anything that looks like a Java stack trace, then chances are you've succeeded. To be certain
though, take some time to try out the examples in CassandraCli and ThriftInterface before
moving on. Also, if you run into problems, Don't Panic, calmly proceed to [[#if_something_goes_wrong|If
Something Goes Wrong]].
  
  == Step 3: Running a cluster ==
  Setting up a Cassandra cluster is ''almost'' as simple as repeating [[#running_a_single_node|Step
2]] for each node in your cluster. There are a few minor exceptions though.
@@ -67, +67 @@

  If you don't yet have access to hardware for a Cassandra cluster you can try it out on EC2
with [[Cassandra EC2]].
  
  == Step 4: Write your application ==
- Cassandra uses [[http://incubator.apache.org/thrift/|Thrift]] for it's external client facing
API. Thrift supports a [[http://svn.apache.org/viewvc/incubator/thrift/trunk/lib/|wide variety
of languages]] so you can code your application to use Thrift directly, or use a [[http://wiki.apache.org/cassandra/ClientExamples|high-level
client]] where available. Be sure to read the documentation on the [[http://wiki.apache.org/thrift|Thrift
wiki]], and checkout the Cassandra-specific examples in ClientExamples before getting started.
+ Cassandra uses [[http://incubator.apache.org/thrift/|Thrift]] for its external client-facing
API. Thrift supports a [[http://svn.apache.org/viewvc/incubator/thrift/trunk/lib/|wide variety
of languages]] so you can code your application to use Thrift directly, or use a [[http://wiki.apache.org/cassandra/ClientExamples|high-level
client]] where available. Be sure to read the documentation on the [[http://wiki.apache.org/thrift|Thrift
wiki]], and check out the Cassandra-specific examples in ClientExamples before getting started.
  
- Checking out a demo application like [[http://github.com/ericflo/twissandra|Twissandra]]
(python + django) will also be useful.
+ Checking out a demo application like [[http://github.com/ericflo/twissandra|Twissandra]]
(Python + Django) will also be useful.
  
  <<Anchor(if_something_goes_wrong)>>
  

Mime
View raw message