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

Nitay Joffe updated HCATALOG-516:
---------------------------------

    Description: HCOF methods use Job everywhere when really all they need is 
Configuration/Credentials. In Giraph we have a few places where we don't have a 
Job object but we do have the Configuration/Credentials. When the job starts we 
have the Job object, but later when the workers are deep in their computation 
all they have is the context they need, namely the Configuration (not the whole 
Job). We need to call some HCatalog methods from them because we we want to 
write data multiple times, so it seems cleaner to allow HCatalog methods to 
just take the Configuration object when that is all that is needed.  (was: HCOF 
methods use Job everywhere when really all they need is 
Configuration/Credentials. In Giraph we have a few places where we don't have a 
Job object but we do have the Configuration/Credentials.)
    
> HCOF should use less generic parameters
> ---------------------------------------
>
>                 Key: HCATALOG-516
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-516
>             Project: HCatalog
>          Issue Type: Bug
>    Affects Versions: 0.5
>            Reporter: Nitay Joffe
>             Fix For: 0.5
>
>         Attachments: HCATALOG-516.patch
>
>
> HCOF methods use Job everywhere when really all they need is 
> Configuration/Credentials. In Giraph we have a few places where we don't have 
> a Job object but we do have the Configuration/Credentials. When the job 
> starts we have the Job object, but later when the workers are deep in their 
> computation all they have is the context they need, namely the Configuration 
> (not the whole Job). We need to call some HCatalog methods from them because 
> we we want to write data multiple times, so it seems cleaner to allow 
> HCatalog methods to just take the Configuration object when that is all that 
> is needed.

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

Reply via email to