From 19be4f8bb0217ecee986d30f59c15b38e5263281 Mon Sep 17 00:00:00 2001 From: Igal Levy Date: Mon, 9 Dec 2013 16:08:14 -0800 Subject: [PATCH] Refactored modules section for better flow/readability and added link to extending druid --- docs/content/Configuration.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/content/Configuration.md b/docs/content/Configuration.md index 1934b941bc3..47c495f0142 100644 --- a/docs/content/Configuration.md +++ b/docs/content/Configuration.md @@ -16,7 +16,9 @@ There are three JVM parameters that we set on all of our processes: ## Modules -As of Druid v0.6, most core Druid functionality has been compartmentalized into modules. There are a set of default modules that may apply to any node type, and there are specific modules for the different node types. Default modules are __lazily instantiated__. Each module has its own set of configuration. This page will describe the configuration of the default modules. +As of Druid v0.6, most core Druid functionality has been compartmentalized into modules. There are a set of default modules that may apply to any node type, and there are specific modules for the different node types. Default modules are __lazily instantiated__. Each module has its own set of configuration. + +This page describes the configuration of the default modules. Node-specific configuration is discussed on each node's respective page. In addition, you can add custom modules to [extend Druid](Modules.html). Configuration of the various modules is done via Java properties. These can either be provided as `-D` system properties on the java command line or they can be passed in via a file called `runtime.properties` that exists on the classpath.