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/10/22 19:15:35 UTC

[jira] [Assigned] (SQOOP-1602) Sqoop2: Fix the current balancing across Loaders internal to Sqoop

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

Veena Basavaraj reassigned SQOOP-1602:
--------------------------------------

    Assignee: Qian Xu  (was: Veena Basavaraj)

[~stanleyxu2005] I took the liberty to create a ticket for the issue you raised today.

Also see a related ticket where we want to expose this balancing step to the connector api in future

> Sqoop2:  Fix the current balancing across Loaders internal to Sqoop 
> --------------------------------------------------------------------
>
>                 Key: SQOOP-1602
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1602
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Veena Basavaraj
>            Assignee: Qian Xu
>
> The balancing of the record to the loaders in done internally in SQOOP today
> While writing the Kite Connector Qian noticed that this is not done fairly.
> While I am testing kite connector, I allocated 2 loaders. I thought data will be divided by 50% and 50% to both loaders. But actually the second loader does nothing, because its DataReader does not have any data to provide. Is it by design?
> >> About loaders do not have data in a balanced way.
> My scenario is 4 "jdbc_mysql" extractors to extract 100k row data (10MB). There are 2 Kite loaders to read data.
> This must be a bug that needs to be fixed in SQOOP



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