[kudu] branch branch-1.9.x updated: [docs] Remove flume kerberos limitation

[gr...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

granthenke pushed a commit to branch branch-1.9.x
in repository https://gitbox.apache.org/repos/asf/kudu.git


The following commit(s) were added to refs/heads/branch-1.9.x by this push:
     new fda5737  [docs] Remove flume kerberos limitation
fda5737 is described below

commit fda573737e6af6af6a24337e9f1664f39b559e98
Author: Grant Henke <gr...@apache.org>
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 <mp...@apache.org>
    Tested-by: Grant Henke <gr...@apache.org>
    (cherry picked from commit 02b614c690ac2e25065132760aaee92b26d51904)
    Reviewed-on: http://gerrit.cloudera.org:8080/13101
    Tested-by: Kudu Jenkins
    Reviewed-by: Alexey Serbin <as...@cloudera.com>
---
 docs/known_issues.adoc | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc
index ad5ba5d..eaa5159 100644
--- a/docs/known_issues.adoc
+++ b/docs/known_issues.adoc
@@ -184,9 +184,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.