[ 
https://issues.apache.org/jira/browse/HIVE-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Surówka updated HIVE-2500:
---------------------------------

    Attachment: HIVE-2500.3.patch

The changes with this patch are as follows (I made some design changes to the 
comment from OCT 14) :

-now the child JVMs should work correctly with debug (user decides whether they 
should be also started in debug mode or not).
-When child JVM starts in debug mode it will start listening on some random 
unused TCP port.
-By default child JVMs start in debug mode, but don't wait with execution for 
the debugger to connect (yet if someone would later decide that he actually 
wants to connect to any of them, he will be able to do that).
-user can specify debug options, as described in debug_help()
-I am very unproficient in bash, so if there are any changes you would like to 
see to make that code look better please let me know.
-Most ugly part of this patch are probably the regex expressions/string 
operations added to MapRedTask. They could be made significantly simpler, if 
additional environment variables were exported, and totally removed if small 
changes to hadoop starting scripts would be made. Yet I decided (maybe wrongly) 
that it's best to close all that entropy in configureDebugVariablesForChildJVM 
method instead of spilling it around (especially that it's just for debug).   

The current diff is at: https://reviews.apache.org/r/2354/diff/3/
                
> Allow Hive to be debugged remotely
> ----------------------------------
>
>                 Key: HIVE-2500
>                 URL: https://issues.apache.org/jira/browse/HIVE-2500
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Robert Surówka
>            Assignee: Robert Surówka
>            Priority: Minor
>         Attachments: HIVE-2500.1.patch, HIVE-2500.2.patch, HIVE-2500.3.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to