mirror of https://github.com/apache/druid.git
edited for flow and readability
This commit is contained in:
parent
5ff77dad34
commit
24dbc58cec
|
@ -3,13 +3,13 @@ layout: doc_page
|
|||
---
|
||||
|
||||
# Druid Plumbers
|
||||
The Plumber is the thing that handles generated segments both while they are being generated and when they are "done". This is also technically a pluggable interface and there are multiple implementations, but there are a lot of details handled by the plumber such that it is expected that there will only be a few implementations and only more advanced third-parties will implement their own.
|
||||
The Plumber handles generated segments both while they are being generated and when they are "done". This is also technically a pluggable interface and there are multiple implementations. However, plumbers handle numerous complex details, and therefore an advanced understanding of Druid is recommended before implementing your own.
|
||||
|
||||
|Field|Type|Description|Required|
|
||||
|-----|----|-----------|--------|
|
||||
|type|String|Specifies the type of plumber. Each value will have its own configuration schema, plumbers packaged with Druid are described below.|yes|
|
||||
|
||||
We provide a brief description of the example to exemplify the types of things that are configured on the plumber.
|
||||
The following can be configured on the plumber:
|
||||
|
||||
* `windowPeriod` is the amount of lag time to allow events. This is configured with a 10 minute window, meaning that any event more than 10 minutes ago will be thrown away and not included in the segment generated by the realtime server.
|
||||
* `basePersistDirectory` is the directory to put things that need persistence. The plumber is responsible for the actual intermediate persists and this tells it where to store those persists.
|
||||
|
|
Loading…
Reference in New Issue