Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1681680078.1246666067317.JavaMail.jira@brutus>
Date: Fri, 3 Jul 2009 17:07:47 -0700 (PDT)
From: "Aaron Kimball (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-674) Sqoop should allow a "where" clause
 to avoid having to export entire tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron Kimball updated MAPREDUCE-674:
------------------------------------

    Status: Patch Available  (was: Open)

> Sqoop should allow a "where" clause to avoid having to export entire tables
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-674
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-674
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: contrib/sqoop
>    Affects Versions: 0.21.0
>            Reporter: Kevin Weil
>            Priority: Minor
>         Attachments: HADOOP-6115.patch, MAPREDUCE-674.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.