[
https://issues.apache.org/jira/browse/FLINK-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676853#comment-17676853
]
Yun Tang commented on FLINK-16850:
----------------------------------
bq. Yun Tang, would you like to complete this ticket, now that we have
migrated benchmarks to the apache repository? I think the only remaining thing
to do is to update creating release guide, maybe backed up by a shell script in
flink-benchmarks repo, to bump versions/create desired branches?
[~pnowojski] It seems I missed to complete this ticket with updating the
creating release guide. Recently, I want to test an older Flink version with
flink-benchmarks but find it would take some extra energy to make current
flink-benchmarks could run under that version.
Thus, I come back to this ticket and reopen it. I will also launch a short
discussion in the dev mailing list.
> 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
> Assignee: Yun Tang
> Priority: Major
> Fix For: 1.13.0
>
>
> 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.20.10#820010)
