From 4114b4902e56d752f29c96f3a73ba9671a601236 Mon Sep 17 00:00:00 2001 From: Himanshu Gupta Date: Mon, 29 Jun 2015 12:17:42 -0500 Subject: [PATCH] fixing the links to doc images --- docs/content/design/design.md | 4 ++-- docs/content/design/indexing-service.md | 2 +- docs/content/design/realtime.md | 2 +- docs/content/design/segments.md | 2 +- .../development/integrating-druid-with-other-technologies.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/content/design/design.md b/docs/content/design/design.md index 109ea876b80..e9fa1fe426e 100644 --- a/docs/content/design/design.md +++ b/docs/content/design/design.md @@ -39,7 +39,7 @@ This separation allows each node to only care about what it is best at. By separ The following diagram shows how queries and data flow through this architecture, and which nodes (and external dependencies, discussed below) are involved: - + All nodes can be run in some highly available fashion, either as symmetric peers in a share-nothing cluster or as hot-swap failover nodes. @@ -51,7 +51,7 @@ Aside from these nodes, there are 3 external dependencies to the system: The following diagram illustrates the cluster's management layer, showing how certain nodes and dependencies help manage the cluster by tracking and exchanging metadata: - + ### Segments and Data Storage diff --git a/docs/content/design/indexing-service.md b/docs/content/design/indexing-service.md index 910448df23c..eac3083bfa0 100644 --- a/docs/content/design/indexing-service.md +++ b/docs/content/design/indexing-service.md @@ -13,7 +13,7 @@ Overlords and middle managers may run on the same node or across multiple nodes Indexing Service Overview ------------------------- -![Indexing Service](../img/indexing_service.png "Indexing Service") +![Indexing Service](../../img/indexing_service.png "Indexing Service")