You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Kevin Weil (JIRA)" <ji...@apache.org> on 2009/06/28 01:26:47 UTC

[jira] Commented: (HADOOP-6115) Sqoop should allow a "where" clause to avoid having to export entire tables

    [ https://issues.apache.org/jira/browse/HADOOP-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724906#action_12724906 ] 

Kevin Weil commented on HADOOP-6115:
------------------------------------

I have this working except for in the case of optimized local importing.  Not sure why this is failing ATM because the same command line statement succeeds, but I expect to have a patch by the end of the weekend.

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