hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Weil (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6115) Sqoop should allow a "where" clause to avoid having to export entire tables
Date Mon, 29 Jun 2009 06:52:47 GMT

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

Kevin Weil updated HADOOP-6115:

    Attachment: HADOOP-6115.patch

This patch adds the ability to specify a "where" clause to sqoop, in the form

<normal sqoop command> --where "my_row > 0 and my_text like '%sqoop%'"

It also works with sqoop's mysql-specific --local flag, using mysqldump's -w flag.  

> Sqoop should allow a "where" clause to avoid having to export entire tables
> ---------------------------------------------------------------------------
>                 Key: HADOOP-6115
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6115
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: contrib/sqoop
>    Affects Versions: 0.21.0
>            Reporter: Kevin Weil
>            Priority: Minor
>         Attachments: HADOOP-6115.patch
> Sqoop currently only exports at the granularity of a table.  This doesn't work well on
systems with large tables, where the overhead of performing a full dump each time is significant.
 Allowing the user to specify a where clause is a relatively simple task which will give Sqoop
a lot more flexibility.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message