Skip to content

Commit d7ca36f

Browse files
authored
Fix md-lint
1 parent bb6de86 commit d7ca36f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/guides/developer/deduplicating-inserts-on-retries.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ Insert operations can sometimes fail due to errors such as timeouts. When insert
99

1010
When an insert is retried, ClickHouse tries to determine whether the data has already been successfully inserted. If the inserted data is marked as a duplicate, ClickHouse does not insert it into the destination table. However, the user will still receive a successful operation status as if the data had been inserted normally.
1111

12-
## Limitations
12+
## Limitations {#limitations}
1313

1414
### Uncertain insert status {#uncertain-insert-status}
1515

16-
The user must retry the insert operation until it succeeds. If all retries fail, it is impossible to determine whether the data was inserted or not. When materialized views are involved, it is also unclear in which tables the data may have appeared. The materialized views could be out of sync with source table.
16+
The user must retry the insert operation until it succeeds. If all retries fail, it is impossible to determine whether the data was inserted or not. When materialized views are involved, it is also unclear in which tables the data may have appeared. The materialized views could be out of sync with the source table.
1717

1818
### Deduplication window limit {#deduplication-window-limit}
1919

0 commit comments

Comments
 (0)