You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2012/09/18 22:13:07 UTC

[jira] [Updated] (NUTCH-1357) All gora mapreduce functionality should go through StorageUtils

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

Lewis John McGibbney updated NUTCH-1357:
----------------------------------------

    Fix Version/s:     (was: 2.1)
                   2.2
    
> All gora mapreduce functionality should go through StorageUtils
> ---------------------------------------------------------------
>
>                 Key: NUTCH-1357
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1357
>             Project: Nutch
>          Issue Type: Improvement
>    Affects Versions: nutchgora
>            Reporter: Ferdy Galema
>             Fix For: 2.2
>
>
> I am trying to make the concept of crawlId work for ALL nutch jobs: it seems the biggest problem with it not working as expected is because of the various ways gora mapreduce is used in nutch.
> Some jobs use StorageUtils, some use GoraMapper/GoraReduce, some even use directly GoraInputFormat/GoraOutputFormat. But the only place the translation is made from crawlId into a schema name is in StorageUtils! Currently I am converting all calls to Gora* mapreduce initializing code to StorageUtils calls.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira