For improving installation experience for HBase 0.92 with Hadoop 0.20.205, I wish we could get these patches into 0.92.0 RC:
HBASE-4415 Add configuration script for setup HBase (hbase-setup-conf.sh) HBASE-4523 dfs.support.append config should be present in the hadoop configs, we should remove them from hbase so the user is not confused when they see the config in 2 places HBASE-4535 hbase-env.sh in hbase rpm does not set HBASE_CONF_DIR HBASE-4635 Remove dependency of java for rpm/deb packaging HBASE-4498 HBase RPM/DEB packages attempt to setup ZooKeeper environment incorrectly Patches are available for all jiras and reviewed. regards, Eric On Nov 1, 2011, at 2:53 PM, Ted Yu wrote: > HBASE-2856 is harder than initially expected. > > It is marked for HBase 0.94. > > On Tue, Nov 1, 2011 at 2:24 PM, lars hofhansl <[email protected]> wrote: > >> +1. That would be a good milestone for 0.92. >> >> >> I also wish we'd get HBASE-4344 and related jiras (HBASE-2856, etc) in. >> >> >> -- Lars >> ________________________________ >> From: Gary Helmling <[email protected]> >> To: [email protected] >> Sent: Tuesday, November 1, 2011 12:00 PM >> Subject: Re: An 0.92.0 Release Candidate this week? >> >> I'd like to lobby for the security patches (HBASE-2742 and HBASE-3025) >> going in to 0.92. This may sound like a big change at this stage, but >> in reality the impact on current HBase core is pretty contained: >> >> * HBASE-2742 adds a "security" profile to the build, which only >> includes the security sources (security/src/...) if enabled. The >> changes to core code in this patch mostly just enable subclassing of >> HBaseClient and HBaseServer for implementation of the SecureRpcEngine. >> >> * HBASE-3025 adds classes to the "security" source tree to implement >> authorization checking. These break down into: >> - an AccessController coprocessor implementation for authorization >> checking. If not enabled, this code has no impact on core. >> - additional shell commands for ACL manipulation: grant, revoke, >> user_permission. These implementations check for existence of the >> security classes on the classpath and will fail gracefully with an >> error message that security is not available. >> >> The use of a maven profile means that security components will only be >> included in the build when activated (mvn ... -P security), so we can >> continue to do builds and releases without the security components, if >> needed. To start with, we may want to do separate release packages >> for the base HBase version vs. HBase with security (0.92.0 and >> 0.92.0-security), so that only those interested in using the security >> features need be impacted by them. >> >> At Trend, we've been running a release with HBase security for the >> past 6 months in production, so it's been proven to work for us. I >> know that there are other groups interested in working with HBase >> security on 0.92, so I would really like to find a way meet that need. >> At the same time, all of the security components have been built to >> be optionally enabled, so I think there is very little risk to core by >> including it. >> >> --gh >> >> On Mon, Oct 31, 2011 at 11:16 AM, Stack <[email protected]> wrote: >>> There's just a few issues left. Check it out: >>> https://issues.apache.org/jira/browse/HBASE/fixforversion/12314223 >>> >>> I'm hoping we can kill these last few and post an RC this week. If >>> there is anything you crew could do to help along the RC, I would >>> appreciate the hand (Or, if there is something you think has to make >>> it into 0.92.0, please speak up). >>> >>> Thanks all, >>> St.Ack >>> >>
