IMPALA-12010: [DOCS] Document the support for non-unique primary key

Incorporated new comments.
Made changes to address new comments posted after the patch was merged.

Change-Id: Ifaea9645cf771b76fda3083d73b14524f53eb186
Reviewed-on: http://gerrit.cloudera.org:8080/19636
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Reviewed-by: Abhishek Chennaka <achennaka@cloudera.com>
Reviewed-by: Wenzhe Zhou <wzhou@cloudera.com>
This commit is contained in:
Shajini Thayasingh
2023-03-20 12:19:50 -07:00
committed by Wenzhe Zhou
parent 04f7e8c0f9
commit 8edfab000e

View File

@@ -210,7 +210,10 @@ under the License.
table. The data engine handles this by appending a system generated auto-incrementing
column to the non-unique primary key columns. This is done to guarantee the uniqueness of
the primary key. This auto-incrementing column is named as 'auto_incrementing_id' with
bigint type. The assignment to it during insertion is automatic.</p>
bigint type and this column is only system generated and cannot be explicitly created by
the user. This auto_incrementing_id column is unique across a partition/tablet i.e. every
partition/tablet would have this column starting from one and incrementing monotonically.
The assignment to this column during insertion is automatic.</p>
</conbody>
</concept>
<concept id="create">