[
https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202124#comment-13202124
]
Jonathan Hsieh commented on HBASE-5341:
---------------------------------------
I'd be happy if the tarball(s) for 0.92.1 just come out with the ./security
directory in the correct place in tarball. I would think that would be the
most expedient thing to do. (this is however, likely easier said than done)
@Gary
- does compiling against hdfs 1.0.0 and running this new hbase jar in
non-secure mode against the append branch hdfs jar work? If it works, I'm not
convinced compilation matters as much. I do most of my system testing of these
release from jars compiled against hadoop 1.0.0 but running on top of a cdh3
hdfs version -- no problems. If the hbase binary doesn't work, then I agree
that this a concern -- it would block shops locked into their own hdfs branches
that don't support hadoop security.
- using the module approach, the security stuff would be a separate jar that we
could add to the classpath right?
@Ted
- There are plenty of pieces we've release that been haven't tested by many
people. That said, regardless of how included, I can commit that we'll be
testing the access control and security features.
@Stack
- Hadoop 1.0.0 and CDH3 both have security and append. The next HDFS it seems
most folks are coalescing around is 0.23, which also has security and append.
> HBase build artifact should include security code by defult
> ------------------------------------------------------------
>
> Key: HBASE-5341
> URL: https://issues.apache.org/jira/browse/HBASE-5341
> Project: HBase
> Issue Type: Improvement
> Components: build, security
> Affects Versions: 0.94.0, 0.92.1
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
>
> Hbase 0.92.0 was released with two artifacts, plain and security. The
> security code is built with -Psecurity. There are two tarballs, but only the
> plain jar in maven repo at repository.a.o.
> I see no reason to do a separate artifact for the security related code,
> since 0.92 already depends on secure Hadoop 1.0.0, and all of the security
> related code is not loaded by default. In this issue, I propose, we merge the
> code under /security to src/ and remove the maven profile.
--
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
