This is an automated email from the ASF dual-hosted git repository.
laiyingchun pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 7089733c1 KUDU-1945 Update faq with non-unique PK
7089733c1 is described below
commit 7089733c1d79931ef7411415f46429bf26d37a7e
Author: Marton Greber <greber...@gmail.com>
AuthorDate: Mon May 8 17:37:51 2023 +0000
KUDU-1945 Update faq with non-unique PK
Change-Id: I3e588ffb84907deed7cfc8d6be088b09f2b54322
Reviewed-on: http://gerrit.cloudera.org:8080/19860
Reviewed-by: Abhishek Chennaka <achenn...@cloudera.com>
Reviewed-by: Wenzhe Zhou <wz...@cloudera.com>
Tested-by: Abhishek Chennaka <achenn...@cloudera.com>
---
faq.md | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/faq.md b/faq.md
index 344fda3fb..cced88cde 100644
--- a/faq.md
+++ b/faq.md
@@ -516,10 +516,12 @@ could be range-partitioned on only the timestamp column.
#### Does Kudu have relational features like autoincrement column, PK/FK
constraints, or built-in indexes?
Kudu tables have a primary key that is used for uniqueness as well as providing
-quick access to individual rows. Auto-incrementing columns, foreign key
constraints,
-and secondary indexes are not currently supported, but could be added in
subsequent
-Kudu releases.
-
+quick access to individual rows. Kudu supports auto-incrementing columns,
however auto-incrementing
+columns are system generated and users can't create a table with
auto-incrementing column explicitly.
+Columns which don't fulfill the uniqueness constraint can be used to create
+[non-unique primary
keys](http://kudu.apache.org/docs/schema_design.html#non-unique_primary_keys).
+Foreign key constraints, and secondary indexes are not currently supported, but
+could be added in subsequent Kudu releases.
### Transactions
