Migrating extendedset from Metamarkets.#3694
Conversation
There was a problem hiding this comment.
This should probably mention the original codebase too
There was a problem hiding this comment.
Updated the NOTICE.
|
This needs to attribute the original codebase |
|
@fjy @gianm Found this url Code repo Also, what do you think adding below in NOTICE (assuming original code is missing from sourceforge)
|
ab02ce5 to
4f1b007
Compare
|
👍 |
|
NB metamx/extendedset#10 was merged in a branch upstream after this PR was filed. |
|
@akashdw sorry for the delay, I think we're good here. If you can fix merge conflicts I can merge |
ffb097a to
ff0eead
Compare
|
@drcrallen Sorry for the delay, I was out for sometime. I rebased the pr but checkstyle is failing because of the license headers on extended set files. I can not change the license because extendedset is a fork of someone else's repository and licensed to Metamarkets under a CLA is not true. |
|
@drcrallen I added a suppress header check for extendedset files. |
* Migrating extendedset from Metamarkets. * Notice change * More details in NOTICE * NOTICE formatting. * suppress header checkstlye for extendedset.
Migrating extendedset from metamarkets. This migration will be helpful to deal problems around having separate PRs and release cycle of Druid and extendedset . This PR is continuation of #3647.
Note:
extendedsetis actually a fork of someone else's repository andlicensed to Metamarkets under a CLAis not true.