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

Aki Tanaka commented on FLINK-18898:
------------------------------------

[~chesnay] Thank you very much for your reply! I built Flink manually using 
Apache BigTop.

After some further investigation, I confirmed that the 
.flink-runtime.version.properties file was removed when creating rpm package. 
Re-packaging jar file (brp-java-repack-jars) removed the property file. 

 
{code:java}
$ jar tvf flink-1.11.0-bin/flink-1.11.0/lib/flink-dist_2.12-1.11.0.jar |grep 
flink-runtime.version.properties
 997 Wed Aug 12 15:27:38 UTC 2020 .flink-runtime.version.properties
$ rpm2cpio /workspace/build/flink/rpm/RPMS/noarch/flink-1.11.0-1.noarch.rpm | 
cpio -idv
$ jar tvf usr/lib/flink/lib/flink-dist_2.12-1.11.0.jar |grep 
flink-runtime.version.properties
$
{code}
I was able to solve this issue by disabling the call of the 
brp-java-repack-jars script. I personally think it would be better not to use 
the dot file name to avoid this behavior if there is no specific reason to use 
dot file. 

If you think we don't need to fix this in Flink end, please feel free to 
resolve this ticket. Thank you.

> .flink-runtime.version.properties file does not exist in flink-dist.jar
> -----------------------------------------------------------------------
>
>                 Key: FLINK-18898
>                 URL: https://issues.apache.org/jira/browse/FLINK-18898
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: 1.11.0
>            Reporter: Aki Tanaka
>            Priority: Major
>
> I noticed that .flink-runtime.version.properties file does not exist in 
> flink-dist jar file. Due to lack of this property file, running 'flink 
> --version' returns unknown version.
> If I rename the '.flink-runtime.version.properties' file to 
> 'flink-runtime.version.properties', I was able to contain the property file 
> in the flink-dist jar. If this approach is fine, I'll create the pull 
> request. If not, I would like to know the best way to work around the problem.



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

Reply via email to