[
https://issues.apache.org/jira/browse/HIVE-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127896#comment-13127896
]
Robert Surówka commented on HIVE-2500:
--------------------------------------
Apparently this diff is still wrong (I will have to do small fix to
MapReduceTask.java, when debug off, it will add just one if check for a key
being in a map per execute() call of that task, and only if new JVM is about to
be started).
As I am working on it I plan to add following features:
-user could specify port on which Hive JVM will wait (8000 will be default).
-user could specify whether child JVMs should be also started in debug mode
(default: not). If started in debug mode, child JVMs will wait on a different
ports than parent (and I will try to make it in such a way, so probability of
ports collision would be very small (to make it impossible one would need to
use some between process communication, since children can start their own
children, and I don't want to do that yet (especially that HIVE may be deployed
on various os-es). User will know on which port new JVMs are waiting, since
upon start they print that information. New JVMs will be started on ports
higher than port of the initial JVM - so if someone needs, he can set initial
port to be higher than any other already used TCP port).
ETA: by mid of next week (hopefully)
> 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
>
>
--
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
