[
https://issues.apache.org/jira/browse/HDFS-12149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088815#comment-16088815
]
Anu Engineer edited comment on HDFS-12149 at 7/17/17 1:38 AM:
--
[~jnp], [~szetszwo], [~cheersyang], [~xyao], [~msingh], [~nandakumar131],
[~linyiqun], [~vagarychen], [~yuanbo], [~arpitagarwal]
There is an interesting thread here in the Legal section, which we should be
aware of before we post this patch which bring in RocksDB dependency.
TL: DR; Due to the RocksDB License change we might be able to use RocksDB.
Approximately 3 hours ago RocksDB switched over to using Apache 2 License,
before that RocksDB was declared as *persona non grata* in the Apache world.
Details: In the Apache JIRA LEGAL-303, it was clarified that Facebook uses a
license -- "Facebook BSD+Patents license". This was deemed to be not suitable
for use in Apache.
Facebook also clarified that the intent of this license was to be different
from Apache license.
https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16046579=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16046579
Around 12 hours ago (Sat, Jul 15th, 2017) Chris Mattmann send out a circular
to all Apache PMCs that RocksDB falls under Category X license, which are
licenses that cannot be included with Apache products. This naturally means
that we cannot commit a change that has a RocksDB dependency.
Fortunately, around 3 hours ago (Sat, Jul 15th, 2017 7:00 PM), Facebook has
committed a new license to RocksDB. That is a classic Apache 2 license. So I
think we are good to use the RocksDB since it is relicensed as Apache 2 (IANAL).
Please be aware that we might have to revert this change if Apache finally
decides that we cannot use RocksDB.
was (Author: anu):
[~jnp], [~szetszwo], [~cheersyang], [~xyao], [~msingh], [~nandakumar131],
[~linyiqun], [~vagarychen], [~yuanbo], [~arpitagarwal]
There is an interesting thread here in the Legal section, which we should be
aware of before we post this patch which bring in RocksDB dependency.
TL: DR; Due to the RocksDB License change we might be able to use RocksDB.
Approximately 3 hours ago RocksDB switched over to using Apache 2 License,
before that RocksDB was declared as *persona non grata* in the Apache world.
Details: In the Apache JIRA LEGAL-303, it was clarified that Facebook uses a
license -- "Facebook BSD+Patents license". This was deemed to be not suitable
for use in Apache.
Facebook also clarified that the intent of this license was to be different
from Apache license.
https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16046579=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16046579
Around 12 hours ago (Sat, Jul 15th, 2017) Chris Mattmann send out a circular
to all Apache PMCs that RocksDB falls under Category X license, which are
licenses that cannot be included with Apache products. This naturally means
that we cannot commit a change that has a RocksDB dependency.
Fortunately, around 3 hours ago (Sat, Jul 15th, 2017 7:00 PM), Facebook has
committed a new license to RocksDB. That is a classic Apache 2 license. So I
think we are good to use the RocksDB since it is relicensed in Apache (IANAL).
Please be aware that we might have to revert this change if Apache finally
decides that we cannot use RocksDB.
> Ozone: RocksDB implementation of ozone metadata store
> -
>
> Key: HDFS-12149
> URL: https://issues.apache.org/jira/browse/HDFS-12149
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>
> HDFS-12069 added a general interface for ozone metadata store, we already
> have a leveldb implementation, this JIRA is to track the work of rocksdb
> implementation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
