[
https://issues.apache.org/jira/browse/FLINK-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074486#comment-17074486
]
Arvid Heise commented on FLINK-16850:
-------------------------------------
{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).
{quote}
Would they even check if it's just a test dependency? A user should actually
not see the dependency at all, except if they are really scanning all artifacts.
Promoting might work but I'd evaluate other options first.
> 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)
