[jira] [Commented] (SQOOP-671) Mapreduce counters are not used in generated mapreduce jobs

["Hari Shreedharan (JIRA)" <ji...@apache.org>]

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

Hari Shreedharan commented on SQOOP-671:
----------------------------------------

I don't understand losing "some counters." As far as I can see the counters are not being pulled in anywhere. This is not related to the way the job is submitted right? It is just that we don't really wait for completion - and the querying needs to happen when a request is made from the client, so when the stats calls is made, we query the MR job to get the stats.
                
> Mapreduce counters are not used in generated mapreduce jobs
> -----------------------------------------------------------
>
>                 Key: SQOOP-671
>                 URL: https://issues.apache.org/jira/browse/SQOOP-671
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>             Fix For: 2.0.0
>
>
> As we're using threads to pass data instead of hadoop native way, we're loosing some counters (bytes written, number of entries) that might be interested for end user. We should propagate those counters ourselves.

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