This is an automated email from the ASF dual-hosted git repository. alexey pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/kudu.git
commit 02b614c690ac2e25065132760aaee92b26d51904 Author: Grant Henke <[email protected]> AuthorDate: Tue Apr 9 17:46:38 2019 -0700 [docs] Remove flume kerberos limitation Removes the flume kerberos limitation as it was resolved via KUDU-2012. Change-Id: Ied4704fc16b18fe0ee93570c3cbbbf6f61da8a4a Reviewed-on: http://gerrit.cloudera.org:8080/12978 Reviewed-by: Mike Percy <[email protected]> Tested-by: Grant Henke <[email protected]> --- docs/known_issues.adoc | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc index e8511af..8425d00 100644 --- a/docs/known_issues.adoc +++ b/docs/known_issues.adoc @@ -162,9 +162,6 @@ * Kudu server Kerberos principals must follow the pattern `kudu/<HOST>@DEFAULT.REALM`. Configuring an alternate Kerberos principal is not supported. -* Kudu's integration with Apache Flume does not support writing to Kudu clusters that - require Kerberos authentication. - * Server certificates generated by Kudu IPKI are incompatible with link:https://www.bouncycastle.org/[bouncycastle] version 1.52 and earlier. See link:https://issues.apache.org/jira/browse/KUDU-2145[KUDU-2145] for details.
