Known Issues in Apache Kudu

Learn about the known issues in Kudu, the impact or changes to the functionality, and the workaround.

Kudu supports only coarse-grain authorization. Kudu does not yet support integration with Atlas.
Kudu HMS Sync is disabled and is not yet supported
Kerberos authentication fails with rdns disabled
When rdns is set to false, the Kudu Java client does not retain the original hostname, and replaces them with the resolved IP addresses. This prevents Kerberos authentication from working properly. For more information, see KUDU-3415.
Add a "ranger_kudu_plugin_service_name" configuration to the Kudu Master configuration group in the blueprint with the value "{{GENERATED_RANGER_SERVICE_NAME}}"