jon-wei commented on a change in pull request #8311: Docusaurus build framework 
+ ingestion doc refresh.
URL: https://github.com/apache/incubator-druid/pull/8311#discussion_r315450244
 
 

 ##########
 File path: docs/design/processes.md
 ##########
 @@ -88,18 +88,30 @@ Within a Data server, functionality is split between two 
processes, the Historic
 
 ### Historical process
 
-[**Historical**](../design/historical.html) processes are the workhorses that 
handle storage and querying on "historical" data
+[**Historical**](../design/historical.md) processes are the workhorses that 
handle storage and querying on "historical" data
 (including any streaming data that has been in the system long enough to be 
committed). Historical processes
 download segments from deep storage and respond to queries about these 
segments. They don't accept writes.
 
 ### Middle Manager process
 
-[**MiddleManager**](../design/middlemanager.html) processes handle ingestion 
of new data into the cluster. They are responsible
+[**MiddleManager**](../design/middlemanager.md) processes handle ingestion of 
new data into the cluster. They are responsible
 for reading from external data sources and publishing new Druid segments.
 
 #### Peon processes
 
-[**Peon**](../design/peons.html) processes are task execution engines spawned 
by MiddleManagers. Each Peon runs a separate JVM and is responsible for 
executing a single task. Peons always run on the same host as the MiddleManager 
that spawned them.
+[**Peon**](../design/peons.md) processes are task execution engines spawned by 
MiddleManagers. Each Peon runs a separate JVM and is responsible for executing 
a single task. Peons always run on the same host as the MiddleManager that 
spawned them.
+
+### Indexer process (optional)
+
+[**MiddleManager**](../design/indexer.md) processes are an alternative to 
MiddleManagers and Peons. Instead of
 
 Review comment:
   MiddleManager -> Indexer

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to