[
https://issues.apache.org/jira/browse/SQOOP-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494786#comment-13494786
]
Hari Shreedharan commented on SQOOP-671:
----------------------------------------
I am not entirely happy with the way we are handling writes to the FS. There is
too much of uncertainity in the code - especially in the
SqoopOutputFormatLoadExecutor class. This patch for now provides the byte count
when the format() method is called - assuming that at that point the data has
been "transferred." This patch, like everything else in sqoop 2 currently
supports only the CSV. I intend to update the way the data is written out in a
future patch: SQOOP-691.
> 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
> Assignee: Hari Shreedharan
> Fix For: 2.0.0
>
> Attachments: SQOOP-671-1.patch, SQOOP-671-2.patch, SQOOP-671-3.patch,
> SQOOP-671-4.patch, SQOOP-671-5.patch
>
>
> 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
