KassieZ commented on code in PR #2333:
URL: https://github.com/apache/doris-website/pull/2333#discussion_r2062818358


##########
i18n/zh-CN/docusaurus-plugin-content-docs/current/faq/load-faq.md:
##########
@@ -24,9 +24,73 @@ specific language governing permissions and limitations
 under the License.
 -->
 
-# Routine Load 常见问题
+# 导入通用问题

Review Comment:
   一级标题 = `"title": "常见导入问题",`,正文中的标题需要从 二级标题开始



##########
docs/faq/load-faq.md:
##########
@@ -0,0 +1,140 @@
+---
+{
+    "title": "Load FAQ",
+    "language": "en"
+}
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# General Load FAQ
+
+## Error "[DATA_QUALITY_ERROR] Encountered unqualified data"
+**Problem Description**: Data quality error during loading.
+
+**Solution**:
+- Stream Load and Insert Into operations will return an error URL, while for 
Broker Load you can check the error URL through the `Show Load` command.
+- Use a browser or curl command to access the error URL to view the specific 
data quality error reasons.
+- Use the strict_mode and max_filter_ratio parameters to control the 
acceptable error rate.
+
+## Error "[E-235] Failed to init rowset builder"
+**Problem Description**: Error -235 occurs when the load frequency is too high 
and data hasn't been compacted in time, exceeding version limits.
+
+**Solution**:
+- Increase the batch size of data loading and reduce loading frequency.
+- Increase the `max_tablet_version_num` parameter in `be.conf`.
+
+## Error "[E-238] Too many segments in rowset"
+**Problem Description**: Error -238 occurs when the number of segments under a 
single rowset exceeds the limit.
+
+**Common Causes**:
+- The bucket number configured during table creation is too small.
+- Data skew occurs; consider using more balanced bucket keys.
+
+## Error "Transaction commit successfully, BUT data will be visible later"
+**Problem Description**: Data load is successful but temporarily not visible.
+
+**Cause**: Usually due to transaction publish delay caused by system resource 
pressure.
+
+## Error "Failed to commit kv txn [...] Transaction exceeds byte limit"
+**Problem Description**: In shared-nothing mode, too many partitions and 
tablets are involved in a single load, exceeding the transaction size limit.
+
+**Solution**:
+- Load data by partition in batches to reduce the number of partitions 
involved in a single load.
+- Optimize table structure to reduce the number of partitions and tablets.
+
+## Extra "\r" in the last column of CSV file
+**Problem Description**: Usually caused by Windows line endings.
+
+**Solution**:
+Specify the correct line delimiter: `-H "line_delimiter:\r\n"`
+
+## CSV data with quotes imported as null
+**Problem Description**: CSV data with quotes becomes null after import.
+
+**Solution**:
+Use the `trim_double_quotes` parameter to remove double quotes around fields.
+
+# Stream Load

Review Comment:
   Level 1 title is `"title": "Load FAQ",` , please start from level 2 title



-- 
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]

Reply via email to