You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by lu...@apache.org on 2023/12/28 10:24:09 UTC

(doris-website) branch master updated: [blog] Fix website failure building and pics center errors (#378)

This is an automated email from the ASF dual-hosted git repository.

luzhijing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 49003e11633 [blog] Fix website failure building and pics center errors (#378)
49003e11633 is described below

commit 49003e1163320637cfad4d1a34b045e65e2dadc0
Author: KassieZ <13...@users.noreply.github.com>
AuthorDate: Thu Dec 28 18:24:04 2023 +0800

    [blog] Fix website failure building and pics center errors (#378)
---
 ...p-data-reporting-tagging-and-data-lake-analytics.md |  14 +++++++-------
 src/constant/newsletter.data.ts                        |   2 +-
 ...s-speeds-up-data-reporting-data-lake-analytics.jpeg | Bin 0 -> 141039 bytes
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/blog/apache-doris-speeds-up-data-reporting-tagging-and-data-lake-analytics.md b/blog/apache-doris-speeds-up-data-reporting-tagging-and-data-lake-analytics.md
index a42db11e884..916c0c88505 100644
--- a/blog/apache-doris-speeds-up-data-reporting-tagging-and-data-lake-analytics.md
+++ b/blog/apache-doris-speeds-up-data-reporting-tagging-and-data-lake-analytics.md
@@ -7,7 +7,7 @@
     'tags': ['Best Practice'],
     'picked': "true",
     'order': "1",
-    "image": 'https://cdn.selectdb.com/static/apache_doris_speeds_up_data_reporting_tagging_and_data_lake_analytics_87a6746df5.png'
+    "image": '/static/images/apache-doris-speeds-up-data-reporting-data-lake-analytics.jpeg'
 }
 
 ---
@@ -43,19 +43,19 @@ Before migrating to Apache Doris, they used ClickHouse, MySQL, and Elasticsearch
 
 Data reporting is one of the major services they provide to their customers and they are bound by an SLA. They used to support such service with a combination of ClickHouse and MySQL, but they found significant fluctuations in their data synchronization duration, making it hard for them to meet the service levels outlined in their SLA. Diagnosis showed that it was because the multiple components add to the complexity and instability of data synchronization tasks. To fix that, they have u [...]
 
-<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/from_clickhouse_mysql_to_apache_doris_6387c0363a.png" alt="from-clickhouse-mysql-to-apache-doris" width="840"/></div >
+<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/from_clickhouse_mysql_to_apache_doris_6387c0363a.png" alt="from-clickhouse-mysql-to-apache-doris" width="840" style={{display: 'inline-block'}} /></div >
 
 ### Performance improvements
 
 With Apache Doris, they ingest data via the [Broker Load](https://doris.apache.org/docs/1.2/data-operate/import/import-way/broker-load-manual) method and reach an SLA compliance rate of over 99% in terms of data synchronization performance.
 
-<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/data_synchronization_size_and_duration_327e4dc1fe.png" alt="data-synchronization-size-and-duration" width="640"/></div >
+<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/data_synchronization_size_and_duration_327e4dc1fe.png" alt="data-synchronization-size-and-duration" width="640" style={{display: 'inline-block'}} /></div >
 
 As for data queries, the Doris-based architecture maintains an **average query response time** of less than **10s** and a **P90 response time** of less than **30s**. This is a 50% speedup compared to the old architecture. 
 
-<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/average_query_response_time_372d71ef16.png" alt="average-query-response-time" width="840"/></div >
+<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/average_query_response_time_372d71ef16.png" alt="average-query-response-time" width="840" style={{display: 'inline-block'}} /></div >
 
-<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/query_response_time_percentile_756c6f6a71.png" alt="query-response-time-percentile" width="840"/></div >
+<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/query_response_time_percentile_756c6f6a71.png" alt="query-response-time-percentile" width="840" style={{display: 'inline-block'}} /></div >
 
 ## Tagging
 
@@ -66,7 +66,7 @@ In the old processing architecture where Elasticsearch was the processing engine
 - Any problematic data in any of the tags could spoil the entire merging operation and thus interrupt the data services.
 - The merging operation was implemented based on Spark and MapReduce and took up to 4 hours. Such a long time frame could encroach on marketing opportunities and lead to unseen losses.
 
-<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/tagging_services_3263e21c36.png" alt="tagging-services" width="840"/></div >
+<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/tagging_services_3263e21c36.png" alt="tagging-services" width="840" style={{display: 'inline-block'}} /></div >
 
 Then Apache Doris takes this over. Apache Doris arranges tag data with its data models, which process data fast and smoothly. The aforementioned merging step can be done by the [Aggregate Key model](https://doris.apache.org/docs/data-table/data-model#aggregate-model), which aggregates tag data based on the specified Aggregate Key upon data ingestion. The [Unique Key model](https://doris.apache.org/docs/data-table/data-model#unique-model) is handy for partial column updates. Again, all yo [...]
 
@@ -86,7 +86,7 @@ The user introduces Compute Nodes into their cluster and deploys them with other
 
 For easier deployment, they have also optimized their Deploy on Yarn process via Skein. As is shown below, they define the number of Compute nodes and the required resources in the YAML file, and then pack the installation file, configuration file, and startup script into the distributed file system. In this way, they can start or stop the entire cluster of over 100 nodes within minutes using one simple line of code.
 
-<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/skein_3516ba1a83.png" alt="skein" width="560"/></div >
+<div style={{textAlign:'center'}}><img src="https://cdn.selectdb.com/static/skein_3516ba1a83.png" alt="skein" width="560" style={{display: 'inline-block'}} /></div >
 
 ## Conclusion
 
diff --git a/src/constant/newsletter.data.ts b/src/constant/newsletter.data.ts
index 39c8b35a55c..2ac92e0315c 100644
--- a/src/constant/newsletter.data.ts
+++ b/src/constant/newsletter.data.ts
@@ -4,7 +4,7 @@ export const NEWSLETTER_DATA = [
         title: 'Apache Doris speeds up data reporting, tagging, and data lake analytics',
         content: `The user leverages the capabilities of Apache Doris in reporting, customer tagging, and data lake analytics and achieves high performance.`,
         to: '/blog/apache-doris-speeds-up-data-reporting-tagging-and-data-lake-analytics',
-        image: 'https://cdn.selectdb.com/static/apache_doris_speeds_up_data_reporting_tagging_and_data_lake_analytics_87a6746df5.png',
+        image: '/static/images/apache-doris-speeds-up-data-reporting-data-lake-analytics.jpeg',
     },
     {
         tags: ['Top News'],
diff --git a/static/images/apache-doris-speeds-up-data-reporting-data-lake-analytics.jpeg b/static/images/apache-doris-speeds-up-data-reporting-data-lake-analytics.jpeg
new file mode 100644
index 00000000000..18bf536e55f
Binary files /dev/null and b/static/images/apache-doris-speeds-up-data-reporting-data-lake-analytics.jpeg differ


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org