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

Hudson commented on AMBARI-20552:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7135 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7135/])
AMBARI-20552. HDP 3.0 TP - create Service Advisor for Hive.(vbrodetskyi) 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9bb5e4aa41526b078b494bab8ba2a7edb61d78a6])
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/configuration/hive-site.xml
* (add) 
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/service_advisor.py


> HDP 3.0 TP - create Service Advisor for Hive
> --------------------------------------------
>
>                 Key: AMBARI-20552
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20552
>             Project: Ambari
>          Issue Type: Story
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20552.patch
>
>
> Create a Service Advisor script for Hive in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6
> In HDP 3.0, Hive will use the same binary/RPM for both batch and interactive 
> mode.
> However, batch and interactive will use different config files.
> Tez is a dependency of Hive, so Tez must be able to install first.
> In HDP 3.0, Hive will use the same binary/RPM for both batch and interactive 
> mode.
> However, batch and interactive will use different config files.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to