flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9718) Add enviroment variable in start-scala-shell.sh to enable remote debug
Date Wed, 04 Jul 2018 08:08:00 GMT

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

ASF GitHub Bot commented on FLINK-9718:
---------------------------------------

Github user zjffdu commented on a diff in the pull request:

    https://github.com/apache/flink/pull/6245#discussion_r200040940
  
    --- Diff: flink-scala-shell/start-script/start-scala-shell.sh ---
    @@ -19,6 +19,9 @@
     
     # from scala-lang 2.10.4
     
    +# Uncomment the following line to enable remote debug
    +# export FLINK_SCALA_SHELL_JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005"
    --- End diff --
    
    I don't find something like `flink-env.sh` for specify flink related env variable. So
I just put it in `start-scala-shell.sh` directly. I don't think bool flag is proper, as it
hide the details of remote debug info, like which port to listen. I believe most of apache
project use `*JAVA_OPTS` for remote debug which is very common. What do you think ?


> Add enviroment variable in start-scala-shell.sh to enable remote debug
> ----------------------------------------------------------------------
>
>                 Key: FLINK-9718
>                 URL: https://issues.apache.org/jira/browse/FLINK-9718
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Jeff Zhang
>            Priority: Major
>              Labels: pull-request-available
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message