This is an automated email from the ASF dual-hosted git repository.
awong pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/master by this push:
new 7caa088 docs: update known issues based on recent features
7caa088 is described below
commit 7caa088462e6fccd50ef62434c1d4eca1f4c16c9
Author: Andrew Wong <[email protected]>
AuthorDate: Wed Nov 11 22:19:12 2020 -0800
docs: update known issues based on recent features
It was reported that we ought to remove DATE from the list of
unsupported types. Along the way, I removed other limitations that have
been addressed in recent releases.
Change-Id: I57a7ae753f541f06cdbf8990b8e9717a37486e41
Reviewed-on: http://gerrit.cloudera.org:8080/16713
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <[email protected]>
Reviewed-by: Grant Henke <[email protected]>
---
docs/known_issues.adoc | 15 +++++----------
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc
index 84f2925..b35cb38 100644
--- a/docs/known_issues.adoc
+++ b/docs/known_issues.adoc
@@ -51,10 +51,12 @@
=== Columns
-* CHAR, DATE, and complex types like ARRAY, MAP, and STRUCT are not supported.
+* `CHAR` and complex types like `ARRAY`, `MAP`, and `STRUCT` are not yet
+ supported.
* Type, nullability and type attributes (i.e. precision and scale of `DECIMAL`,
- length of `VARCHAR`)of existing columns cannot be changed by altering the
table.
+ length of `VARCHAR`) of existing columns cannot be changed by altering the
+ table.
* Tables can have a maximum of 300 columns by default.
@@ -72,7 +74,7 @@
* Secondary indexes are not supported.
-* Multi-row transactions are not supported.
+* Multi-row transactions are not yet supported.
* Relational features, like foreign keys, are not supported.
@@ -100,8 +102,6 @@
== Cluster management
-* Rolling restart is not supported.
-
* Recommended maximum point-to-point latency within a Kudu cluster is 20
milliseconds.
* Recommended minimum point-to-point bandwidth within a Kudu cluster is 10
Gbps.
@@ -119,16 +119,11 @@
* Write ahead logs (WAL) can only be stored on one disk.
-* Tablet servers cannot be gracefully decommissioned.
-
* Tablet servers can’t change address/port.
* Kudu has a hard requirement on having up-to-date NTP. Kudu masters and
tablet servers
will crash when out of sync.
-* Kudu releases are only tested with NTP. Other time synchronization providers
like Chrony
- may or may not work.
-
== Scale
Kudu is known to run seamlessly across a wide array of environments and
workloads
