[
https://issues.apache.org/jira/browse/ATLAS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-32:
----------------------------------
Fix Version/s: (was: 0.5.1-incubating)
0.6-incubating
Affects Version/s: (was: 0.5-incubating)
0.6-incubating
> Atlas hook fails to fire in certain secure deployments
> ------------------------------------------------------
>
> Key: ATLAS-32
> URL: https://issues.apache.org/jira/browse/ATLAS-32
> Project: Atlas
> Issue Type: Bug
> Affects Versions: 0.6-incubating
> Reporter: Jonathan Maron
> Assignee: Jonathan Maron
> Priority: Critical
> Fix For: 0.6-incubating
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> In certain secure deployments, the interactions from hive to atlas trigger
> security exceptions like the following:
> 2015-06-20 07:29:00,506 INFO [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:run(154)) - Atlas hook failed
> com.sun.jersey.api.client.ClientHandlerException: java.io.IOException:
> org.apache.hadoop.security.authentication.client.AuthenticationException:
> GSSException: No valid credentials provided (Mechanism level: Failed to find
> any Kerberos tgt)
> this is more than likely due the need to perform the interactions as an
> identity that has an associated kerberos ticket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
