Skip to content

Commit

Permalink
Clearer language around external dependencies in tutorials.
Browse files Browse the repository at this point in the history
  • Loading branch information
gianm committed Jul 14, 2015
1 parent 798c332 commit 183f51f
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions docs/content/tutorials/tutorial-a-first-look-at-druid.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,9 +77,9 @@ You should see a bunch of files:
## External Dependencies

Druid requires 3 external dependencies.
* A "deep storage" that acts as a backup data repository.
* A "metadata storage" such as MySQL to hold configuration and metadata information. Druid uses [Apache Derby](http://db.apache.org/derby/) by default.
* [Apache Zookeeper](http://zookeeper.apache.org/) for coordination among different pieces of the cluster. For this tutorial, we only need the zookeeper dependency.
* A "deep storage" that acts as a data repository. This is generally distributed storage like HDFS or S3. For prototyping or experimentation on a single machine, Druid can use the local filesystem.
* A "metadata storage" to hold configuration and metadata information. This is generally a small, shared database like MySQL or Postgres. For prototyping or experimentation on a single machine, Druid can use a local instance of [Apache Derby](http://db.apache.org/derby/).
* [Apache Zookeeper](http://zookeeper.apache.org/) for coordination among different pieces of the cluster.

#### Set up Zookeeper

Expand Down
6 changes: 3 additions & 3 deletions docs/content/tutorials/tutorial-the-druid-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,9 @@ cd druid-0.7.1

## External Dependencies
Druid requires 3 external dependencies.
* A "deep storage" that acts as a backup data repository.
* A "metadata storage" such as MySQL to hold configuration and metadata information. Druid uses [Apache Derby](http://db.apache.org/derby/) by default.
* [Apache Zookeeper](http://zookeeper.apache.org/) for coordination among different pieces of the cluster. For this tutorial, we only need the zookeeper dependency.
* A "deep storage" that acts as a data repository. This is generally distributed storage like HDFS or S3. For prototyping or experimentation on a single machine, Druid can use the local filesystem.
* A "metadata storage" to hold configuration and metadata information. This is generally a small, shared database like MySQL or Postgres. For prototyping or experimentation on a single machine, Druid can use a local instance of [Apache Derby](http://db.apache.org/derby/).
* [Apache Zookeeper](http://zookeeper.apache.org/) for coordination among different pieces of the cluster.

For deep storage, we will use the local disk in this tutorial, but for production, HDFS and S3 are popular options. For the metadata storage, Derby is used, but for production Mysql or PostgreSQL etc should be used.

Expand Down

0 comments on commit 183f51f

Please sign in to comment.