You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2020/05/11 05:58:00 UTC
[jira] [Commented] (FLINK-16850) Make flink-benchmark align with
different releases of Flink
[ https://issues.apache.org/jira/browse/FLINK-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104099#comment-17104099 ]
Yun Tang commented on FLINK-16850:
----------------------------------
[~tzulitai], would you please kindly help to create the 1st commit for the empty repo: https://github.com/apache/flink-benchmarks to migrate from https://github.com/dataArtisans/flink-benchmarks ? Thank you very much.
> 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: Sub-task
> 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)