[jira] [Commented] (SQOOP-2949) SQL Syntax error when split-by column is of character type and min or max value has single quote inside it
[
https://issues.apache.org/jira/browse/SQOOP-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597566#comment-16597566
]
Fero Szabo commented on SQOOP-2949:
---
Hi [~gireeshp],
Do you have an update on this issue? We'd like to get this one into the next
release, if possible... :)
> SQL Syntax error when split-by column is of character type and min or max
> value has single quote inside it
> --
>
> Key: SQOOP-2949
> URL: https://issues.apache.org/jira/browse/SQOOP-2949
> Project: Sqoop
> Issue Type: Bug
>Affects Versions: 1.4.6
> Environment: Sqoop 1.4.6
> Run on Hadoop 2.6.0
> On Ubuntu
>Reporter: Gireesh Puthumana
>Assignee: Gireesh Puthumana
>Priority: Major
>
> Did a sqoop import from mysql table "emp", with split-by column "ename",
> which is a varchar(100) type.
> +Used below command:+
> sqoop import --connect jdbc:mysql://localhost/testdb --username root
> --password * --table emp --m 2 --target-dir /sqoopTest/5 --split-by ename;
> +Ename has following records:+
> | ename |
> | gireesh |
> | aavesh |
> | shiva' |
> | jamir |
> | balu|
> | santosh |
> | sameer |
> Min value is "aavesh" and max value is "shiva'" (please note the single quote
> inside max value).
> When run, it tried to execute below query in mapper 2 and failed:
> SELECT `ename`, `eid`, `deptid` FROM `emp` AS `emp` WHERE ( `ename` >=
> 'jd聯聭聪G耀' ) AND ( `ename` <= 'shiva'' )
> +Stack trace:+
> {quote}
> 2016-06-05 16:54:06,749 ERROR [main]
> org.apache.sqoop.mapreduce.db.DBRecordReader: Top level exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error
> in your SQL syntax; check the manual that corresponds to your MySQL server
> version for the right syntax to use near ''shiva'' )' at line 1
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
> at com.mysql.jdbc.Util.getInstance(Util.java:387)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:942)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3966)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3902)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2526)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2673)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2549)
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
> at
> com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962)
> at
> org.apache.sqoop.mapreduce.db.DBRecordReader.executeQuery(DBRecordReader.java:111)
> at
> org.apache.sqoop.mapreduce.db.DBRecordReader.nextKeyValue(DBRecordReader.java:235)
> at
> org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:553)
> at
> org.apache.hadoop.mapreduce.task.MapContextImpl.nextKeyValue(MapContextImpl.java:80)
> at
> org.apache.hadoop.mapreduce.lib.map.WrappedMapper$Context.nextKeyValue(WrappedMapper.java:91)
> at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
> at
> org.apache.sqoop.mapreduce.AutoProgressMapper.run(AutoProgressMapper.java:64)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:784)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Review Request 68570: SQOOP-3373: Document simple and incremental import into S3
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68570/#review208134 --- Ship it! Hi Bogi, Thank you for adding this thourogh S3 documentation, both ant docs and gradle docs work fine, ship it! - Szabolcs Vasas On Aug. 30, 2018, 12:20 p.m., Boglarka Egyed wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68570/ > --- > > (Updated Aug. 30, 2018, 12:20 p.m.) > > > Review request for Sqoop, daniel voros, Fero Szabo, and Szabolcs Vasas. > > > Bugs: SQOOP-3373 > https://issues.apache.org/jira/browse/SQOOP-3373 > > > Repository: sqoop-trunk > > > Description > --- > > Documenting simple and incremental import into Amazon S3. > > > Diffs > - > > src/docs/user/SqoopUserGuide.txt 8d9c12d1cd1c39b788ef8d971eecf982d6974e3b > src/docs/user/s3.txt PRE-CREATION > > > Diff: https://reviews.apache.org/r/68570/diff/2/ > > > Testing > --- > > ant docs > > > Thanks, > > Boglarka Egyed > >
Re: Review Request 68541: SQOOP-3104: Create test categories instead of test suites and naming conventions
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68541/#review208128 --- Hi Nguyen, I found a couple of test classes which are not categorized, can you please check them? org.apache.sqoop.util.TestDirCleanupHook org.apache.sqoop.util.TestFileSystemUtil org.apache.sqoop.util.TestMainframeFTPClientUtils org.apache.sqoop.util.TestOptionsFileExpansion org.apache.sqoop.util.TestSqoopJsonUtil org.apache.sqoop.util.TestSubstitutionUtils - Szabolcs Vasas On Aug. 28, 2018, 3:52 p.m., Nguyen Truong wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68541/ > --- > > (Updated Aug. 28, 2018, 3:52 p.m.) > > > Review request for Sqoop. > > > Bugs: SQOOP-3104 > https://issues.apache.org/jira/browse/SQOOP-3104 > > > Repository: sqoop-trunk > > > Description > --- > > We are currently unsing test naming conventions to differentiate between > ManualTests, Unit tests and 3rd party tests. Instead of that, I implemented > junit categories which will allow us to have more categories in the future. > This would also remove the reliance on the test class name. > > Test categories skeleton: > SqoopTest _ UnitTest > |__ IntegrationTest > |__ ManualTest > > ThirdPartyTest _ CubridTest >|__ Db2Test >|__ MainFrameTest >|__ MysqlTest >|__ NetezzaTest >|__ OracleTest >|__ PostgresqlTest >|__ SqlServerTest > > KerberizedTest > > Categories explanation: > * SqoopTest: Group of the big categories, including: > - UnitTest: It tests one class only with its dependencies mocked or > if the dependency > is lightweight we can keep it. It must not start a minicluster or an > hsqldb database. > It does not need JCDB drivers. > - IntegrationTest: It usually tests a whole scenario. It may start up > miniclusters, > hsqldb and connect to external resources like RDBMSs. > - ManualTest: This should be a deprecated category which should not > be used in the future. > It only exists to mark the currently existing manual tests. > * ThirdPartyTest: An orthogonal hierarchy for tests that need a JDBC > driver and/or a docker > container/external RDBMS instance to run. Subcategories express what kind > of external > resource the test needs. E.g: OracleTest needs an Oracle RDBMS and Oracle > driver on the classpath > * KerberizedTest: Test that needs Kerberos, which needs to be run on a > separate JVM. > > Opinions are very welcomed. Thanks! > > > Diffs > - > > build.gradle fc7fc0c4c > src/test/org/apache/sqoop/TestConnFactory.java fb6c94059 > src/test/org/apache/sqoop/TestIncrementalImport.java 29c477954 > src/test/org/apache/sqoop/TestSqoopOptions.java e55682edf > src/test/org/apache/sqoop/accumulo/TestAccumuloUtil.java 631eeff5e > src/test/org/apache/sqoop/authentication/TestKerberosAuthenticator.java > f5700ce65 > src/test/org/apache/sqoop/db/TestDriverManagerJdbcConnectionFactory.java > 244831672 > > src/test/org/apache/sqoop/db/decorator/TestKerberizedConnectionFactoryDecorator.java > d3e3fb23e > src/test/org/apache/sqoop/hbase/HBaseKerberizedConnectivityTest.java > 3bfb39178 > src/test/org/apache/sqoop/hbase/TestHBasePutProcessor.java e78a535f4 > src/test/org/apache/sqoop/hcat/TestHCatalogBasic.java ba05cabbb > > src/test/org/apache/sqoop/hive/HiveServer2ConnectionFactoryInitializerTest.java > 4d2cb2f88 > src/test/org/apache/sqoop/hive/TestHiveClientFactory.java a3c2dc939 > src/test/org/apache/sqoop/hive/TestHiveMiniCluster.java 419f888c0 > src/test/org/apache/sqoop/hive/TestHiveServer2Client.java 02617295e > src/test/org/apache/sqoop/hive/TestHiveServer2ParquetImport.java b55179a4f > src/test/org/apache/sqoop/hive/TestHiveServer2TextImport.java 410724f37 > src/test/org/apache/sqoop/hive/TestHiveTypesForAvroTypeMapping.java > 276e9eaa4 > src/test/org/apache/sqoop/hive/TestTableDefWriter.java 626ad22f6 > src/test/org/apache/sqoop/hive/TestTableDefWriterForExternalTable.java > f1768ee76 > src/test/org/apache/sqoop/io/TestCodecMap.java e71921823 > src/test/org/apache/sqoop/io/TestLobFile.java 2bc95f283 > src/test/org/apache/sqoop/io/TestNamedFifo.java a93784e08 > src/test/org/apache/sqoop/io/TestSplittableBufferedWriter.java c59aa26ad > src/test/org/apache/sqoop/lib/TestBlobRef.java b271d3c7b > src/test/org/apache/sqoop/lib/TestBooleanParser.java 914ab37e4 >
[jira] [Updated] (SQOOP-3373) Document simple and incremental import into S3
[ https://issues.apache.org/jira/browse/SQOOP-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boglarka Egyed updated SQOOP-3373: -- Attachment: SQOOP-3373.patch > Document simple and incremental import into S3 > -- > > Key: SQOOP-3373 > URL: https://issues.apache.org/jira/browse/SQOOP-3373 > Project: Sqoop > Issue Type: Sub-task >Affects Versions: 1.4.7 >Reporter: Boglarka Egyed >Assignee: Boglarka Egyed >Priority: Major > Attachments: SQOOP-3373.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68570: SQOOP-3373: Document simple and incremental import into S3
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68570/ --- (Updated Aug. 30, 2018, 12:20 p.m.) Review request for Sqoop, daniel voros, Fero Szabo, and Szabolcs Vasas. Changes --- Fixed typo Bugs: SQOOP-3373 https://issues.apache.org/jira/browse/SQOOP-3373 Repository: sqoop-trunk Description --- Documenting simple and incremental import into Amazon S3. Diffs (updated) - src/docs/user/SqoopUserGuide.txt 8d9c12d1cd1c39b788ef8d971eecf982d6974e3b src/docs/user/s3.txt PRE-CREATION Diff: https://reviews.apache.org/r/68570/diff/2/ Changes: https://reviews.apache.org/r/68570/diff/1-2/ Testing --- ant docs Thanks, Boglarka Egyed
Review Request 68570: SQOOP-3373: Document simple and incremental import into S3
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68570/ --- Review request for Sqoop, daniel voros, Fero Szabo, and Szabolcs Vasas. Bugs: SQOOP-3373 https://issues.apache.org/jira/browse/SQOOP-3373 Repository: sqoop-trunk Description --- Documenting simple and incremental import into Amazon S3. Diffs - src/docs/user/SqoopUserGuide.txt 8d9c12d1cd1c39b788ef8d971eecf982d6974e3b src/docs/user/s3.txt PRE-CREATION Diff: https://reviews.apache.org/r/68570/diff/1/ Testing --- ant docs Thanks, Boglarka Egyed
Re: Review Request 68541: SQOOP-3104: Create test categories instead of test suites and naming conventions
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68541/#review208124 --- Just an FYI: I have now found another test interdependency when running the tests with this patch applied, submitted a fix for it in this patch: https://issues.apache.org/jira/browse/SQOOP-3375 - Szabolcs Vasas On Aug. 28, 2018, 3:52 p.m., Nguyen Truong wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68541/ > --- > > (Updated Aug. 28, 2018, 3:52 p.m.) > > > Review request for Sqoop. > > > Bugs: SQOOP-3104 > https://issues.apache.org/jira/browse/SQOOP-3104 > > > Repository: sqoop-trunk > > > Description > --- > > We are currently unsing test naming conventions to differentiate between > ManualTests, Unit tests and 3rd party tests. Instead of that, I implemented > junit categories which will allow us to have more categories in the future. > This would also remove the reliance on the test class name. > > Test categories skeleton: > SqoopTest _ UnitTest > |__ IntegrationTest > |__ ManualTest > > ThirdPartyTest _ CubridTest >|__ Db2Test >|__ MainFrameTest >|__ MysqlTest >|__ NetezzaTest >|__ OracleTest >|__ PostgresqlTest >|__ SqlServerTest > > KerberizedTest > > Categories explanation: > * SqoopTest: Group of the big categories, including: > - UnitTest: It tests one class only with its dependencies mocked or > if the dependency > is lightweight we can keep it. It must not start a minicluster or an > hsqldb database. > It does not need JCDB drivers. > - IntegrationTest: It usually tests a whole scenario. It may start up > miniclusters, > hsqldb and connect to external resources like RDBMSs. > - ManualTest: This should be a deprecated category which should not > be used in the future. > It only exists to mark the currently existing manual tests. > * ThirdPartyTest: An orthogonal hierarchy for tests that need a JDBC > driver and/or a docker > container/external RDBMS instance to run. Subcategories express what kind > of external > resource the test needs. E.g: OracleTest needs an Oracle RDBMS and Oracle > driver on the classpath > * KerberizedTest: Test that needs Kerberos, which needs to be run on a > separate JVM. > > Opinions are very welcomed. Thanks! > > > Diffs > - > > build.gradle fc7fc0c4c > src/test/org/apache/sqoop/TestConnFactory.java fb6c94059 > src/test/org/apache/sqoop/TestIncrementalImport.java 29c477954 > src/test/org/apache/sqoop/TestSqoopOptions.java e55682edf > src/test/org/apache/sqoop/accumulo/TestAccumuloUtil.java 631eeff5e > src/test/org/apache/sqoop/authentication/TestKerberosAuthenticator.java > f5700ce65 > src/test/org/apache/sqoop/db/TestDriverManagerJdbcConnectionFactory.java > 244831672 > > src/test/org/apache/sqoop/db/decorator/TestKerberizedConnectionFactoryDecorator.java > d3e3fb23e > src/test/org/apache/sqoop/hbase/HBaseKerberizedConnectivityTest.java > 3bfb39178 > src/test/org/apache/sqoop/hbase/TestHBasePutProcessor.java e78a535f4 > src/test/org/apache/sqoop/hcat/TestHCatalogBasic.java ba05cabbb > > src/test/org/apache/sqoop/hive/HiveServer2ConnectionFactoryInitializerTest.java > 4d2cb2f88 > src/test/org/apache/sqoop/hive/TestHiveClientFactory.java a3c2dc939 > src/test/org/apache/sqoop/hive/TestHiveMiniCluster.java 419f888c0 > src/test/org/apache/sqoop/hive/TestHiveServer2Client.java 02617295e > src/test/org/apache/sqoop/hive/TestHiveServer2ParquetImport.java b55179a4f > src/test/org/apache/sqoop/hive/TestHiveServer2TextImport.java 410724f37 > src/test/org/apache/sqoop/hive/TestHiveTypesForAvroTypeMapping.java > 276e9eaa4 > src/test/org/apache/sqoop/hive/TestTableDefWriter.java 626ad22f6 > src/test/org/apache/sqoop/hive/TestTableDefWriterForExternalTable.java > f1768ee76 > src/test/org/apache/sqoop/io/TestCodecMap.java e71921823 > src/test/org/apache/sqoop/io/TestLobFile.java 2bc95f283 > src/test/org/apache/sqoop/io/TestNamedFifo.java a93784e08 > src/test/org/apache/sqoop/io/TestSplittableBufferedWriter.java c59aa26ad > src/test/org/apache/sqoop/lib/TestBlobRef.java b271d3c7b > src/test/org/apache/sqoop/lib/TestBooleanParser.java 914ab37e4 > src/test/org/apache/sqoop/lib/TestClobRef.java f94d1a8af > src/test/org/apache/sqoop/lib/TestFieldFormatter.java 9ac55e703 > src/test/org/apache/sqoop/lib/TestLargeObjectLoader.java 1e07d7174 >
Review Request 68569: HiveMiniCluster does not restore hive-site.xml location
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68569/ --- Review request for Sqoop. Bugs: SQOOP-3375 https://issues.apache.org/jira/browse/SQOOP-3375 Repository: sqoop-trunk Description --- HiveMiniCluster sets the hive-site.xml location using org.apache.hadoop.hive.conf.HiveConf#setHiveSiteLocation static method during startup but it does not restore the original location during shutdown. This makes HCatalogImportTest and HCatalogExportTest fail if they are ran in the same JVM after any test using HiveMiniCluster. Diffs - src/test/org/apache/sqoop/hive/minicluster/HiveMiniCluster.java 19bb7605c Diff: https://reviews.apache.org/r/68569/diff/1/ Testing --- Executed unit and third party tests. Thanks, Szabolcs Vasas
[jira] [Updated] (SQOOP-3368) Add fail-fast scenarios to S3 incremental import use cases without --temporary-rootdir option
[
https://issues.apache.org/jira/browse/SQOOP-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boglarka Egyed updated SQOOP-3368:
--
Attachment: SQOOP-3368.patch
> Add fail-fast scenarios to S3 incremental import use cases without
> --temporary-rootdir option
> -
>
> Key: SQOOP-3368
> URL: https://issues.apache.org/jira/browse/SQOOP-3368
> Project: Sqoop
> Issue Type: Sub-task
>Affects Versions: 1.4.7
>Reporter: Boglarka Egyed
>Assignee: Boglarka Egyed
>Priority: Major
> Attachments: SQOOP-3368.patch, SQOOP-3368.patch, SQOOP-3368.patch
>
>
> The current implementation of Sqoop handles HDFS as a default filesystem,
> i.e. it creates temporary directories on HDFS in case of incremental append
> or merge imports. To make these incremental import use cases work with S3 the
> user needs to set the {{--temporary-rootdir}} to an S3 location properly.
> There should be fail-fast scenarios without the {{--temporary-rootdir}}
> option.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SQOOP-3375) HiveMiniCluster does not restore hive-site.xml location
Szabolcs Vasas created SQOOP-3375: - Summary: HiveMiniCluster does not restore hive-site.xml location Key: SQOOP-3375 URL: https://issues.apache.org/jira/browse/SQOOP-3375 Project: Sqoop Issue Type: Sub-task Reporter: Szabolcs Vasas HiveMiniCluster sets the hive-site.xml location using org.apache.hadoop.hive.conf.HiveConf#setHiveSiteLocation static method during startup but it does not restore the original location during shutdown. This makes HCatalogImportTest and HCatalogExportTest fail if they are ran in the same JVM after any test using HiveMiniCluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SQOOP-3375) HiveMiniCluster does not restore hive-site.xml location
[ https://issues.apache.org/jira/browse/SQOOP-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szabolcs Vasas reassigned SQOOP-3375: - Assignee: Szabolcs Vasas > HiveMiniCluster does not restore hive-site.xml location > --- > > Key: SQOOP-3375 > URL: https://issues.apache.org/jira/browse/SQOOP-3375 > Project: Sqoop > Issue Type: Sub-task >Reporter: Szabolcs Vasas >Assignee: Szabolcs Vasas >Priority: Major > > HiveMiniCluster sets the hive-site.xml location using > org.apache.hadoop.hive.conf.HiveConf#setHiveSiteLocation static method during > startup but it does not restore the original location during shutdown. > This makes HCatalogImportTest and HCatalogExportTest fail if they are ran in > the same JVM after any test using HiveMiniCluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68536: SQOOP-3368: Add fail-fast scenarios to S3 incremental import use cases without --temporary-rootdir option
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68536/#review208123 --- Ship it! Hi Bogi, Thanks for improving the patch, I have ran the tests, everything looks good, let's ship it! - Szabolcs Vasas On Aug. 30, 2018, 9:59 a.m., Boglarka Egyed wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68536/ > --- > > (Updated Aug. 30, 2018, 9:59 a.m.) > > > Review request for Sqoop, daniel voros, Fero Szabo, Nguyen Truong, and > Szabolcs Vasas. > > > Bugs: SQOOP-3368 > https://issues.apache.org/jira/browse/SQOOP-3368 > > > Repository: sqoop-trunk > > > Description > --- > > The current implementation of Sqoop handles HDFS as a default filesystem, > i.e. it creates temporary directories on HDFS in case of incremental append > or merge imports. To make these incremental import use cases work with S3 the > user needs to set the --temporary-rootdir to an S3 location properly. > > > Diffs > - > > src/java/org/apache/sqoop/tool/ImportTool.java > 139733732d2a28d171568b9118c98a47a3d2fc50 > > src/test/org/apache/sqoop/tool/TestS3IncrementalImportOptionValidations.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/68536/diff/3/ > > > Testing > --- > > ant clean test > ./gradlew test -Ds3.bucket.url= > -Ds3.generator.command= > > > Thanks, > > Boglarka Egyed > >
Re: Review Request 68536: SQOOP-3368: Add fail-fast scenarios to S3 incremental import use cases without --temporary-rootdir option
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68536/ --- (Updated Aug. 30, 2018, 9:59 a.m.) Review request for Sqoop, daniel voros, Fero Szabo, Nguyen Truong, and Szabolcs Vasas. Changes --- Changed to startsWith() usage, looking for s3a uri scheme intead of "s3" only Bugs: SQOOP-3368 https://issues.apache.org/jira/browse/SQOOP-3368 Repository: sqoop-trunk Description --- The current implementation of Sqoop handles HDFS as a default filesystem, i.e. it creates temporary directories on HDFS in case of incremental append or merge imports. To make these incremental import use cases work with S3 the user needs to set the --temporary-rootdir to an S3 location properly. Diffs (updated) - src/java/org/apache/sqoop/tool/ImportTool.java 139733732d2a28d171568b9118c98a47a3d2fc50 src/test/org/apache/sqoop/tool/TestS3IncrementalImportOptionValidations.java PRE-CREATION Diff: https://reviews.apache.org/r/68536/diff/3/ Changes: https://reviews.apache.org/r/68536/diff/2-3/ Testing --- ant clean test ./gradlew test -Ds3.bucket.url= -Ds3.generator.command= Thanks, Boglarka Egyed
