[ 
https://issues.apache.org/jira/browse/FLINK-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072592#comment-17072592
 ] 

Piotr Nowojski commented on FLINK-16850:
----------------------------------------

About the last point of lack of access. Probably for the semi legal semi 
psychological concerns we still can not add GPLv2 dependency to the Flink repo. 
Technically we could:

{quote}
But JMH actually has GPLv2 with Classpath Exception, like pretty much all of 
the core Java libraries. So it should be okay with ASL2, at least when we don't 
build shaded or fat jars, or as a test dependency. In fact, Apache Arrow is 
using it like that.
{quote}

but explaining it to everyone that checks for GPLv2 is quite painful (there are 
Flink users that are actually checking those kind of things).

Another solution would be to promote {{flink-benchmarks}} to Apache project 
(independent of the main Flink repo), but with the same committers, and add to 
our release manual one step of running some script in the 
{{apache/flink-benchmarks}} repository, that would bump the release version, 
create release branch etc.

> Make flink-benchmark align with different releases of Flink
> -----------------------------------------------------------
>
>                 Key: FLINK-16850
>                 URL: https://issues.apache.org/jira/browse/FLINK-16850
>             Project: Flink
>          Issue Type: Improvement
>          Components: Benchmarks
>    Affects Versions: 1.10.0
>            Reporter: Yun Tang
>            Priority: Major
>
> Currently, [flink-benchmark|https://github.com/dataArtisans/flink-benchmarks] 
> does not have any releases to align with release branches of Flink. Just 
> change the {{flink.version}} when executing benchmark is not enough as 
> {{flink-benchmark}} always use the latset interfaces which might not existed 
> in previous Flink versions. Take FLINK-15222 for example, this let 
> {{flink-benchmark}} to use new version of interface which is only existed 
> after Flink-1.11
> I think we could also let {{flink-benchmark}} to have releases or at least 
> specific branch to align with releases of Flink.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to