You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2016/05/23 06:47:12 UTC

[jira] [Updated] (ATLAS-809) JAAS configuration needed for Kafka interaction via Atlas config file

     [ https://issues.apache.org/jira/browse/ATLAS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shwetha G S updated ATLAS-809:
------------------------------
    Attachment: 0001-In-memory-JAAS-Configurator.-Addressed-review-commen.patch

patch from reviewboard

> JAAS configuration needed for Kafka interaction via Atlas config file
> ---------------------------------------------------------------------
>
>                 Key: ATLAS-809
>                 URL: https://issues.apache.org/jira/browse/ATLAS-809
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Madhan Neethiraj
>            Assignee: Abhay Kulkarni
>         Attachments: 0001-In-memory-JAAS-Configurator.-Addressed-review-commen.patch
>
>
> In a kerberized environment, using Kafka from Atlas requires 'KafkaClient' section to be configured in application's JAAS config file. Given Atlas hooks run in host components (like Hive, Falcon, Storm..), this requires updates to JAAS config file used by the component; and in some components (like Hive) require update to JVM startup parameters to specify the location of JAAS configuration file. Instead of requiring to update each component's JAAS configuration file and startup parameters, it will be cleaner and simpler to handle JAAS configuration via existing Atlas configuration file (atlas-application.properties).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)