The failure is from TestAvroImport under JDK 1.6 (specifically the testcase testNonstandardCharactersInColumnName)
It looks like a JDK 1.6 specific bug. Venkat On 6/29/15, 10:04 PM, "Hudson (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/SQOOP-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14607498#comment-14607498 > ] > >Hudson commented on SQOOP-2334: >------------------------------- > >FAILURE: Integrated in Sqoop-ant-jdk-1.6-hadoop100 #971 (See >[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop100/971/]) >SQOOP-2334: Sqoop Volume Per Mapper (venkat: >https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=e21529ac6aad03bdcb572c61420e258be2d823fe) >* src/java/org/apache/sqoop/mapreduce/DataDrivenImportJob.java >* src/test/org/apache/sqoop/mapreduce/db/TestIntegerSplitter.java >* src/java/org/apache/sqoop/tool/ImportTool.java >* src/docs/man/import-args.txt >* src/java/org/apache/sqoop/tool/BaseSqoopTool.java >* src/java/org/apache/sqoop/mapreduce/db/DateSplitter.java >* src/java/org/apache/sqoop/config/ConfigurationConstants.java >* src/java/org/apache/sqoop/mapreduce/db/DataDrivenDBInputFormat.java >* src/java/org/apache/sqoop/SqoopOptions.java >* src/java/org/apache/sqoop/config/ConfigurationHelper.java >* src/java/org/apache/sqoop/mapreduce/db/IntegerSplitter.java >* src/docs/user/import.txt > > >> Sqoop Volume Per Mapper >> ----------------------- >> >> Key: SQOOP-2334 >> URL: https://issues.apache.org/jira/browse/SQOOP-2334 >> Project: Sqoop >> Issue Type: New Feature >> Affects Versions: 1.4.5 >> Reporter: Atul Gupta >> Assignee: Rakesh Sharma >> Fix For: 1.4.7 >> >> Attachments: SQOOP-2334.patch, SQOOP-2334_1.patch, SQOOP-2334_2.patch >> >> >> There is no way where user can define the upper limit of volume that each >> mapper can handle. Current Sqoop does the calculation based on mapper by >> Switch -m and --split-by but this does not give control user to specify the >> upper limit of volume handle by the mapper . >> if we can add such functionality in the Sqoop that would help us to load the >> bigger data set in case we don't have continuous key data available and >> there is a huge gap in maximum and minimum data set value. > > > >-- >This message was sent by Atlassian JIRA >(v6.3.4#6332) >
