vtlim commented on code in PR #14379: URL: https://github.com/apache/druid/pull/14379#discussion_r1222109150
########## docs/design/architecture.md: ########## @@ -107,7 +107,7 @@ example, a single day, if your datasource is partitioned by day). Within a chunk [_segments_](../design/segments.md). Each segment is a single file, typically comprising up to a few million rows of data. Since segments are organized into time chunks, it's sometimes helpful to think of segments as living on a timeline like the following: -<img src="../assets/druid-timeline.png" width="800" /> + Review Comment: ```suggestion  ``` ########## docs/design/architecture.md: ########## @@ -29,7 +29,7 @@ Druid has a distributed architecture that is designed to be cloud-friendly and e The following diagram shows the services that make up the Druid architecture, how they are typically organized into servers, and how queries and data flow through this architecture. -<img src="../assets/druid-architecture.png" width="800"/> + Review Comment: ```suggestion  ``` ########## docs/design/processes.md: ########## @@ -43,7 +43,7 @@ Druid processes can be deployed any way you like, but for ease of deployment we * **Query** * **Data** -<img src="../assets/druid-architecture.png" width="800"/> + Review Comment: ```suggestion  ``` -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
