Refactored modules section for better flow/readability and added link to extending druid

This commit is contained in:
Igal Levy 2013-12-09 16:08:14 -08:00
parent 0e3378e5cd
commit 19be4f8bb0
1 changed files with 3 additions and 1 deletions

View File

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