[
https://issues.apache.org/jira/browse/FLINK-35331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846933#comment-17846933
]
Hector Sanchez commented on FLINK-35331:
----------------------------------------
Added [PR#742|https://github.com/apache/flink-web/pull/742] with fix.
The shortcode `flink_download` used to create the download links had the
property `source_release_url` mandatory. I just added a conditional so no need
to have that property anymore. This way we can have only the
`binary_release_url` for those binary only downloads.
I have updated the
`[additional_components.yml|https://github.com/apache/flink-web/pull/742/files#diff-45fd031d774cda3e995f0ebe71de328688f561f75000a4d0a234fccd72bd2151]`
file update the hadoop links. I haven't found any other download links with
binary only. Please report if there is any other missing
> Download links for binary releases are displayed as source releases on website
> ------------------------------------------------------------------------------
>
> Key: FLINK-35331
> URL: https://issues.apache.org/jira/browse/FLINK-35331
> Project: Flink
> Issue Type: Bug
> Components: Project Website
> Reporter: Xintong Song
> Priority: Major
> Labels: pull-request-available
>
> Take Pre-bundled Hadoop as examples. The content for downloading are binary
> releases, while the link is displayed as "Pre-bundled Hadoop 2.x.y Source
> Release (asc, sha512)". The problem is caused by misusing
> `source_release_[url|asc_url|sha512_url]` for binary contents in the
> corresponding [yaml
> file.|https://github.com/apache/flink-web/blob/asf-site/docs/data/additional_components.yml]
> There are many similar cases in the webpage.
> And a relevant issues is that, some source releases are displayed as "XXX
> Source Release Source Release", due to including "Source Release" in the
> `name` field of the corresponding yaml file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
