Skip to content

Commit

Permalink
[Doc] Fixed description of insert behavior on primary key table (#53111)
Browse files Browse the repository at this point in the history
Signed-off-by: kalyanmysore <[email protected]>
Signed-off-by: 絵空事スピリット <[email protected]>
Co-authored-by: 絵空事スピリット <[email protected]>
(cherry picked from commit 29d5f63)
  • Loading branch information
kalyanmysore authored and mergify[bot] committed Nov 22, 2024
1 parent 5a57cf5 commit 5dc8e80
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/en/table_design/table_types/table_types.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,4 +41,4 @@ For more descriptions of sort keys, see [Sort keys and prefix indexes](../indexe

- Unique Key table and Primary Key table

StarRocks replaces each newly loaded record with the previously loaded record and retains only the most recently loaded record as a row in the table. After the loading is complete, the table does not contain rows that have the same primary key. The Unique Key table and the Primary Key table can be considered a special Aggregate table in which the REPLACE aggregate function is specified for metric columns to return the most recent record among a group of records that have the same primary key.
StarRocks replaces each previously loaded record with the newly loaded record and retains only the most recently loaded record as a row in the table. After the loading is complete, the table does not contain previous rows that have the same primary key. Only the latest record that contains the same unique key/primary key is retained. The Unique Key table and the Primary Key table can be considered a special Aggregate table in which the REPLACE aggregate function is specified for metric columns to return the most recent record among a group of records that have the same primary key.

0 comments on commit 5dc8e80

Please sign in to comment.