falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-390) falcon HCatProcess tests are failing in secure clusters
Date Mon, 28 Apr 2014 18:00:31 GMT

    [ https://issues.apache.org/jira/browse/FALCON-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983320#comment-13983320
] 

Venkatesh Seetharam commented on FALCON-390:
--------------------------------------------

bq. For multiple source usecase, this creates multiple replication workflows. Is there any
difference in workflows?
[~shwethags], good catch. In case of table storage, we need to pass the hive-site.xml that
vary by cluster in the workflow definition. Also, if security is enabled, then a credential
object needs to be created per cluster. Will there be any issue with this approach?

bq. OozieWorkflowBuilder.createHiveConf() and propagateHiveCredentials() set the same properties.
Move setting properties to common code?
They differ a little bit, former creates a hive-site.xml per cluster for actions while latter
adds the credentials to properties for coordinator to authenticate against hive for partition
filtering. There are additional things in latter but let me think about it. 

Thanks! 

> falcon HCatProcess tests are failing in secure clusters
> -------------------------------------------------------
>
>                 Key: FALCON-390
>                 URL: https://issues.apache.org/jira/browse/FALCON-390
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.5
>         Environment: linux, secure
>            Reporter: Raghav Kumar Gautam
>            Assignee: Venkatesh Seetharam
>              Labels: security
>             Fix For: 0.5
>
>         Attachments: FALCON-390-v1.patch, FALCON-390-v2.patch
>
>
> All the HCatProcess tests are failing in secure mode. Oozie is not able to talk to hcat
server. The following additions additional configuration needs to be added.
> job.properties-
> hive.metastore.sasl.enabled=true
> hive.metastore.kerberos.principal=hive/<host>@<realm>
> workflow.xml-
> <credentials>
> <credential name='hiveauth' type='hcat'>
> <property>
> <name>hcat.metastore.uri</name>
> <value>thrift://<host>:<port></value>
> </property>
> <property>
> <name>hcat.metastore.principal</name>
> <value>hive/<host>@<realm></value>
> </property>
> </credential>
> </credentials>



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message