giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-144) GiraphJob should not extend Job (users should not be able to call Job methods like waitForCompletion or setMapper..etc)
Date Sun, 25 Mar 2012 20:29:26 GMT

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

Jakob Homan commented on GIRAPH-144:
------------------------------------

Sorry, had missed the first ping.  Composition is definitely the way to go, I'm just still
a bit worried about exposing the underlying Job.  Once we go to YARN, there's no reason to
think that there will be a Job anymore to expose.  It might be time to pull in Hadoop's interface
classifications and mark that method as private unstable...  But this approach is better than
what we have now, so go ahead with it until we come up with something better.
                
> GiraphJob should not extend Job  (users should not be able to call Job methods like waitForCompletion
or setMapper..etc)
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GIRAPH-144
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-144
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Dave
>            Assignee: Avery Ching
>         Attachments: GIRAPH-144.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>


--
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

        

Mime
View raw message