Skip to content

Commit eaa81be

Browse files
committed
caps to lower in paragraph names
1 parent 18e50bc commit eaa81be

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

ydb/docs/en/core/reference/ydb-cli/export-import/toc_i.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,5 +13,5 @@ items:
1313
href: import-s3.md
1414
- name: Importing data from a file to an existing table
1515
href: import-file.md
16-
- name: View Backup and Restoration
16+
- name: View backup and restoration
1717
href: view-backup.md

ydb/docs/en/core/reference/ydb-cli/export-import/view-backup.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
# View Backup and Restoration
1+
# View backup and restoration
22

33
This article explains the backup and restoration behavior of views in {{ ydb-short-name }}.
44

5-
## Backup File Organization (View vs Table)
5+
## Backup file organization
66

77
In most aspects, backing up views does not differ from backing up tables:
88

@@ -18,9 +18,9 @@ However, the formats used to backup views and tables differ:
1818

1919
Thus, during restoration, tables are restored from the protobuf representation (`scheme.pb`), whereas views are restored by executing the `create_view.sql` statements.
2020

21-
## View Query Rewrite
21+
## View query rewrite
2222

23-
As we have discussed in the previous [paragraph](#backup-file-organization-view-vs-table), {{ ydb-short-name }} views are backed up as `CREATE VIEW` SQL definitions. During restoration from a backup, these plain-text definitions require special processing to adjust object reference paths within view queries to ensure correctness in the target database.
23+
As we have discussed in the previous [paragraph](#backup-file-organization), {{ ydb-short-name }} views are backed up as `CREATE VIEW` SQL definitions. During restoration from a backup, these plain-text definitions require special processing to adjust object reference paths within view queries to ensure correctness in the target database.
2424

2525
### Example
2626

@@ -51,7 +51,7 @@ ydb --database /target_db --endpoint <endpoint> tools restore --path . --input .
5151

5252
the {{ ydb-short-name }} CLI automatically rewrites the query stored in the `create_view.sql` file to reference `/target_db/my_table` instead of the original `/my_database/my_table`.
5353

54-
### Query Rewriting Rules
54+
### Query rewriting rules
5555

5656
The query rewriting follows these rules:
5757

@@ -69,7 +69,7 @@ restored_reference_path = restore_root + reference_path_relative_to_backup_root
6969

7070
This ensures that after restoration, the references within the view correctly point to the intended tables or objects in the new environment.
7171

72-
#### Handling Relative Paths
72+
#### Handling relative paths
7373

7474
Views can reference tables or other views using path-based references, which may be absolute or relative. Absolute reference paths are handled by replacing the `backup_root` path part with the `restore_root`. Relative reference paths follow similar logic. More precisely, relative paths are first resolved to absolute paths using the [TablePathPrefix](../../../yql/reference/syntax/pragma#table-path-prefix) pragma:
7575

0 commit comments

Comments
 (0)