This is an automated email from the ASF dual-hosted git repository.
zykkk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git
The following commit(s) were added to refs/heads/master by this push:
new 846d6edab8 [docs](docs) Rename Advanced Usage Files for SEO (#22511)
846d6edab8 is described below
commit 846d6edab82a1ec4d9d94d5e75fae6e1c5d750c6
Author: KassieZ <[email protected]>
AuthorDate: Fri Aug 4 19:33:57 2023 +0800
[docs](docs) Rename Advanced Usage Files for SEO (#22511)
---
docs/en/docs/advanced/best-practice/compaction.md | 4 ++--
docs/en/docs/advanced/best-practice/debug-log.md | 4 ++--
docs/en/docs/advanced/best-practice/import-analysis.md | 2 +-
docs/en/docs/advanced/best-practice/query-analysis.md | 6 +++---
docs/en/docs/advanced/cache/partition-cache.md | 16 ++++++++--------
.../{cold_hot_separation.md => cold-hot-separation.md} | 6 +++---
.../docs/advanced/{compute_node.md => compute-node.md} | 8 ++++----
docs/en/docs/advanced/lateral-view.md | 4 ++--
docs/en/docs/advanced/orthogonal-bitmap-manual.md | 4 ++--
docs/en/docs/advanced/orthogonal-hll-manual.md | 4 ++--
docs/en/docs/advanced/partition/table-temp-partition.md | 4 ++--
docs/en/docs/advanced/resource.md | 2 +-
docs/en/docs/advanced/sql-mode.md | 4 ++--
docs/en/docs/advanced/time-zone.md | 4 ++--
docs/en/docs/advanced/using-hll.md | 2 +-
docs/sidebars.json | 4 ++--
.../{cold_hot_separation.md => cold-hot-separation.md} | 0
.../docs/advanced/{compute_node.md => compute-node.md} | 0
18 files changed, 39 insertions(+), 39 deletions(-)
diff --git a/docs/en/docs/advanced/best-practice/compaction.md
b/docs/en/docs/advanced/best-practice/compaction.md
index 5168b38dab..e48756b57e 100644
--- a/docs/en/docs/advanced/best-practice/compaction.md
+++ b/docs/en/docs/advanced/best-practice/compaction.md
@@ -32,7 +32,7 @@ Doris writes data through a structure similar to LSM-Tree,
and continuously merg
Appropriately adjusting the compaction strategy can greatly improve load and
query efficiency. Doris provides the following two compaction strategies for
tuning:
-## Vertical compaction
+## Vertical Compaction
<version since="1.2.2">
</version>
@@ -47,7 +47,7 @@ BE configuration：
- `vertical_compaction_max_segment_size` is used to configure the size of the
disk file after vertical compaction, the default value is 268435456 (bytes)
-## Segment compaction
+## Segment Compaction
Segment compaction mainly deals with the large-scale data load. Segment
compaction operates during the load process and compact segments inside the
job, which is different from normal compaction and vertical compaction. This
mechanism can effectively reduce the number of generated segments and avoid the
-238 (OLAP_ERR_TOO_MANY_SEGMENTS) errors.
diff --git a/docs/en/docs/advanced/best-practice/debug-log.md
b/docs/en/docs/advanced/best-practice/debug-log.md
index c85627f7cd..7ad99359e8 100644
--- a/docs/en/docs/advanced/best-practice/debug-log.md
+++ b/docs/en/docs/advanced/best-practice/debug-log.md
@@ -33,7 +33,7 @@ The system operation logs of Doris's FE and BE nodes are at
INFO level by defaul
>Enable DEBUG log may cause a large number of logs to be generated, **Please
>be careful to open it in production environment**.
-## Enable FE Debug log
+## Enable FE Debug Log
The Debug level log of FE can be turned on by modifying the configuration
file, or it can be turned on at runtime through the interface or API.
@@ -101,7 +101,7 @@ The Debug level log of FE can be turned on by modifying the
configuration file,
The `del_verbose` parameter specifies the package or class name for which
to turn off Debug logging.
-## Enable BE Debug log
+## Enable BE Debug Log
BE's Debug log currently only supports modifying and restarting the BE node
through the configuration file to take effect.
diff --git a/docs/en/docs/advanced/best-practice/import-analysis.md
b/docs/en/docs/advanced/best-practice/import-analysis.md
index 967e21a38a..95fc1c3ace 100644
--- a/docs/en/docs/advanced/best-practice/import-analysis.md
+++ b/docs/en/docs/advanced/best-practice/import-analysis.md
@@ -31,7 +31,7 @@ Doris provides a graphical command to help users analyze a
specific import more
> This function is currently only for Broker Load analysis.
-## Import plan tree
+## Import Plan Tree
If you don't know much about Doris' query plan tree, please read the previous
article [DORIS/best practices/query analysis](./query-analysis.md).
diff --git a/docs/en/docs/advanced/best-practice/query-analysis.md
b/docs/en/docs/advanced/best-practice/query-analysis.md
index f220cce6c9..f1ae9865c2 100644
--- a/docs/en/docs/advanced/best-practice/query-analysis.md
+++ b/docs/en/docs/advanced/best-practice/query-analysis.md
@@ -29,7 +29,7 @@ under the License.
Doris provides a graphical command to help users analyze a specific query or
import more easily. This article describes how to use this feature.
-## query plan tree
+## Query Plan Tree
SQL is a descriptive language, and users describe the data they want to get
through a SQL. The specific execution mode of a SQL depends on the
implementation of the database. The query planner is used to determine how the
database executes a SQL.
@@ -93,7 +93,7 @@ As shown above, we divided the stand-alone plan into two
Fragments: F1 and F2. D
And a Fragment will be further divided into multiple Instances. Instance is
the final concrete execution instance. Dividing into multiple Instances helps
to make full use of machine resources and improve the execution concurrency of
a Fragment.
-## View query plan
+## View Query Plan
You can view the execution plan of a SQL through the following three commands.
@@ -466,7 +466,7 @@ mysql> explain verbose select tbl1.k1, sum(tbl1.k2) from
tbl1 join tbl2 on tbl1.
> The information displayed in the query plan is still being standardized and
> improved, and we will introduce it in detail in subsequent articles.
-## View query Profile
+## View Query Profile
The user can open the session variable `is_report_success` with the following
command:
diff --git a/docs/en/docs/advanced/cache/partition-cache.md
b/docs/en/docs/advanced/cache/partition-cache.md
index c4d0bf0394..25e5ddd4de 100644
--- a/docs/en/docs/advanced/cache/partition-cache.md
+++ b/docs/en/docs/advanced/cache/partition-cache.md
@@ -26,7 +26,7 @@ under the License.
# Partition Cache
-## Demand scenario
+## Demand Scenarios
In most data analysis scenarios, write less and read more. Data is written
once and read frequently. For example, the dimensions and indicators involved
in a report are calculated at one time in the early morning, but there are
hundreds or even thousands of times every day. page access, so it is very
suitable for caching the result set. In data analysis or BI applications, the
following business scenarios exist:
@@ -50,7 +50,7 @@ This partitioned caching strategy can solve the above
problems, giving priority
- Implemented two caching strategies, SQLCache and PartitionCache, the latter
has a finer cache granularity
- Use consistent hashing to solve the problem of BE nodes going online and
offline. The caching algorithm in BE is an improved LRU
-## SQLCache
+## SQL Cache
SQLCache stores and retrieves the cache according to the SQL signature, the
partition ID of the queried table, and the latest version of the partition. The
combination of the three determines a cached data set. If any one changes, such
as SQL changes, such as query fields or conditions are different, or the
version changes after the data is updated, the cache will not be hit.
@@ -58,7 +58,7 @@ If multiple tables are joined, use the latest updated
partition ID and the lates
SQLCache is more suitable for T+1 update scenarios. Data is updated in the
early morning. The results obtained from the BE for the first query are put
into the cache, and subsequent identical queries are obtained from the cache.
Real-time update data can also be used, but there may be a problem of low hit
rate. You can refer to the following PartitionCache.
-## PartitionCache
+## Partition Cache
### Design Principles
@@ -147,15 +147,15 @@ Partition cache is suitable for partitioning by date,
some partitions are update
Partition fields can also be other fields, but need to ensure that only a
small number of partition updates.
-### Some restrictions
+### Some Restrictions
- Only OlapTable is supported, other tables such as MySQL have no version
information and cannot sense whether the data is updated
- Only supports grouping by partition field, does not support grouping by
other fields, grouping by other fields, the grouped data may be updated, which
will cause the cache to be invalid
- Only the first half of the result set, the second half of the result set and
all cache hits are supported, and the result set is not supported to be divided
into several parts by the cached data
-## How to use
+## How to Use
-### Enable SQLCache
+### Enable SQL Cache
Make sure cache_enable_sql_mode=true in fe.conf (default is true)
@@ -172,7 +172,7 @@ MySQL [(none)]> set [global] enable_sql_cache=true;
Note: global is a global variable, not referring to the current session
variable
-### Enable PartitionCache
+### Enable Partition Cache
Make sure cache_enable_partition_mode=true in fe.conf (default is true)
@@ -226,7 +226,7 @@ Partition average data size = cache_memory_total /
cache_partition_total
Other monitoring: You can view the CPU and memory indicators of the BE node,
the Query Percentile and other indicators in the Query statistics from Grafana,
and adjust the Cache parameters to achieve business goals.
-### Optimization parameters
+### Optimization Parameters
The configuration item cache_result_max_row_count of FE, the maximum number of
rows in the cache for the query result set, can be adjusted according to the
actual situation, but it is recommended not to set it too large to avoid taking
up too much memory, and the result set exceeding this size will not be cached.
diff --git a/docs/en/docs/advanced/cold_hot_separation.md
b/docs/en/docs/advanced/cold-hot-separation.md
similarity index 98%
rename from docs/en/docs/advanced/cold_hot_separation.md
rename to docs/en/docs/advanced/cold-hot-separation.md
index 8509abd35f..7b954c577b 100644
--- a/docs/en/docs/advanced/cold_hot_separation.md
+++ b/docs/en/docs/advanced/cold-hot-separation.md
@@ -1,6 +1,6 @@
---
{
-"title": "Cold hot separation",
+"title": "Cold Hot Separation",
"language": "en"
}
---
@@ -24,9 +24,9 @@ specific language governing permissions and limitations
under the License.
-->
-# [Experimental] Cold hot separation
+# [Experimental] Cold Hot Separation
-## Demand scenario
+## Demand Scenarios
A big usage scenario in the future is similar to the es log storage. In the
log scenario, the data will be cut by date. Many data are cold data, with few
queries. Therefore, the storage cost of such data needs to be reduced. From the
perspective of saving storage costs
1. The price of ordinary cloud disks of cloud manufacturers is higher than
that of object storage
diff --git a/docs/en/docs/advanced/compute_node.md
b/docs/en/docs/advanced/compute-node.md
similarity index 98%
rename from docs/en/docs/advanced/compute_node.md
rename to docs/en/docs/advanced/compute-node.md
index 1cd7c53a99..2dbc2e9290 100644
--- a/docs/en/docs/advanced/compute_node.md
+++ b/docs/en/docs/advanced/compute-node.md
@@ -25,12 +25,12 @@
-- >
-# Compute node
+# Compute Node
<version since="1.2.1">
</version>
-## Scenario
+## Scenarios
At present, Doris is a typical Share-Nothing architecture, which achieves very
high performance by binding data and computing resources in the same node.
With the continuous improvement of the performance for the Doris computing
engine, more and more users have begun to use Doris to directly query data on
data lake.
@@ -41,7 +41,7 @@ For these two mixed loads in one cluster, current Doris
architecture will appear
2. Poor disk usage, the data lake query only needs the computing resources,
while doris binding the storage and computing and we have to expand them
together, and cause a low utilization rate for disk.
3. Poor expansion efficiency, when the cluster is expanded, Doris will start
the migration of Tablet data, and this process will take a lot of time. And the
data lake query load has obvious peaks and valleys, it need hourly flexibility.
-## solution
+## Solutions
Implement a BE node role specially used for federated computing named `Compute
node`.
`Compute node` is used to handle remote federated queries such as this query
of data lake.
The original BE node type is called `hybrid node`, and this type of node can
not only execute SQL query, but also handle tablet data storage.
@@ -108,7 +108,7 @@ min_backend_num_for_external_table=3
When using the [MultiCatalog](../lakehouse/multi-catalog/multi-catalog.md)
function when querying, the query will be dispatched to the computing node
first.
-### some restrictions
+### Some Restrictions
- Compute nodes are controlled by configuration items, so do not configure
mixed type nodes, modify the configuration to compute nodes.
diff --git a/docs/en/docs/advanced/lateral-view.md
b/docs/en/docs/advanced/lateral-view.md
index c6921f3663..b32283f026 100644
--- a/docs/en/docs/advanced/lateral-view.md
+++ b/docs/en/docs/advanced/lateral-view.md
@@ -1,6 +1,6 @@
---
{
- "title": "Row to column",
+ "title": "Row to Column",
"language": "en"
}
---
@@ -24,7 +24,7 @@ specific language governing permissions and limitations
under the License.
-->
-# Row to column
+# Row to Column
Used in conjunction with generator functions such as `EXPLODE`, will generate
a virtual table containing one or more rows. `LATERAL VIEW` applies rows to
each raw output row.
diff --git a/docs/en/docs/advanced/orthogonal-bitmap-manual.md
b/docs/en/docs/advanced/orthogonal-bitmap-manual.md
index 2fb9c65eb9..526afdfb8d 100644
--- a/docs/en/docs/advanced/orthogonal-bitmap-manual.md
+++ b/docs/en/docs/advanced/orthogonal-bitmap-manual.md
@@ -1,6 +1,6 @@
---
{
- "title": "Orthogonal BITMAP calculation",
+ "title": "Orthogonal BITMAP Calculation",
"language": "en"
}
---
@@ -24,7 +24,7 @@ specific language governing permissions and limitations
under the License.
-->
-# Orthogonal BITMAP calculation
+# Orthogonal BITMAP Calculation
## Background
diff --git a/docs/en/docs/advanced/orthogonal-hll-manual.md
b/docs/en/docs/advanced/orthogonal-hll-manual.md
index fd2dc4e0fe..6d0c1e6fa2 100644
--- a/docs/en/docs/advanced/orthogonal-hll-manual.md
+++ b/docs/en/docs/advanced/orthogonal-hll-manual.md
@@ -1,6 +1,6 @@
---
{
- "title": "HLL approximate accurate deduplication",
+ "title": "HLL Approximate Accurate Deduplication",
"language": "en"
}
---
@@ -24,5 +24,5 @@ specific language governing permissions and limitations
under the License.
-->
-# HLL approximate accurate deduplication
+# HLL Approximate Accurate Deduplication
diff --git a/docs/en/docs/advanced/partition/table-temp-partition.md
b/docs/en/docs/advanced/partition/table-temp-partition.md
index aa478d20ed..59c326c0de 100644
--- a/docs/en/docs/advanced/partition/table-temp-partition.md
+++ b/docs/en/docs/advanced/partition/table-temp-partition.md
@@ -1,6 +1,6 @@
---
{
- "title": "Temporary partition",
+ "title": "Temporary Partition",
"language": "en"
}
---
@@ -24,7 +24,7 @@ specific language governing permissions and limitations
under the License.
-->
-# Temporary partition
+# Temporary Partition
Since version 0.12, Doris supports temporary partitioning.
diff --git a/docs/en/docs/advanced/resource.md
b/docs/en/docs/advanced/resource.md
index 237d280ee2..e04502f455 100644
--- a/docs/en/docs/advanced/resource.md
+++ b/docs/en/docs/advanced/resource.md
@@ -1,6 +1,6 @@
---
{
- "title": "Resource management",
+ "title": "Resource Management",
"language": "en"
}
---
diff --git a/docs/en/docs/advanced/sql-mode.md
b/docs/en/docs/advanced/sql-mode.md
index b39104cf96..4c9227f0d2 100644
--- a/docs/en/docs/advanced/sql-mode.md
+++ b/docs/en/docs/advanced/sql-mode.md
@@ -1,6 +1,6 @@
---
{
-"title": "SQL MODE",
+"title": "SQL Mode",
"language": "en"
}
---
@@ -24,7 +24,7 @@ specific language governing permissions and limitations
under the License.
-->
-# SQL MODE
+# SQL Mode
The sql mode newly supported by Doris refers to the sql mode management
mechanism of Mysql. Each client can set its own sql mode, and database
administrators with Admin privileges can set the global sql mode.
## sql mode introduce
diff --git a/docs/en/docs/advanced/time-zone.md
b/docs/en/docs/advanced/time-zone.md
index 5444c044ba..e729704714 100644
--- a/docs/en/docs/advanced/time-zone.md
+++ b/docs/en/docs/advanced/time-zone.md
@@ -1,6 +1,6 @@
---
{
- "title": "Time zone",
+ "title": "Time Zone",
"language": "en"
}
---
@@ -24,7 +24,7 @@ specific language governing permissions and limitations
under the License.
-->
-# Time zone
+# Time Zone
Doris supports multiple time zone settings
diff --git a/docs/en/docs/advanced/using-hll.md
b/docs/en/docs/advanced/using-hll.md
index f78e20724f..2f98f52e50 100644
--- a/docs/en/docs/advanced/using-hll.md
+++ b/docs/en/docs/advanced/using-hll.md
@@ -1,6 +1,6 @@
---
{
- "title": "Approximate deduplication using HLL",
+ "title": "Approximate Deduplication Using HLL",
"language": "en"
}
---
diff --git a/docs/sidebars.json b/docs/sidebars.json
index b164264ad7..21a991aa82 100644
--- a/docs/sidebars.json
+++ b/docs/sidebars.json
@@ -162,8 +162,8 @@
"advanced/variables",
"advanced/time-zone",
"advanced/small-file-mgr",
- "advanced/cold_hot_separation",
- "advanced/compute_node",
+ "advanced/cold-hot-separation",
+ "advanced/compute-node",
"advanced/lateral-view"
]
},
diff --git a/docs/zh-CN/docs/advanced/cold_hot_separation.md
b/docs/zh-CN/docs/advanced/cold-hot-separation.md
similarity index 100%
rename from docs/zh-CN/docs/advanced/cold_hot_separation.md
rename to docs/zh-CN/docs/advanced/cold-hot-separation.md
diff --git a/docs/zh-CN/docs/advanced/compute_node.md
b/docs/zh-CN/docs/advanced/compute-node.md
similarity index 100%
rename from docs/zh-CN/docs/advanced/compute_node.md
rename to docs/zh-CN/docs/advanced/compute-node.md
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
