From 219f33d5b4de73caff5404c3459f6ac9d8c62b0b Mon Sep 17 00:00:00 2001 From: gccgdb1234 Date: Sat, 23 Jul 2022 16:06:12 +0800 Subject: [PATCH] doc: fix picture broken link --- docs/en/07-develop/03-insert-data/05-high-volume.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/07-develop/03-insert-data/05-high-volume.md b/docs/en/07-develop/03-insert-data/05-high-volume.md index f8849a74b3..29a2c82fc7 100644 --- a/docs/en/07-develop/03-insert-data/05-high-volume.md +++ b/docs/en/07-develop/03-insert-data/05-high-volume.md @@ -66,7 +66,7 @@ Below are the scenario for the sample programs of high performance wrting. - Application program maps the received data to different writing threads based on table name to make sure all the data for each table is always processed by a specific writing thread. - Each writing thread writes the received data into TDengine once the message queue becomes empty or the read data meets a threshold. -![Thread Model of High Performance Writing into TDengine](../../../zh/07-develop/03-insert-data/highvolume.webp) +![Thread Model of High Performance Writing into TDengine](highvolume.webp) ### Sample Programs -- GitLab