[
https://issues.apache.org/jira/browse/HIVE-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051471#comment-15051471
]
Naveen Gangam commented on HIVE-11866:
--------------------------------------
[~thejas] I am seeing no response on the LEGAL jira except a push from Apache
DS team to adopt ApacheDS for testing. I have sought some internal legal advice
on this matter. Here is what I got back
"When you say something "is not compatible with Apache 2" are you referring to
a compatibility requirement imposed by the Apache Hive project particularly?
Or are you just saying that the ENTIRE distribution, including all its
dependencies, can no longer be released under Apache 2?
In either case, the UnboundIP license
(https://docs.ldap.com/ldap-sdk/docs/LICENSE-UnboundID-LDAPSDK.txt) does
include a clause allowing UnboundIP to unilaterally terminate the license at
any time.
Notwithstanding anything contained in this Agreement to the contrary, UnboundID
may also, in its sole discretion, terminate or suspend access to the SDK to You
or any end user at any time.
Naturally, that makes the SDK's inclusion in a project, particularly as a
foundational tool, rather risky. This may be why the jira considers the
license "not compatible". But from a cursory review I understand that
UnboundID alternatively provides the SDK under the GPL or LGPL licenses
(https://docs.ldap.com/ldap-sdk/docs/index.html)
(https://docs.ldap.com/ldap-sdk/docs/LICENSE.txt). If no one is modifying the
SDK, but simply linking to it at arms-length as an independent file in its
original form, I'm not sure why anyone would object to including it in Apache
Hive as an LGPL dependency (Naveen seems to suggest below that he'll be using
it at arms-length). If Hive requires that ALL dependencies be Apache
licensed, then this wouldn't be acceptable. But taking a copy of the SDK under
the LGPL license shouldn't prevent you from releasing the rest of Hive under
the Apache license. Furthermore, Naveen seems to indicate that the SDK will
only appear internally on the Apache Hive machines (e.g., it won't be
redistributed with the package provided to customers). If that's the case,
then use of an internal copy of the SDK solely on the Hive machines would be
particularly benign. See, e.g.,
(https://docs.ldap.com/ldap-sdk/docs/ldapsdk-faq.html#internal)
There are no restrictions on the use of the LDAP SDK in an application that is
for internal use only and will not be redistributed outside of your
organization.
(Still, if developers [inside and outside the Hive group] will be regularly
downloading and uploading test framework builds that include the SDK from the
Hive group, you might make the LGPL election explicit as a precaution)
So you may just have Naveen confirm that an LGPL 2.1 license would be
acceptable to the Hive group and that the SDK copy will remain within Hive
(e.g., the test framework is not distributed, except when developers push /
pull the build from a Hive machine).
[I'm not sure which edition (standard, minimal, or commercial) of the SDK
Naveen is contemplating using, but all three seem to have the same licensing
options for his purpose (https://www.ldap.com/unboundid-ldap-sdk-for-java).]
"
Given that our usage is "at arms length" and the binaries wouldnt be packaged
in the end product, do you think we have enough to re-insert this fix? Thanks
> Add framework to enable testing using LDAPServer using LDAP protocol
> --------------------------------------------------------------------
>
> Key: HIVE-11866
> URL: https://issues.apache.org/jira/browse/HIVE-11866
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 1.3.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Attachments: HIVE-11866.2.patch, HIVE-11866.patch
>
>
> Currently there is no unit test coverage for HS2's LDAP Atn provider using a
> LDAP Server on the backend. This prevents testing of the LDAPAtnProvider with
> some realistic usecases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
