[
https://issues.apache.org/jira/browse/FLINK-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613543#comment-16613543
]
ASF GitHub Bot commented on FLINK-10341:
----------------------------------------
TisonKun commented on issue #6690: [FLINK-10341][shell script] Add option to
print flink command when running bin/flink
URL: https://github.com/apache/flink/pull/6690#issuecomment-421019008
I am not a bash expert and find @dawidwys, you are right. To be accurate, it
would be `bash -x COMMAND 2>&1 | grep exec` or something, otherwise it prints
scare text.
From my side it is a frequent demand to see what the real command executed
so I would approve this change. We could achieve it even just by hacking this
script locally. So the problem is whether we provide such feature within the
project and, well, the print format and the approach by setenv not optimized so
it looks like no more than just `bash -x`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add option to print flink command when running bin/flink
> --------------------------------------------------------
>
> Key: FLINK-10341
> URL: https://issues.apache.org/jira/browse/FLINK-10341
> Project: Flink
> Issue Type: Improvement
> Components: Startup Shell Scripts
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
> Priority: Major
> Labels: pull-request-available
>
> It would be very useful if I can see the final java command which is used to
> run flink program, specially when I hit very weird issue as flink
> contributor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
