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

jirapos...@reviews.apache.org commented on HBASE-4498:
------------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2075/
-----------------------------------------------------------

Review request for hbase.


Summary
-------

Updated ZOOKEEPER_HOME location to default to /usr (default location of 
ZooKeeper rpm/deb package)


This addresses bug HBASE-4498.
    https://issues.apache.org/jira/browse/HBASE-4498


Diffs
-----

  /src/packages/update-hbase-env.sh 1176602 

Diff: https://reviews.apache.org/r/2075/diff


Testing
-------


Thanks,

Eric


                
> HBase RPM/DEB packages attempt to setup ZooKeeper environment incorrectly
> -------------------------------------------------------------------------
>
>                 Key: HBASE-4498
>                 URL: https://issues.apache.org/jira/browse/HBASE-4498
>             Project: HBase
>          Issue Type: Bug
>          Components: build, scripts
>    Affects Versions: 0.92.0
>         Environment: Java, Linux
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.92.0
>
>         Attachments: HBASE-4498.patch
>
>
> HBase RPM packaging was done prior to completion of ZooKeeper RPM packaging.  
> In update-hbase-env.sh, it expects ZooKeeper environment script to exist in 
> /etc/default/zookeeper-env.sh.  After several revision of ZOOKEEPER-999, it 
> was decided to remove /etc/default/zookeeper-env.sh by ZooKeeper community.  
> Hence, update-hbase-env.sh should not depend on 
> /etc/default/zookeeper-env.sh.  Instead, update-hbase-env.sh should assume 
> ZooKeeper exists in /usr for RPM/deb packages.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to