You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 1, 2024. It is now read-only.
2. Append a block (Block1) of 3 columns，and the compressed sizes of the three columns are 11.3K, 7.8K, and 3.5K.
193
+
2. Append a block (Block1) of 3 columns, and the compressed sizes of the three columns are 11.3K, 7.8K, and 3.5K.
194
194
```
195
-
1）Calculate an optimal size for each column：12K，8K and 4K
196
-
2）Find unused candidate parts. Not found here.
195
+
1) Calculate an optimal size for each column: 12K, 8K and 4K
196
+
2) Find unused candidate parts. Not found here.
197
197
3) Allocate new parts for these 3 columns
198
198
4) Flush these 3 columns to the specified new parts
199
199
5) Flush meta
@@ -202,8 +202,8 @@ Suppose the `MinPartSize` is `4`, which stands for `4K`. It starts with an empty
202
202
203
203
3. There are some updates to the 3rd column of Block0, which is marked as `Block0-2`. Now we start to checkpoint the updates into segment file. The compressed size of the updated `Block0-2` is 7.3K.
204
204
```
205
-
1）Calculate an optimal size：8K
206
-
2）Find unused candidate parts. Not found here.
205
+
1) Calculate an optimal size: 8K
206
+
2) Find unused candidate parts. Not found here.
207
207
3) Allocate a new part
208
208
4) Flush to the specified new part
209
209
5) Flush meta
@@ -213,18 +213,18 @@ Suppose the `MinPartSize` is `4`, which stands for `4K`. It starts with an empty
213
213
214
214
4. There are some updates to the first column of Block1, which is marked as `Block1-0`. Now we start to checkpoint the updates into segment file. The compressed size of the updated `Block1-0` is 3.6K.
215
215
```
216
-
1）Calculate an optimal size：4K
217
-
2）Find unused candidate parts. Unused Part(3, 1) found
216
+
1) Calculate an optimal size: 4K
217
+
2) Find unused candidate parts. Unused Part(3, 1) found
3) Flush these 3 columns to the specified unused parts
229
229
4) Flush meta
230
230
```
@@ -595,7 +595,7 @@ Txn Local Storage
595
595
596
596
#### UPDATE & DELETE
597
597
##### UPDATE & DELETE INSERTED DATA
598
-
If any deletes applied to the batch in the transaction local store，a bitmap for deletion is created. Any update will be transfer to a delete and insert.
598
+
If any deletes applied to the batch in the transaction local store, a bitmap for deletion is created. Any update will be transfer to a delete and insert.
599
599
600
600
##### UPDATE & DELETE COMMITTED DATA
601
601
A delete history will be create for blocks with any **DELETE** operation.
@@ -634,7 +634,7 @@ A transaction usually contains multiple **DDL** and **DML** statements. As menti
634
634
All **DDL** operations correspond to **Catalog****DML** operations, see the [corresponding chapter](#Catalog) for details.
635
635
636
636
### Commit
637
-
As mentioned earlier，the data of a transaction is grouped by table, and each group of data is a combination of the following data types
637
+
As mentioned earlier, the data of a transaction is grouped by table, and each group of data is a combination of the following data types
638
638
- <imgsrc="https://latex.codecogs.com/svg.image?Batch_{}^{i}"title="Batch_{}^{i}" />. The i-th uncommitted batch
639
639
- <imgsrc="https://latex.codecogs.com/svg.image?Bitmap_{}^{i}"title="Bitmap_{}^{i}" />. The delete bitmap of <imgsrc="https://latex.codecogs.com/svg.image?Batch_{}^{i}"title="Batch_{}^{i}" />
640
640
- <imgsrc="https://latex.codecogs.com/svg.image?DeleteNode_{blk}"title="DeleteNode_{blk}" />. The delete node of a committed block.
0 commit comments