hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10847) 0.94: drop non-secure builds, make security the default
Date Sat, 29 Mar 2014 06:18:14 GMT

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

Lars Hofhansl commented on HBASE-10847:

Not sure that would do. We'd then only run the secure tests with the SecureRpcEngine.
The way I see it: The SecureRpcEngine is more general (by definition). It can run a secure
and non-secure setting. It's the one we should switch to and the one that gets the testing.

Maybe another option is to now have a non-secure profile, just for testing. It would exclude
the the secure tests and the secure resources (with some maven trickery). That way we could
still two jenkins build.

Yet another option is run a select set of with the both RpcEngines. TestFromClientSide comes
to mind, as well as some of the bulkload and M/R tests. So almost all tests would run with
the SecureRpcEngine, and some would also run with the WritableRpcEngine.
I think I'd favor this latter option.

> 0.94: drop non-secure builds, make security the default
> -------------------------------------------------------
>                 Key: HBASE-10847
>                 URL: https://issues.apache.org/jira/browse/HBASE-10847
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.94.19
>         Attachments: 10847-v2.txt, 10847.txt
> I would like to only create a single 0.94 tarball/release that contains the security
code - and drop the non-secure tarballs and releases.
> Let's discuss...

This message was sent by Atlassian JIRA

View raw message