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

ASF GitHub Bot commented on FALCON-2045:
----------------------------------------

GitHub user yzheng-hortonworks opened a pull request:

    https://github.com/apache/falcon/pull/197

    FALCON-2045 Enhance document on registry point in cluster specifiction for 
Hive HA mode

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/yzheng-hortonworks/falcon FALCON-2045

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/falcon/pull/197.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #197
    
----
commit eaadf67e76bd6ae3faa760a80e4c3a23de9f949a
Author: yzheng-hortonworks <yzh...@hortonworks.com>
Date:   2016-06-22T23:46:25Z

    FALCON-2045 Enhance document on registry point in cluster specifiction for 
Hive HA mode

----


> Enhance document on registry point in cluster specifiction for Hive HA mode
> ---------------------------------------------------------------------------
>
>                 Key: FALCON-2045
>                 URL: https://issues.apache.org/jira/browse/FALCON-2045
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Ying Zheng
>            Assignee: Ying Zheng
>
> Got some inquiries from users when they try to use Hive HA mode, but got an 
> error when scheduling entities with Oozie. One common cause is the wrong 
> format of registry endpoint in cluster specification.
> The registry endpoint Oozie supports should only contain one "thrft://" at 
> the beginning. However, most of users will add "thrft://" to each Hive 
> metastore host. This JIRA is to provide documentation / example for Hive HA 
> case.



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

Reply via email to