This is an automated email from the ASF dual-hosted git repository. stigahuang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/impala.git
commit 8edfab000e9ecd89cb3bed2b24e640489e88b342 Author: Shajini Thayasingh <[email protected]> AuthorDate: Mon Mar 20 12:19:50 2023 -0700 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 <[email protected]> Reviewed-by: Abhishek Chennaka <[email protected]> Reviewed-by: Wenzhe Zhou <[email protected]> --- docs/topics/impala_kudu.xml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/topics/impala_kudu.xml b/docs/topics/impala_kudu.xml index 0bc781b3b..8f9fbf194 100644 --- a/docs/topics/impala_kudu.xml +++ b/docs/topics/impala_kudu.xml @@ -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">
