[jira] [Updated] (ATLAS-585) NotificationHookConsumer creates new AtlasClient for every message

["Shwetha G S (JIRA)" <ji...@apache.org>]

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

Shwetha G S updated ATLAS-585:
------------------------------
    Attachment: ATLAS-585.patch

> NotificationHookConsumer creates new AtlasClient for every message
> ------------------------------------------------------------------
>
>                 Key: ATLAS-585
>                 URL: https://issues.apache.org/jira/browse/ATLAS-585
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Shwetha G S
>             Fix For: 0.7-incubating
>
>         Attachments: ATLAS-585.patch
>
>
> Every AtlasClient instance creates com.sun.jersey.api.client.Client which is expensive. As part of ATLAS-577, NotificationHookConsumer creates new atlas client for every message. This is done to pass the user information(the user who created the message/entities) through the APIs. This wouldn't work in kerberos environment where the credentials are not available on the atlas server. We should probably make the API call as atlas user and pass in the actual user information in another query param(like doas user)



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