You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/12/24 16:26:13 UTC

[jira] [Assigned] (SQOOP-1938) DOC:update the sqoop MR engine implementation details

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

Veena Basavaraj reassigned SQOOP-1938:
--------------------------------------

    Assignee: Veena Basavaraj

> DOC:update the sqoop MR engine implementation details
> -----------------------------------------------------
>
>                 Key: SQOOP-1938
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1938
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>
> https://cwiki.apache.org/confluence/display/SQOOP/Sqoop+MR+Execution+Engine
> 1. Why we need SqoopWritable, what can be done in future?
> 2. Even though we call sqoop as a map only, is that how it always works? what happend when numLoaders is non zero
> {code}
>       // Set number of reducers as number of configured loaders  or suppress
>       // reduce phase entirely if loaders are not set at all.
>       if(request.getLoaders() != null) {
>         job.setNumReduceTasks(request.getLoaders());
>       } else {
>         job.setNumReduceTasks(0);
>       }
> {code}
> 3. Internals of SqoopNullOutputFormat and how SqoopWritable is used in it



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)