Wenzhe Zhou has posted comments on this change. ( 
http://gerrit.cloudera.org:8080/19587 )

Change subject: IMPALA-11906: [DOCS] Document the support for non-unique 
primary key
......................................................................


Patch Set 1:

(4 comments)

http://gerrit.cloudera.org:8080/#/c/19587/1/docs/topics/impala_kudu.xml
File docs/topics/impala_kudu.xml:

http://gerrit.cloudera.org:8080/#/c/19587/1/docs/topics/impala_kudu.xml@228
PS1, Line 228: auto_incrementing_id'
'auto_incrementing_id'


http://gerrit.cloudera.org:8080/#/c/19587/1/docs/topics/impala_kudu.xml@252
PS1, Line 252: PRIMARY KEY
PRIMARY KEY attribute


http://gerrit.cloudera.org:8080/#/c/19587/1/docs/topics/impala_kudu.xml@272
PS1, Line 272: <note>When you query a table using the SELECT statement, it will 
not display the system
             :             generated auto incrementing column unless the column 
is explicitly specified in the
             :             select list.</note>
move to line 251 as separate concept "Query auto incrementing column"


http://gerrit.cloudera.org:8080/#/c/19587/1/docs/topics/impala_kudu.xml@288
PS1, Line 288: <li>Kudu supports multiple-rows transactions for INSERT and CTAS 
statements, but does not
             :             support UPDATE/UPSERT/DELETE statements.</li>
This is not directly related to non unique primary key. We need to add a 
separate section for Kudu Transaction, then add this as limitation for Kudu 
transaction.



--
To view, visit http://gerrit.cloudera.org:8080/19587
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I7b5a452f2199d097077150c012497aa4a3ecf7d9
Gerrit-Change-Number: 19587
Gerrit-PatchSet: 1
Gerrit-Owner: Shajini Thayasingh <sthayasi...@cloudera.com>
Gerrit-Reviewer: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Gerrit-Reviewer: Wenzhe Zhou <wz...@cloudera.com>
Gerrit-Comment-Date: Tue, 07 Mar 2023 08:16:50 +0000
Gerrit-HasComments: Yes

Reply via email to