[
https://issues.apache.org/jira/browse/MAPREDUCE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727195#action_12727195
]
Hadoop QA commented on MAPREDUCE-674:
-------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12412131/MAPREDUCE-674.patch
against trunk revision 790971.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/352/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/352/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/352/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/352/console
This message is automatically generated.
> 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.