[
https://issues.apache.org/jira/browse/FLINK-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031906#comment-15031906
]
ASF GitHub Bot commented on FLINK-3077:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1418#issuecomment-160655415
I think for release builds, the commit ID may be null, depending on how the
uploaded release binary was built...
> Add "version" command to CliFrontend for showing the version of the
> installation
> --------------------------------------------------------------------------------
>
> Key: FLINK-3077
> URL: https://issues.apache.org/jira/browse/FLINK-3077
> Project: Flink
> Issue Type: Improvement
> Components: Command-line client
> Reporter: Robert Metzger
> Assignee: Sachin Goel
> Fix For: 1.0.0
>
>
> I have the bin directory of Flink in my $PATH variable, so I can just do
> "flink run" on the command line for executing stuff.
> However, I have multiple Flink versions locally and its hard to find out
> which installation the bash is picking in the end.
> adding a simple "version" command will resolve that issue and I consider it
> helpful in general.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
