[
https://issues.apache.org/jira/browse/BIGTOP-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497375#comment-13497375
]
Peter Linnell commented on BIGTOP-780:
--------------------------------------
+1 LGTM
> cannot install hive-server in SLES
> ----------------------------------
>
> Key: BIGTOP-780
> URL: https://issues.apache.org/jira/browse/BIGTOP-780
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.5.0
> Reporter: Johnny Zhang
> Assignee: Roman Shaposhnik
> Priority: Blocker
> Fix For: 0.5.0
>
> Attachments:
> 0001-BIGTOP-780.-cannot-install-hive-server-in-SLES.patch,
> BIGTOP-780.patch.txt
>
>
> do below to install hive-server in SLES
> {noformat}
> zypper clean -a
> ......
> bin/dd of=/etc/zypp/repos.d/cloudera-cdh3.repo << __EOT__
> [bigtop]
> name=Bigtop
> enabled=1
> gpgcheck=0
> type=NONE
> baseurl=http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Repository/./label=sles11//lastSuccessfulBuild/artifact/repo/
> __EOT__
> ......
> zypper install hive-server
> {noformat}
> the installation process seems fine, but the status is shown as 'not
> installed'
> {noformat}
> pkgtest-sles64-11:~ # zypper -q -n info hive-server
> Information for package hive-server:
> Repository: Bigtop
> Name: hive-server
> Version: 0.9.0.222-1
> Arch: noarch
> Vendor:
> Support Level: unknown
> Installed: No
> Status: not installed
> Installed Size: 5.0 KiB
> Summary: Provides a Hive Thrift service.
> Description:
> This optional package hosts a Thrift server for Hive clients across a network
> to use.
> ......
> ......
> pkgtest-sles64-11:~ # service hive-server status
> service: no such service hive-server
> {noformat}
> afterward, I tried install hive-server again, but seems OS think it is
> already installed
> {noformat}
> # zypper install hive-server
> Loading repository data...
> Reading installed packages...
> Resolving package dependencies...
> Nothing to do.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
