hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ari Rabkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4818) Enable JobTracker Instrumentation API with user job configuration
Date Thu, 18 Dec 2008 02:54:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657657#action_12657657

Ari Rabkin commented on HADOOP-4818:

Can you comment on why we don't want the API to be public?  Seems like that's very limiting...

> Enable JobTracker Instrumentation API with user job configuration
> -----------------------------------------------------------------
>                 Key: HADOOP-4818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>         Environment: Redhat EL 5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.0
>         Attachments: HADOOP-4818-1.patch, HADOOP-4818.patch
> The JobTracker Instrumentation API is currently sending JobTracker configuration to submitJob(conf,
JobID) call.  Instead, this should be changed to submitJob(job.getJobConf(), JobID) to obtain
job related configuration.  i.e., Chukwa could use this API to find out the job history file
location.  In addition, the API should be public for general public to implement useful utilities
to interface with this API.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message