You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "John Vines (Created) (JIRA)" <ji...@apache.org> on 2012/01/05 21:20:39 UTC

[jira] [Created] (ACCUMULO-267) Mapreduce API should not use JobContext to set configuration information

Mapreduce API should not use JobContext to set configuration information
------------------------------------------------------------------------

                 Key: ACCUMULO-267
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-267
             Project: Accumulo
          Issue Type: Bug
          Components: client
            Reporter: John Vines
            Assignee: Billie Rinaldi


JobContext specifically says that it is a read-only view of job information. Our inputformat's configuration calls take JobContext as an input, rip out the Configuration object, and writes to it.

Instead, calls should just take in a Configuration object directly (or a Job object, but that passes in more information than is needed, and can cause discrepancies depending on which mapreduce api).

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

        

[jira] [Resolved] (ACCUMULO-267) Mapreduce API should not use JobContext to set configuration information

Posted by "John Vines (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Vines resolved ACCUMULO-267.
---------------------------------

    Resolution: Fixed
    
> Mapreduce API should not use JobContext to set configuration information
> ------------------------------------------------------------------------
>
>                 Key: ACCUMULO-267
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-267
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: John Vines
>            Assignee: John Vines
>              Labels: mapreduce
>             Fix For: 1.4.0
>
>
> JobContext specifically says that it is a read-only view of job information. Our inputformat's configuration calls take JobContext as an input, rip out the Configuration object, and writes to it.
> Instead, calls should just take in a Configuration object directly (or a Job object, but that passes in more information than is needed, and can cause discrepancies depending on which mapreduce api).

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

        

[jira] [Assigned] (ACCUMULO-267) Mapreduce API should not use JobContext to set configuration information

Posted by "John Vines (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Vines reassigned ACCUMULO-267:
-----------------------------------

    Assignee: John Vines  (was: Billie Rinaldi)
    
> Mapreduce API should not use JobContext to set configuration information
> ------------------------------------------------------------------------
>
>                 Key: ACCUMULO-267
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-267
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: John Vines
>            Assignee: John Vines
>              Labels: mapreduce
>             Fix For: 1.4.0
>
>
> JobContext specifically says that it is a read-only view of job information. Our inputformat's configuration calls take JobContext as an input, rip out the Configuration object, and writes to it.
> Instead, calls should just take in a Configuration object directly (or a Job object, but that passes in more information than is needed, and can cause discrepancies depending on which mapreduce api).

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

        

[jira] [Updated] (ACCUMULO-267) Mapreduce API should not use JobContext to set configuration information

Posted by "John Vines (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Vines updated ACCUMULO-267:
--------------------------------

    Fix Version/s: 1.4.0

We should fix in 1.4 so we can deprecate it there and remove in 1.5
                
> Mapreduce API should not use JobContext to set configuration information
> ------------------------------------------------------------------------
>
>                 Key: ACCUMULO-267
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-267
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: John Vines
>            Assignee: John Vines
>              Labels: mapreduce
>             Fix For: 1.4.0
>
>
> JobContext specifically says that it is a read-only view of job information. Our inputformat's configuration calls take JobContext as an input, rip out the Configuration object, and writes to it.
> Instead, calls should just take in a Configuration object directly (or a Job object, but that passes in more information than is needed, and can cause discrepancies depending on which mapreduce api).

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