[jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: --- Attachment: SQOOP-3052.patch > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > Attachments: SQOOP-3052.patch > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: --- Attachment: (was: SQOOP-3052.patch) > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: --- Attachment: SQOOP-3052.patch > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > Attachments: SQOOP-3052.patch > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: --- Attachment: (was: SQOOP-3052.patch) > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: --- Attachment: (was: SQOOP-3052.patch) > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404790#comment-16404790 ] Anna Szonyi commented on SQOOP-3052: Hi [~maugli], It seems I've missed your comment - apologies! The patches I attached were in a mostly complete state, I attached it as I got some requests around trying it out, but there were some files missing (script templates, etc.) and some further polishing to be done. I'll attach the finished version. Best, Anna > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > Attachments: SQOOP-3052.patch, SQOOP-3052.patch > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: --- Attachment: SQOOP-3052.patch > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > Attachments: SQOOP-3052.patch, SQOOP-3052.patch > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3052: -- Assignee: Anna Szonyi (was: Anna Szonyi) > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > Attachments: SQOOP-3052.patch > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: --- Attachment: SQOOP-3052.patch > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Major > Fix For: 1.5.0 > > Attachments: SQOOP-3052.patch > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SQOOP-3199) Sqoop 1.4.7 release preparation
[ https://issues.apache.org/jira/browse/SQOOP-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161130#comment-16161130 ] Anna Szonyi commented on SQOOP-3199: Hi [~maugli], I know you've been very busy lately, so the delays are of course understandable with the release. Do you think you will be able to close off the release by the end of September, if not then we would be happy to take the shepherding of it over. Also, we would be happy to help with anything else (Bogi and Szabi ran the 3rd party tests), if needed. There have been a few questions about the content as well, I will direct them to this umbrella jira. Thanks, Anna > Sqoop 1.4.7 release preparation > --- > > Key: SQOOP-3199 > URL: https://issues.apache.org/jira/browse/SQOOP-3199 > Project: Sqoop > Issue Type: Task >Reporter: Attila Szabo >Assignee: Attila Szabo > Fix For: no-release > > Attachments: text.html > > > Umbrella jira for 1.4.6 release. > For reference, the release wikis are: > https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release > https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release+Sqoop2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3196) Modify MySQLAuthTest to use configurable test database parameters
[ https://issues.apache.org/jira/browse/SQOOP-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143588#comment-16143588 ] Anna Szonyi commented on SQOOP-3196: Hi [~vasas], Thanks for your contribution! Please feel free to resolve the jira and the review request. Thanks, Anna > Modify MySQLAuthTest to use configurable test database parameters > -- > > Key: SQOOP-3196 > URL: https://issues.apache.org/jira/browse/SQOOP-3196 > Project: Sqoop > Issue Type: Test >Reporter: Szabolcs Vasas >Assignee: Szabolcs Vasas > Attachments: SQOOP-3196.patch, SQOOP-3196.patch, SQOOP-3196.patch > > > Most of the MySQL third party test cases use MySQLTestUtils to get the test > database parameters because these parameters can be configured using system > properties. > One exception is MySQLAuthTest which uses a predefined database name, > username and password which cannot be configured. > The goal of this JIRA is to change MySQLAuthTest to use MySQLTestUtils since > it would make setting up a new test database easier and make the MySQL third > party test suite more consistent. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3139) sqoop tries to re execute select query during import in case of a connection reset error and this is causing lots of duplicate records from source
[ https://issues.apache.org/jira/browse/SQOOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136985#comment-16136985 ] Anna Szonyi commented on SQOOP-3139: Hi [~Swank], Thanks for the contribution, and congrats on your first commit! Please resolve the jira and set the review to "Submitted". Thanks, Anna > sqoop tries to re execute select query during import in case of a connection > reset error and this is causing lots of duplicate records from source > -- > > Key: SQOOP-3139 > URL: https://issues.apache.org/jira/browse/SQOOP-3139 > Project: Sqoop > Issue Type: Bug >Affects Versions: 1.4.6 > Environment: IBM Hadoop distribution: 4.2.0 > version: 1.4.6_IBM_27 > Sqoop 1.4.6_IBM_27 >Reporter: hemanth meka >Assignee: Zoltán Tóth > Fix For: 1.5.0 > > Attachments: SQOOP-3139-3.patch, SQOOP-3139.patch > > > We cannot reproduce this issue as it depends on network. Here is a edited log > content for understanding the issue. > Log start > . > . > 2017-02-22 07:35:37,638 INFO [main] > org.apache.sqoop.mapreduce.sqlserver.SqlServerRecordReader: Using query: > select sequence_number, analytical_bundle_masked where ( Sequence_Number >= > 8571429 ) AND ( Sequence_Number <= 1000 ) > 2017-02-22 07:35:37,662 INFO [main] > org.apache.sqoop.mapreduce.db.DBRecordReader: Executing query: select > sequence_number, analytical_bundle_masked where ( Sequence_Number >= 8571429 > ) AND ( Sequence_Number <= 1000 ) > 2017-02-22 07:39:00,533 ERROR [main] > org.apache.sqoop.mapreduce.db.DBRecordReader: Top level exception: > com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset > at > com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2399) > at > com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2383) > at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1884) > at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:6685) > at com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:6595) > at > com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:6571) > at com.microsoft.sqlserver.jdbc.TDSReader.readBytes(IOBuffer.java:6864) > at > com.microsoft.sqlserver.jdbc.TDSReader.readWrappedBytes(IOBuffer.java:6886) > at > com.microsoft.sqlserver.jdbc.TDSReader.readUnsignedShort(IOBuffer.java:6801) > at > com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValuePrep(dtv.java:3570) > at com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValue(dtv.java:3936) > at com.microsoft.sqlserver.jdbc.DTV.getValue(dtv.java:226) > at com.microsoft.sqlserver.jdbc.Column.getValue(Column.java:144) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2099) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2084) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getString(SQLServerResultSet.java:2427) > at > org.apache.sqoop.lib.JdbcWritableBridge.readString(JdbcWritableBridge.java:71) > at > com.cloudera.sqoop.lib.JdbcWritableBridge.readString(JdbcWritableBridge.java:61) > at QueryResult.readFields0(QueryResult.java:10706) > at QueryResult.readFields(QueryResult.java:10415) > at > org.apache.sqoop.mapreduce.db.DBRecordReader.nextKeyValue(DBRecordReader.java:244) > at > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader.nextKeyValue(SQLServerDBRecordReader.java:148) > at > org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:556) > 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:145) > at > org.apache.sqoop.mapreduce.AutoProgressMapper.run(AutoProgressMapper.java:64) > at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341) > at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164) > 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:1657) > at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158) > 2017-02-22 07:39:00,552 WARN [main] > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader: Trying to recover from > DB read failure: > j
[jira] [Commented] (SQOOP-2411) Sqoop using '--direct' option fails with mysqldump exit code 2 and 3
[ https://issues.apache.org/jira/browse/SQOOP-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125598#comment-16125598 ] Anna Szonyi commented on SQOOP-2411: Hi [~sanysand...@gmail.com], Thanks for following up on this jira! In general we should only close these types of jiras if we know that we can't solve the issue from the Sqoop side/it's an expected failure/not a problem. However it might be a question around the cause of the exception: is the logging sufficient for the end user to tell what the root cause was, etc. Also it's a question of whether increasing 'net-write-timeout' or 'net-read-timeout' should solve these and if it's just a question of increasing it further (to how much) or if we're not passing it correctly (it's a bug on our end) or it doesn't have the desired effect (maybe a doc update). In general if you could reproduce the issue, and think it's solvable, this could be an improvement to potentially improve logging or solve the time out issues/check whether the net-read-timeout increasing helps (or a doc jira about usage). Thanks, Anna > Sqoop using '--direct' option fails with mysqldump exit code 2 and 3 > > > Key: SQOOP-2411 > URL: https://issues.apache.org/jira/browse/SQOOP-2411 > Project: Sqoop > Issue Type: Bug > Components: connectors/mysql >Affects Versions: 1.4.6 > Environment: Amazon EMR >Reporter: Karthick H >Assignee: Sandish Kumar HN >Priority: Critical > > I am running Sqoop in AWS EMR. I am trying to copy a table ~10 GB from MySQL > into HDFS. > I get the following exception > 15/07/06 12:19:07 INFO mapreduce.Job: Task Id : > attempt_1435664372091_0048_m_00_2, Status : FAILED > Error: java.io.IOException: mysqldump terminated with status 3 > at org.apache.sqoop.mapreduce.MySQLDumpMapper.map(MySQLDumpMapper.java:485) > at org.apache.sqoop.mapreduce.MySQLDumpMapper.map(MySQLDumpMapper.java:49) > at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:152) > at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:773) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341) > at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:175) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548) > at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:170) > 15/07/06 12:19:07 INFO mapreduce.Job: Task Id : > attempt_1435664372091_0048_m_05_2, Status : FAILED > Error: java.io.IOException: mysqldump terminated with status 2 > at org.apache.sqoop.mapreduce.MySQLDumpMapper.map(MySQLDumpMapper.java:485) > at org.apache.sqoop.mapreduce.MySQLDumpMapper.map(MySQLDumpMapper.java:49) > at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:152) > at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:773) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341) > at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:175) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548) > at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:170) > 15/07/06 12:19:08 INFO mapreduce.Job: map 0% reduce 0% > 15/07/06 12:19:20 INFO mapreduce.Job: map 25% reduce 0% > 15/07/06 12:19:22 INFO mapreduce.Job: map 38% reduce 0% > 15/07/06 12:19:23 INFO mapreduce.Job: map 50% reduce 0% > 15/07/06 12:19:24 INFO mapreduce.Job: map 75% reduce 0% > 15/07/06 12:19:25 INFO mapreduce.Job: map 100% reduce 0% > 15/07/06 12:23:11 INFO mapreduce.Job: Job job_1435664372091_0048 failed with > state FAILED due to: Task failed task_1435664372091_0048_m_00 > Job failed as tasks failed. failedMaps:1 failedReduces:0 > 15/07/06 12:23:11 INFO mapreduce.Job: Counters: 8 > Job Counters > Failed map tasks=28 > Launched map tasks=28 > Other local map tasks=28 > Total time spent by all maps in occupied slots (ms)=34760760 > Total time spent by all reduces in occupied slots (ms)=0 > Total time spent by all map tasks (ms)=5793460 > Total vcore-seconds taken by all map tasks=5793460 > Total megabyte-seconds taken by all map tasks=8342582400 > 15/07/06 12:23:11 WARN mapreduce.Counters: Group FileSystemCounters is > deprecated. Use org.apache.hadoop.mapreduce.FileSystemCounter instead > 15/07/06 12:23:11 INFO mapreduce.ImportJobBase: Transferred 0 bytes in > 829.8697 seconds (0 bytes/sec) > 15/07/06 12:23:11 WARN mapreduce.Counters: Group > org.apache.hadoop.mapred.Task$Counter is deprecated. Use > org.apache.hadoop.mapreduce.T
[jira] [Commented] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files
[ https://issues.apache.org/jira/browse/SQOOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119600#comment-16119600 ] Anna Szonyi commented on SQOOP-2907: Hi [~yuan_zac], Thanks for the original patch and the green light! :) [~sanysand...@gmail.com], Thank you for the great description of the contribution process! The only minor side note is the naming convention we have: it's SQOOP-(JIRANr)-(patchrevision).patch (meaning that if you have changed the patch 3 times due to a review it would be SQOOP-2907-3.patch). Please go ahead and submit the rebased patch for review! Thanks, Anna > Export parquet files to RDBMS: don't require .metadata for parquet files > > > Key: SQOOP-2907 > URL: https://issues.apache.org/jira/browse/SQOOP-2907 > Project: Sqoop > Issue Type: Improvement > Components: metastore >Affects Versions: 1.4.6 > Environment: sqoop 1.4.6 > export parquet files to Oracle >Reporter: Ruslan Dautkhanov >Assignee: Sandish Kumar HN > Attachments: SQOOP-2907.patch, SQOOP-2907.patch1 > > > Kite currently requires .metadata. > Parquet files have their own metadata stored along data files. > It would be great for Export operation on parquet files to RDBMS not to > require .metadata. > We have most of the files created by Spark and Hive, and they don't create > .metadata, it only Kite that does. > It makes sqoop export of parquet files usability very limited. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files
[ https://issues.apache.org/jira/browse/SQOOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118505#comment-16118505 ] Anna Szonyi edited comment on SQOOP-2907 at 8/8/17 3:53 PM: Hi [~sanysand...@gmail.com], Thanks for picking this up again! Please make sure that it applies to the current trunk (or if needed please rebase on it), also we should ping [~yuan_zac] and [~514793...@qq.com]] in case the original author wants to reclaim their patch. If not (or we receive no reply), then please submit it for review! Thanks, Anna was (Author: anna.szonyi): Hi [~sanysand...@gmail.com], Thanks for picking this up again! Please make sure that it applies to the current trunk (or if needed please rebase on it), also we should ping [~yuan_zac] and [~chenkai.dr] in case the original author wants to reclaim their patch. If not (or we receive no reply), then please submit it for review! Thanks, Anna > Export parquet files to RDBMS: don't require .metadata for parquet files > > > Key: SQOOP-2907 > URL: https://issues.apache.org/jira/browse/SQOOP-2907 > Project: Sqoop > Issue Type: Improvement > Components: metastore >Affects Versions: 1.4.6 > Environment: sqoop 1.4.6 > export parquet files to Oracle >Reporter: Ruslan Dautkhanov >Assignee: Sandish Kumar HN > Attachments: SQOOP-2907.patch, SQOOP-2907.patch1 > > > Kite currently requires .metadata. > Parquet files have their own metadata stored along data files. > It would be great for Export operation on parquet files to RDBMS not to > require .metadata. > We have most of the files created by Spark and Hive, and they don't create > .metadata, it only Kite that does. > It makes sqoop export of parquet files usability very limited. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files
[ https://issues.apache.org/jira/browse/SQOOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118505#comment-16118505 ] Anna Szonyi edited comment on SQOOP-2907 at 8/8/17 3:52 PM: Hi [~sanysand...@gmail.com], Thanks for picking this up again! Please make sure that it applies to the current trunk (or if needed please rebase on it), also we should ping [~yuan_zac] and [~chenkai.dr] in case the original author wants to reclaim their patch. If not (or we receive no reply), then please submit it for review! Thanks, Anna was (Author: anna.szonyi): Hi [~sanysand...@gmail.com], Thanks for picking this up again! Please make sure that it applies to the current trunk (or if needed please rebase on it), also we should ping [~yuan_zac] in case the original author wants to reclaim their patch. If not (or we receive no reply), then please submit it for review! Thanks, Anna > Export parquet files to RDBMS: don't require .metadata for parquet files > > > Key: SQOOP-2907 > URL: https://issues.apache.org/jira/browse/SQOOP-2907 > Project: Sqoop > Issue Type: Improvement > Components: metastore >Affects Versions: 1.4.6 > Environment: sqoop 1.4.6 > export parquet files to Oracle >Reporter: Ruslan Dautkhanov >Assignee: Sandish Kumar HN > Attachments: SQOOP-2907.patch, SQOOP-2907.patch1 > > > Kite currently requires .metadata. > Parquet files have their own metadata stored along data files. > It would be great for Export operation on parquet files to RDBMS not to > require .metadata. > We have most of the files created by Spark and Hive, and they don't create > .metadata, it only Kite that does. > It makes sqoop export of parquet files usability very limited. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files
[ https://issues.apache.org/jira/browse/SQOOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118505#comment-16118505 ] Anna Szonyi commented on SQOOP-2907: Hi [~sanysand...@gmail.com], Thanks for picking this up again! Please make sure that it applies to the current trunk (or if needed please rebase on it), also we should ping [~yuan_zac] in case the original author wants to reclaim their patch. If not (or we receive no reply), then please submit it for review! Thanks, Anna > Export parquet files to RDBMS: don't require .metadata for parquet files > > > Key: SQOOP-2907 > URL: https://issues.apache.org/jira/browse/SQOOP-2907 > Project: Sqoop > Issue Type: Improvement > Components: metastore >Affects Versions: 1.4.6 > Environment: sqoop 1.4.6 > export parquet files to Oracle >Reporter: Ruslan Dautkhanov >Assignee: Sandish Kumar HN > Attachments: SQOOP-2907.patch, SQOOP-2907.patch1 > > > Kite currently requires .metadata. > Parquet files have their own metadata stored along data files. > It would be great for Export operation on parquet files to RDBMS not to > require .metadata. > We have most of the files created by Spark and Hive, and they don't create > .metadata, it only Kite that does. > It makes sqoop export of parquet files usability very limited. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3149) Sqoop incremental import - NULL column updates are not pulled into HBase table
[ https://issues.apache.org/jira/browse/SQOOP-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112700#comment-16112700 ] Anna Szonyi commented on SQOOP-3149: Hi [~jilani], Thank you for your contribution and an extra thank you for being so patient throughout the entire process! Thanks, Anna > Sqoop incremental import - NULL column updates are not pulled into HBase > table > --- > > Key: SQOOP-3149 > URL: https://issues.apache.org/jira/browse/SQOOP-3149 > Project: Sqoop > Issue Type: Bug > Components: connectors/generic, hbase-integration >Affects Versions: 1.4.6 >Reporter: Jilani Shaik > Attachments: hbase_delete_support_in_incremental_import > > > Sqoop incremental import data from any database to HBase, if source table's > column from a row is updated to NULL, then target HBase table still showing > the previous value for that column. > So if you do a scan on the table for that row, HBase shows the previous > values of the column. > Expected Result: Sqoop incremental import, If NULL columns are there in > source, then HBase need not store that and if it already exists need to > delete that column for a given row. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SQOOP-3178) SQOOP PARQUET INCREMENTAL MERGE
[ https://issues.apache.org/jira/browse/SQOOP-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096771#comment-16096771 ] Anna Szonyi edited comment on SQOOP-3178 at 7/21/17 8:02 PM: - Hi [~sanysand...@gmail.com], Thank you for your contribution, looking forward to future patches :)! Please set the jira to resolved and the review request to submitted. Thanks, Anna was (Author: anna.szonyi): Hi [~sanysand...@gmail.com], Thank you for your contribution, looking forward to future patches :)! Thanks, Anna > SQOOP PARQUET INCREMENTAL MERGE > > > Key: SQOOP-3178 > URL: https://issues.apache.org/jira/browse/SQOOP-3178 > Project: Sqoop > Issue Type: Improvement > Components: build, codegen, connectors > Environment: None >Reporter: Sandish Kumar HN >Assignee: Sandish Kumar HN >Priority: Blocker > Labels: features, newbie, sqoop > > Currently, sqoop-1 only supports merging of two Parquet format data sets but > it doesn't support to do incremental merge, so I have written a Sqoop > Incremental Merge MR for Parquet File Format and I have tested with million > records of data with N number of iterations. > blocked by issue https://issues.apache.org/jira/browse/SQOOP-3192 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SQOOP-3178) SQOOP PARQUET INCREMENTAL MERGE
[ https://issues.apache.org/jira/browse/SQOOP-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096771#comment-16096771 ] Anna Szonyi edited comment on SQOOP-3178 at 7/21/17 8:01 PM: - Hi [~sanysand...@gmail.com], Thank you for your contribution, looking forward to future patches :)! Thanks, Anna was (Author: anna.szonyi): Hi Sandish, Thank you for your contribution, looking forward to future patches :)! Thanks, Anna > SQOOP PARQUET INCREMENTAL MERGE > > > Key: SQOOP-3178 > URL: https://issues.apache.org/jira/browse/SQOOP-3178 > Project: Sqoop > Issue Type: Improvement > Components: build, codegen, connectors > Environment: None >Reporter: Sandish Kumar HN >Assignee: Sandish Kumar HN >Priority: Blocker > Labels: features, newbie, sqoop > > Currently, sqoop-1 only supports merging of two Parquet format data sets but > it doesn't support to do incremental merge, so I have written a Sqoop > Incremental Merge MR for Parquet File Format and I have tested with million > records of data with N number of iterations. > blocked by issue https://issues.apache.org/jira/browse/SQOOP-3192 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3178) SQOOP PARQUET INCREMENTAL MERGE
[ https://issues.apache.org/jira/browse/SQOOP-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096771#comment-16096771 ] Anna Szonyi commented on SQOOP-3178: Hi Sandish, Thank you for your contribution, looking forward to future patches :)! Thanks, Anna > SQOOP PARQUET INCREMENTAL MERGE > > > Key: SQOOP-3178 > URL: https://issues.apache.org/jira/browse/SQOOP-3178 > Project: Sqoop > Issue Type: Improvement > Components: build, codegen, connectors > Environment: None >Reporter: Sandish Kumar HN >Assignee: Sandish Kumar HN >Priority: Blocker > Labels: features, newbie, sqoop > > Currently, sqoop-1 only supports merging of two Parquet format data sets but > it doesn't support to do incremental merge, so I have written a Sqoop > Incremental Merge MR for Parquet File Format and I have tested with million > records of data with N number of iterations. > blocked by issue https://issues.apache.org/jira/browse/SQOOP-3192 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3197) Database credentials cannot be configured in PostgreSQL third party tests
[ https://issues.apache.org/jira/browse/SQOOP-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076627#comment-16076627 ] Anna Szonyi commented on SQOOP-3197: Hey Szabolcs, Thanks for your continued improvements/standardization to the tests we are running! Thanks, Anna > Database credentials cannot be configured in PostgreSQL third party tests > - > > Key: SQOOP-3197 > URL: https://issues.apache.org/jira/browse/SQOOP-3197 > Project: Sqoop > Issue Type: Test >Reporter: Szabolcs Vasas >Assignee: Szabolcs Vasas > Attachments: SQOOP-3197.patch > > > PostgreSQL third party tests look like they support configurable database > parameters (e.g. they load the database user, name and password from a system > property) but the property names in the test cases do not match the property > names in the build.xml and because of that these parameters cannot be > specified from the command line. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3206) Make sqoop fail if user uses --direct connector and tries to encode a null value when using a MySQL database
[ https://issues.apache.org/jira/browse/SQOOP-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076455#comment-16076455 ] Anna Szonyi commented on SQOOP-3206: Hey Zach, Thank you for your great contribution! :) Thanks, Anna > Make sqoop fail if user uses --direct connector and tries to encode a null > value when using a MySQL database > > > Key: SQOOP-3206 > URL: https://issues.apache.org/jira/browse/SQOOP-3206 > Project: Sqoop > Issue Type: Improvement >Reporter: Zach Berkowitz >Assignee: Zach Berkowitz >Priority: Minor > Attachments: sqoop-3206.patch > > > The MySQL tools, mysqldump and mysqlimport, do not support custom null value > options, so sqoop should fail fast when --direct mode and > --input-null-string, --input-null-non-string, --null-string, or > --null-non-string are used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3194) HCatalogExportTest fails because of column escaping problems
[ https://issues.apache.org/jira/browse/SQOOP-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055514#comment-16055514 ] Anna Szonyi commented on SQOOP-3194: Thanks for the fix Szabolcs! > HCatalogExportTest fails because of column escaping problems > > > Key: SQOOP-3194 > URL: https://issues.apache.org/jira/browse/SQOOP-3194 > Project: Sqoop > Issue Type: Test >Reporter: Szabolcs Vasas >Assignee: Szabolcs Vasas > Attachments: SQOOP-3194.patch > > > It seems there were some changes in the escaping logic in the test framework > which broke HCatalogExportTest. Since it is a third party test ant clean test > did not spot the problem earlier. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3198) Fix DirectMySQLExportTest and OracleExportTest
[ https://issues.apache.org/jira/browse/SQOOP-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055493#comment-16055493 ] Anna Szonyi commented on SQOOP-3198: Hey Szabi, Thanks for catching and fixing this! Thanks, Anna > Fix DirectMySQLExportTest and OracleExportTest > -- > > Key: SQOOP-3198 > URL: https://issues.apache.org/jira/browse/SQOOP-3198 > Project: Sqoop > Issue Type: Improvement >Affects Versions: 1.4.6 >Reporter: Szabolcs Vasas >Assignee: Szabolcs Vasas > Labels: newbie > Attachments: SQOOP-3198.patch > > > DirectMySQLExportTest and OracleExportTest extend TestExport class and some > of the new test cases added in SQOOP-3158 fail in these tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SQOOP-3158) Columns added to Mysql after initial sqoop import, export back to table with same schema fails
[ https://issues.apache.org/jira/browse/SQOOP-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044116#comment-16044116 ] Anna Szonyi commented on SQOOP-3158: Hi Eric, Another great contribution, thank you for your continued work to better Sqoop! Thanks, Anna > Columns added to Mysql after initial sqoop import, export back to table with > same schema fails > --- > > Key: SQOOP-3158 > URL: https://issues.apache.org/jira/browse/SQOOP-3158 > Project: Sqoop > Issue Type: Improvement >Affects Versions: 1.4.6 >Reporter: viru reddy >Assignee: Eric Lin > Labels: newbie > Attachments: SQOOP-3158.2.patch, SQOOP-3158.3.patch, > SQOOP-3158.4.patch, SQOOP-3158.patch > > > I have table in MySQL with 2 columns until yesterday. The columns are id and > name. > 1,Raj > 2,Jack > I have imported this data into HDFS yesterday itself as a file. Today we > added a new column to the table in MySQL called salary. The table looks like > below. > 1,Raj > 2,Jack > 3,Jill,2000 > 4,Nick,3000 > Now I have done Incremental import on this table as a file. > Part-m-0 file contains > 1,Raj > 2,Jack > Part-m-1 file contains > 3,Jill,2000 > 4,Nick,3000 > Now I created a new table in MySQL with same schema as Original MySQL table > with columns id name and salary. > When I do sqoop export only last 2 rows are getting inserted to the new table > in MySQL and the sqoop export fails > How can I reflect all the rows to be inserted to the table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SQOOP-816) Scoop and support for external Hive tables
[ https://issues.apache.org/jira/browse/SQOOP-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012005#comment-16012005 ] Anna Szonyi commented on SQOOP-816: --- Hi [~chris.t...@gmail.com], Thank you for your contribution! Thanks, Anna > Scoop and support for external Hive tables > -- > > Key: SQOOP-816 > URL: https://issues.apache.org/jira/browse/SQOOP-816 > Project: Sqoop > Issue Type: Improvement > Components: hive-integration >Reporter: Santosh Achhra >Assignee: Chris Teoh >Priority: Minor > Labels: External, Hive,, Scoop,, Tables, newbie > > Sqoop is not supporting HIVE external tables at the moment. Any imports using > scoop creates a managed table, in real world scenario it is very important to > have EXTERNAL tables. As of now we have to execute ALTER statement to change > table properties to make the the table as external table which is not a big > deal but it would nice have an option in scoop to specify type of table which > is required -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SQOOP-3168) Sqoop Saved Job feature of overwriting job argument at execution time is not working in Sqoop1.4.6CDH 5.8.0
[ https://issues.apache.org/jira/browse/SQOOP-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960653#comment-15960653 ] Anna Szonyi commented on SQOOP-3168: Hi, Unfortunately this is a bug that was introduced with SQOOP-2779 and later fixed by SQOOP-2896. As for a workaround: there is none, besides patching it with the fix of SQOOP-2896, as for CDH 5.8.0, only creating new jobs or upgrading to 5.8.5+ would solve it, as that is where the fix was first backported. Apologies and Regards, Anna > Sqoop Saved Job feature of overwriting job argument at execution time is not > working in Sqoop1.4.6CDH 5.8.0 > --- > > Key: SQOOP-3168 > URL: https://issues.apache.org/jira/browse/SQOOP-3168 > Project: Sqoop > Issue Type: Bug >Reporter: Hemendra Yadav > > Hi, > I have created one sqoop saved job using below command :: > sqoop job --create -- import --connect --driver > com.mysql.jdbc.Driver --username --password --table > --target-dir location1 --fields-terminated-by , --escaped-by \\ -m 1 > > I need to put the data to different location so while execution i have > provided new location in below command:: > sqoop job --exec jobname1 -- --target-dir location_new > But it still picks up the target directory from the saved job i.e. location1. > I am currently using sqoop 1.4.6 CDH 5.8.0 version. When i have checked the > sqoop code it seems that in sqoop CDH 5.8.0 code for overwritting job > argument is removed from the method "private int execJob(SqoopOptions opts)" > in the class "org.apache.sqoop.tool.JobTool" due to issue > "https://issues.apache.org/jira/browse/SQOOP-2779";. > When i have executed the same command using sqoop 1.4.6 CDH 5.7.3 it is able > to overwrite the target directory and working as expected. > Can you please suggest any workaround how to import data to a different > target directory while executing sqoop saved job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SQOOP-3159) Sqoop (export + --table) with Oracle table_name having '$' fails with error (ORA-00942 or java.lang.NoClassDefFoundError)
[
https://issues.apache.org/jira/browse/SQOOP-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943364#comment-15943364
]
Anna Szonyi commented on SQOOP-3159:
Thank you for your contribution Szabolcs!
Thanks,
Anna
> Sqoop (export + --table) with Oracle table_name having '$' fails with error
> (ORA-00942 or java.lang.NoClassDefFoundError)
> -
>
> Key: SQOOP-3159
> URL: https://issues.apache.org/jira/browse/SQOOP-3159
> Project: Sqoop
> Issue Type: Bug
>Reporter: Markus Kemper
>Assignee: Szabolcs Vasas
> Attachments: SQOOP-3159.patch
>
>
> Sqoop (export + --table) with Oracle table_name having '$' fails with error
> (ORA-00942 or java.lang.NoClassDefFoundError), see test case below.
> *Test Case*
> {noformat}
> #
> # STEP 01 - Create Data
> #
> export MYCONN=jdbc:oracle:thin:@oracle1.cloudera.com:1521/db11g;
> export MYUSER=sqoop
> export MYPSWD=cloudera
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "drop table t1"
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "create table t1 (c1 int, c2 date, c3 varchar(10))"
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "insert into t1 values (1, current_date, 'some data')"
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "select * from t1"
> Output:
> ---
> | C1 | C2 | C3 |
> ---
> | 1| 2017-03-21 13:30:02.0 | some data |
> ---
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "drop table t\$1"
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "create table t\$1 (c1 int, c2 date, c3 varchar(10))"
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "insert into t\$1 values (1, current_date, 'some data')"
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "select * from t\$1"
> Output:
> ---
> | C1 | C2 | C3 |
> ---
> | 1| 2017-03-21 13:31:18.0 | some data |
> ---
> #
> # STEP 02 - Import and Export without '$' (baseline)
> #
> sqoop import --connect $MYCONN --username $MYUSER --password $MYPSWD --table
> "T1" --target-dir /user/root/t1 --delete-target-dir --num-mappers 1
> hdfs dfs -cat /user/root/t1/part*
> Output:
> 17/03/21 06:39:31 INFO mapreduce.ImportJobBase: Transferred 34 bytes in
> 21.6129 seconds (1.5731 bytes/sec)
> 17/03/21 06:39:31 INFO mapreduce.ImportJobBase: Retrieved 1 records.
> ~
> 1,2017-03-21 13:30:02.0,some data
> sqoop export --connect $MYCONN --username $MYUSER --password $MYPSWD --table
> T1 --export-dir /user/root/t1 --num-mappers 1
> sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query
> "select * from t1"
> Output:
> 17/03/21 06:46:07 INFO mapreduce.ExportJobBase: Transferred 163 bytes in
> 21.4938 seconds (7.5836 bytes/sec)
> 17/03/21 06:46:07 INFO mapreduce.ExportJobBase: Exported 1 records.
> ~
> ---
> | C1 | C2 | C3 |
> ---
> | 1| 2017-03-21 13:30:02.0 | some data |
> | 1| 2017-03-21 13:30:02.0 | some data |
> ---
> #
> # STEP 03 - Export with '$' (--table T$1)
> #
> sqoop export --connect $MYCONN --username $MYUSER --password $MYPSWD --table
> T$1 --export-dir /user/root/t1 --num-mappers 1
> Output:
> 17/03/21 06:49:28 INFO manager.SqlManager: Executing SQL statement: SELECT
> t.* FROM "T" t WHERE 1=0
> 17/03/21 06:49:28 ERROR manager.SqlManager: Error executing statement:
> java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
> #
> # STEP 04 - Export with '$' (--table T\$1)
> #
> sqoop export --connect $MYCONN --username $MYUSER --password $MYPSWD --table
> T\$1 --export-dir /user/root/t1 --num-mappers 1
> Output:
> 17/03/22 07:27:26 INFO manager.SqlManager: Executing SQL statement: SELECT
> t.* FROM "T$1" t WHERE 1=0
> 17/03/22 07:27:26 INFO orm.CompilationManager: HADOOP_MAPRED_HOME is
> /opt/cloudera/parcels/CDH/lib/hadoop-mapreduce
> 17/03/22 07:27:27 INFO mapreduce.ExportJobBase: Beginning export of T$1
>
> 2017-03-22 07:27:54,215 WAR
[jira] [Commented] (SQOOP-3143) Restore fail messages removed in SQOOP-3091
[ https://issues.apache.org/jira/browse/SQOOP-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928804#comment-15928804 ] Anna Szonyi commented on SQOOP-3143: Thanks for this contribution Bogi! /Anna > Restore fail messages removed in SQOOP-3091 > --- > > Key: SQOOP-3143 > URL: https://issues.apache.org/jira/browse/SQOOP-3143 > Project: Sqoop > Issue Type: Sub-task >Affects Versions: 1.4.6 >Reporter: Boglarka Egyed >Assignee: Boglarka Egyed >Priority: Minor > Attachments: SQOOP-3143.patch > > > Restore fail messages on excepted exceptions using > reportMissingExceptionWithMessage functionality added in JUnit 4.12 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SQOOP-3154) Sqoop2: Add Anna Szonyi to committer list in our pom file
[ https://issues.apache.org/jira/browse/SQOOP-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928527#comment-15928527 ] Anna Szonyi commented on SQOOP-3154: Thanks [~abrahamfine]! Everything is *perfect*! Thanks, /Anna > Sqoop2: Add Anna Szonyi to committer list in our pom file > - > > Key: SQOOP-3154 > URL: https://issues.apache.org/jira/browse/SQOOP-3154 > Project: Sqoop > Issue Type: Bug >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 1.99.8 > > Attachments: SQOOP-3154.patch > > > Now that [~szonyi] is committer we should update our committer list in the > root pom.xml file: > Also add [~abrahamfine] as PMC member. > https://github.com/apache/sqoop/blob/sqoop2/pom.xml#L903 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SQOOP-3146) Sqoop (import + --as-parquetfile) with Oracle (CLOB vs. BLOB) is inconsistent
Anna Szonyi created SQOOP-3146: -- Summary: Sqoop (import + --as-parquetfile) with Oracle (CLOB vs. BLOB) is inconsistent Key: SQOOP-3146 URL: https://issues.apache.org/jira/browse/SQOOP-3146 Project: Sqoop Issue Type: Bug Reporter: Anna Szonyi # Owner: Sqoopinators # Component: Sqoop1 # Purpose: Escalation Test Case # SFDC Case ID:127558 # SFDC EscalationID: CDH-50699 # File: SupportTest_Case_127558_JIRA_CDH-50699.txt # # Description # 1. Sqoop import + —as-parquetfile + CLOB Data Types (Gives Error) # 2. Sqoop import + —as-parquetfile + BLOB Data Types (Works Good) ## USE CASE [1] . Sqoop import + —as-parquetfile + CLOB Data Types (Gives Error) ## ### # STEP 01 - CREATE DATA ### sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query "create table t1_clob (c1 int,c2 clob)" sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query "insert into t1_clob values(1,'qwqewewqrerew121212121212’)” sqoop eval --connect $MYCONN --username $MYUSER --password $MYPSWD --query "select * from t1_clob" # OUTPUT # --- | C1 | C2 | --- | 1| qwqewewqrerew121212121212 | --- STEP 02 - IMPORT AS PARQUET FILE (Without —map-column-java) [REPRODUCING THE ERROR] sqoop import --connect $MYCONN --username $MYUSER --password $MYPSWD --as-parquetfile --table T1_CLOB --delete-target-dir --target-dir '/projects/t1_clob' -m 1 OUTPUT —— Please set $ACCUMULO_HOME to the root of your Accumulo installation. 17/02/21 10:07:08 INFO sqoop.Sqoop: Running Sqoop version: 1.4.6-cdh5.8.3 17/02/21 10:07:08 WARN tool.BaseSqoopTool: Setting your password on the command-line is insecure. Consider using -P instead. 17/02/21 10:07:08 INFO oracle.OraOopManagerFactory: Data Connector for Oracle and Hadoop is disabled. 17/02/21 10:07:08 INFO manager.SqlManager: Using default fetchSize of 1000 17/02/21 10:07:08 INFO tool.CodeGenTool: Beginning code generation 17/02/21 10:07:08 INFO tool.CodeGenTool: Will generate java class as codegen_T1_CLOB 17/02/21 10:07:09 INFO manager.OracleManager: Time zone has been set to GMT 17/02/21 10:07:09 INFO manager.SqlManager: Executing SQL statement: SELECT t.* FROM "T1_CLOB" t WHERE 1=0 17/02/21 10:07:09 INFO orm.CompilationManager: HADOOP_MAPRED_HOME is /opt/cloudera/parcels/CDH/lib/hadoop-mapreduce Note: /tmp/sqoop-root/compile/cbaf5013e6bc9dad7283090f9d761289/codegen_T1_CLOB.java uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. 17/02/21 10:07:11 INFO orm.CompilationManager: Writing jar file: /tmp/sqoop-root/compile/cbaf5013e6bc9dad7283090f9d761289/codegen_T1_CLOB.jar 17/02/21 10:07:13 INFO tool.ImportTool: Destination directory /projects/t1_clob is not present, hence not deleting. 17/02/21 10:07:13 INFO manager.OracleManager: Time zone has been set to GMT 17/02/21 10:07:13 INFO manager.OracleManager: Time zone has been set to GMT 17/02/21 10:07:13 INFO mapreduce.ImportJobBase: Beginning import of T1_CLOB 17/02/21 10:07:13 INFO Configuration.deprecation: mapred.jar is deprecated. Instead, use mapreduce.job.jar 17/02/21 10:07:13 INFO manager.OracleManager: Time zone has been set to GMT 17/02/21 10:07:13 INFO manager.OracleManager: Time zone has been set to GMT 17/02/21 10:07:13 INFO manager.SqlManager: Executing SQL statement: SELECT t.* FROM "T1_CLOB" t WHERE 1=0 17/02/21 10:07:13 INFO manager.SqlManager: Executing SQL statement: SELECT t.* FROM "T1_CLOB" t WHERE 1=0 17/02/21 10:07:13 ERROR tool.ImportTool: Imported Failed: Cannot convert SQL type 2005 # STEP 02.1 - IMPORT AS PARQUET FILE + —map-column-java (For CLOB data type) # sqoop import --connect $MYCONN --username $MYUSER --password $MYPSWD --as-parquet file --table T1_CLOB --map-column-java C2=String --delete-target-dir --target-dir '/projects/t1_clob' -m 1 OUTPUT ——— 17/02/21 10:09:50 INFO tool.ImportTool: Destination directory /projects/t1_clob is not present, hence not deleting. 17/02/21 10:09:50 INFO mapreduce.ImportJobBase: Beginning import of T1_CLOB 17/02/21 10:10:09 INFO mapreduce.Job: map 0% reduce 0% 17/02/21 10:10:34 INFO mapreduce.Job: map 100% reduce 0% 17/02/21 10:10:35 INFO map
[jira] [Assigned] (SQOOP-3145) Misc. test changes, so we don't need to fork with every test
[ https://issues.apache.org/jira/browse/SQOOP-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3145: -- Assignee: Anna Szonyi > Misc. test changes, so we don't need to fork with every test > > > Key: SQOOP-3145 > URL: https://issues.apache.org/jira/browse/SQOOP-3145 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi >Assignee: Anna Szonyi > > Currently we can only run tests with "fork with every" single test. We can > make a few changes for the tests to be able to run without needing to fork > every tests (table names can contain the testnames, queryname.jar can be > overwritten, etc.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SQOOP-3145) Misc. test changes, so we don't need to fork with every test
[ https://issues.apache.org/jira/browse/SQOOP-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3145: --- Description: Currently we can only run tests with "fork with every" single test. We can make a few changes for the tests to be able to run without needing to fork every tests (table names can contain the testnames, queryname.jar can be overwritten, etc.) > Misc. test changes, so we don't need to fork with every test > > > Key: SQOOP-3145 > URL: https://issues.apache.org/jira/browse/SQOOP-3145 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi > > Currently we can only run tests with "fork with every" single test. We can > make a few changes for the tests to be able to run without needing to fork > every tests (table names can contain the testnames, queryname.jar can be > overwritten, etc.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SQOOP-3145) Misc. test changes, so we don't need to fork with every test
Anna Szonyi created SQOOP-3145: -- Summary: Misc. test changes, so we don't need to fork with every test Key: SQOOP-3145 URL: https://issues.apache.org/jira/browse/SQOOP-3145 Project: Sqoop Issue Type: Improvement Reporter: Anna Szonyi -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SQOOP-3136) Sqoop should work well with not default file systems
[
https://issues.apache.org/jira/browse/SQOOP-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885723#comment-15885723
]
Anna Szonyi commented on SQOOP-3136:
Hey [~yalovyyi],
Understandable, most of the time so do I, unfortunately Sqoop still
supports/uses Java 7 - we are planning to propose a switch to java 8 in the
near future (that will have to be a community decision), in the mean time we're
stuck with 7. We have source and target enforcements in ant, though it is to
enforce the related syntax more than the compiler/compilation itself afair.
[~maugli] added a small patch to remove the offending method, so there is not
much else to do :).
Thanks again for the contribution!
Thanks,
Anna
> Sqoop should work well with not default file systems
>
>
> Key: SQOOP-3136
> URL: https://issues.apache.org/jira/browse/SQOOP-3136
> Project: Sqoop
> Issue Type: Improvement
> Components: connectors/hdfs
>Affects Versions: 1.4.5
>Reporter: Illya Yalovyy
>Assignee: Illya Yalovyy
> Attachments: SQOOP-3136.patch
>
>
> Currently Sqoop assumes default file system when it comes to IO operations.
> It makes it hard to use other FileSystem implementations as source or
> destination. Here is an example:
> {code}
> sqoop import --connect --table table1 --driver DRIVER> --username root --password --delete-target-dir --target-dir
> s3a://some-bucket/tmp/sqoop
> ...
> 17/02/15 19:16:59 ERROR tool.ImportTool: Imported Failed: Wrong FS:
> s3a://some-bucket/tmp/sqoop, expected: hdfs://:8020
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SQOOP-3136) Sqoop should work well with not default file systems
[
https://issues.apache.org/jira/browse/SQOOP-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882404#comment-15882404
]
Anna Szonyi commented on SQOOP-3136:
Hi [~yalovyyi] [~maugli],
Thanks for the patch, this is super useful! However I am/HUDSON is having
issues running the tests -
/src/test/org/apache/sqoop/util/TestFileSystemUtil.java:36: error: cannot find
symbol
conf.set("fs.my.impl", MyFileSystem.class.getTypeName());
As far as I know [this
method|https://docs.oracle.com/javase/8/docs/api/java/lang/Class.html#getTypeName--]
was introduced in Java 1.8 and currently Sqoop supports/is built with/for 1.7
which is causing the above issue.
Could you please look into this?
Thanks,
Anna
> Sqoop should work well with not default file systems
>
>
> Key: SQOOP-3136
> URL: https://issues.apache.org/jira/browse/SQOOP-3136
> Project: Sqoop
> Issue Type: Improvement
> Components: connectors/hdfs
>Affects Versions: 1.4.5
>Reporter: Illya Yalovyy
>Assignee: Illya Yalovyy
> Attachments: SQOOP-3136.patch
>
>
> Currently Sqoop assumes default file system when it comes to IO operations.
> It makes it hard to use other FileSystem implementations as source or
> destination. Here is an example:
> {code}
> sqoop import --connect --table table1 --driver DRIVER> --username root --password --delete-target-dir --target-dir
> s3a://some-bucket/tmp/sqoop
> ...
> 17/02/15 19:16:59 ERROR tool.ImportTool: Imported Failed: Wrong FS:
> s3a://some-bucket/tmp/sqoop, expected: hdfs://:8020
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SQOOP-3139) sqoop tries to re execute select query during import in case of a connection reset error and this is causing lots of duplicate records from source
[ https://issues.apache.org/jira/browse/SQOOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3139: --- Attachment: SQOOP-3139.patch > sqoop tries to re execute select query during import in case of a connection > reset error and this is causing lots of duplicate records from source > -- > > Key: SQOOP-3139 > URL: https://issues.apache.org/jira/browse/SQOOP-3139 > Project: Sqoop > Issue Type: Bug >Affects Versions: 1.4.6 > Environment: IBM Hadoop distribution: 4.2.0 > version: 1.4.6_IBM_27 > Sqoop 1.4.6_IBM_27 >Reporter: hemanth meka > Attachments: SQOOP-3139.patch > > > We cannot reproduce this issue as it depends on network. Here is a edited log > content for understanding the issue. > Log start > . > . > 2017-02-22 07:35:37,638 INFO [main] > org.apache.sqoop.mapreduce.sqlserver.SqlServerRecordReader: Using query: > select sequence_number, analytical_bundle_masked where ( Sequence_Number >= > 8571429 ) AND ( Sequence_Number <= 1000 ) > 2017-02-22 07:35:37,662 INFO [main] > org.apache.sqoop.mapreduce.db.DBRecordReader: Executing query: select > sequence_number, analytical_bundle_masked where ( Sequence_Number >= 8571429 > ) AND ( Sequence_Number <= 1000 ) > 2017-02-22 07:39:00,533 ERROR [main] > org.apache.sqoop.mapreduce.db.DBRecordReader: Top level exception: > com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset > at > com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2399) > at > com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2383) > at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1884) > at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:6685) > at com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:6595) > at > com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:6571) > at com.microsoft.sqlserver.jdbc.TDSReader.readBytes(IOBuffer.java:6864) > at > com.microsoft.sqlserver.jdbc.TDSReader.readWrappedBytes(IOBuffer.java:6886) > at > com.microsoft.sqlserver.jdbc.TDSReader.readUnsignedShort(IOBuffer.java:6801) > at > com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValuePrep(dtv.java:3570) > at com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValue(dtv.java:3936) > at com.microsoft.sqlserver.jdbc.DTV.getValue(dtv.java:226) > at com.microsoft.sqlserver.jdbc.Column.getValue(Column.java:144) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2099) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2084) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getString(SQLServerResultSet.java:2427) > at > org.apache.sqoop.lib.JdbcWritableBridge.readString(JdbcWritableBridge.java:71) > at > com.cloudera.sqoop.lib.JdbcWritableBridge.readString(JdbcWritableBridge.java:61) > at QueryResult.readFields0(QueryResult.java:10706) > at QueryResult.readFields(QueryResult.java:10415) > at > org.apache.sqoop.mapreduce.db.DBRecordReader.nextKeyValue(DBRecordReader.java:244) > at > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader.nextKeyValue(SQLServerDBRecordReader.java:148) > at > org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:556) > 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:145) > at > org.apache.sqoop.mapreduce.AutoProgressMapper.run(AutoProgressMapper.java:64) > at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341) > at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164) > 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:1657) > at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158) > 2017-02-22 07:39:00,552 WARN [main] > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader: Trying to recover from > DB read failure: > java.io.IOException: SQLException in nextKeyValue > at > org.apache.sqoop.mapreduce.db.DBRecordReader.nextKeyValue(DBRecordReader.java:277) > at > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader.nextKeyValue(SQLServerDBRecordReader.java:148) >
[jira] [Commented] (SQOOP-3139) sqoop tries to re execute select query during import in case of a connection reset error and this is causing lots of duplicate records from source
[ https://issues.apache.org/jira/browse/SQOOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880362#comment-15880362 ] Anna Szonyi commented on SQOOP-3139: Hi, This might be because of the mapper task re-tries the failed action 4 times by default. There was a fix for this (SQOOP-2055) for the export case. Something similar should probably also be done for the import. I've created a patch on top of SQOOP-3140 (note the patch also needs 3140 to be committed to be useable) for the import to set the mapred max attempt to one. I would like to propose this change to the community: that we set the same default of 1 attempt for export and import, with the possibility of overriding it as needed. In the mean time you can try overriding the mapreduce.map.maxattempts to 1 instead of the default 4. Best, /Anna > sqoop tries to re execute select query during import in case of a connection > reset error and this is causing lots of duplicate records from source > -- > > Key: SQOOP-3139 > URL: https://issues.apache.org/jira/browse/SQOOP-3139 > Project: Sqoop > Issue Type: Bug >Affects Versions: 1.4.6 > Environment: IBM Hadoop distribution: 4.2.0 > version: 1.4.6_IBM_27 > Sqoop 1.4.6_IBM_27 >Reporter: hemanth meka > > We cannot reproduce this issue as it depends on network. Here is a edited log > content for understanding the issue. > Log start > . > . > 2017-02-22 07:35:37,638 INFO [main] > org.apache.sqoop.mapreduce.sqlserver.SqlServerRecordReader: Using query: > select sequence_number, analytical_bundle_masked where ( Sequence_Number >= > 8571429 ) AND ( Sequence_Number <= 1000 ) > 2017-02-22 07:35:37,662 INFO [main] > org.apache.sqoop.mapreduce.db.DBRecordReader: Executing query: select > sequence_number, analytical_bundle_masked where ( Sequence_Number >= 8571429 > ) AND ( Sequence_Number <= 1000 ) > 2017-02-22 07:39:00,533 ERROR [main] > org.apache.sqoop.mapreduce.db.DBRecordReader: Top level exception: > com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset > at > com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2399) > at > com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2383) > at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1884) > at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:6685) > at com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:6595) > at > com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:6571) > at com.microsoft.sqlserver.jdbc.TDSReader.readBytes(IOBuffer.java:6864) > at > com.microsoft.sqlserver.jdbc.TDSReader.readWrappedBytes(IOBuffer.java:6886) > at > com.microsoft.sqlserver.jdbc.TDSReader.readUnsignedShort(IOBuffer.java:6801) > at > com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValuePrep(dtv.java:3570) > at com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValue(dtv.java:3936) > at com.microsoft.sqlserver.jdbc.DTV.getValue(dtv.java:226) > at com.microsoft.sqlserver.jdbc.Column.getValue(Column.java:144) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2099) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2084) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getString(SQLServerResultSet.java:2427) > at > org.apache.sqoop.lib.JdbcWritableBridge.readString(JdbcWritableBridge.java:71) > at > com.cloudera.sqoop.lib.JdbcWritableBridge.readString(JdbcWritableBridge.java:61) > at QueryResult.readFields0(QueryResult.java:10706) > at QueryResult.readFields(QueryResult.java:10415) > at > org.apache.sqoop.mapreduce.db.DBRecordReader.nextKeyValue(DBRecordReader.java:244) > at > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader.nextKeyValue(SQLServerDBRecordReader.java:148) > at > org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:556) > 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:145) > at > org.apache.sqoop.mapreduce.AutoProgressMapper.run(AutoProgressMapper.java:64) > at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341) > at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164) > at java.security.AccessController.doPrivileged(Nativ
[jira] [Assigned] (SQOOP-3139) sqoop tries to re execute select query during import in case of a connection reset error and this is causing lots of duplicate records from source
[ https://issues.apache.org/jira/browse/SQOOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3139: -- Assignee: Anna Szonyi > sqoop tries to re execute select query during import in case of a connection > reset error and this is causing lots of duplicate records from source > -- > > Key: SQOOP-3139 > URL: https://issues.apache.org/jira/browse/SQOOP-3139 > Project: Sqoop > Issue Type: Bug >Affects Versions: 1.4.6 > Environment: IBM Hadoop distribution: 4.2.0 > version: 1.4.6_IBM_27 > Sqoop 1.4.6_IBM_27 >Reporter: hemanth meka >Assignee: Anna Szonyi > Attachments: SQOOP-3139.patch > > > We cannot reproduce this issue as it depends on network. Here is a edited log > content for understanding the issue. > Log start > . > . > 2017-02-22 07:35:37,638 INFO [main] > org.apache.sqoop.mapreduce.sqlserver.SqlServerRecordReader: Using query: > select sequence_number, analytical_bundle_masked where ( Sequence_Number >= > 8571429 ) AND ( Sequence_Number <= 1000 ) > 2017-02-22 07:35:37,662 INFO [main] > org.apache.sqoop.mapreduce.db.DBRecordReader: Executing query: select > sequence_number, analytical_bundle_masked where ( Sequence_Number >= 8571429 > ) AND ( Sequence_Number <= 1000 ) > 2017-02-22 07:39:00,533 ERROR [main] > org.apache.sqoop.mapreduce.db.DBRecordReader: Top level exception: > com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset > at > com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2399) > at > com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2383) > at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1884) > at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:6685) > at com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:6595) > at > com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:6571) > at com.microsoft.sqlserver.jdbc.TDSReader.readBytes(IOBuffer.java:6864) > at > com.microsoft.sqlserver.jdbc.TDSReader.readWrappedBytes(IOBuffer.java:6886) > at > com.microsoft.sqlserver.jdbc.TDSReader.readUnsignedShort(IOBuffer.java:6801) > at > com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValuePrep(dtv.java:3570) > at com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValue(dtv.java:3936) > at com.microsoft.sqlserver.jdbc.DTV.getValue(dtv.java:226) > at com.microsoft.sqlserver.jdbc.Column.getValue(Column.java:144) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2099) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue(SQLServerResultSet.java:2084) > at > com.microsoft.sqlserver.jdbc.SQLServerResultSet.getString(SQLServerResultSet.java:2427) > at > org.apache.sqoop.lib.JdbcWritableBridge.readString(JdbcWritableBridge.java:71) > at > com.cloudera.sqoop.lib.JdbcWritableBridge.readString(JdbcWritableBridge.java:61) > at QueryResult.readFields0(QueryResult.java:10706) > at QueryResult.readFields(QueryResult.java:10415) > at > org.apache.sqoop.mapreduce.db.DBRecordReader.nextKeyValue(DBRecordReader.java:244) > at > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader.nextKeyValue(SQLServerDBRecordReader.java:148) > at > org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:556) > 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:145) > at > org.apache.sqoop.mapreduce.AutoProgressMapper.run(AutoProgressMapper.java:64) > at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341) > at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164) > 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:1657) > at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158) > 2017-02-22 07:39:00,552 WARN [main] > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader: Trying to recover from > DB read failure: > java.io.IOException: SQLException in nextKeyValue > at > org.apache.sqoop.mapreduce.db.DBRecordReader.nextKeyValue(DBRecordReader.java:277) > at > org.apache.sqoop.mapreduce.db.SQLServerDBRecordReader.nextKeyValue(S
[jira] [Updated] (SQOOP-3140) mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts - old property is used by SQOOP-2055
[ https://issues.apache.org/jira/browse/SQOOP-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3140: --- Attachment: SQOOP-3140.patch > mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts > - old property is used by SQOOP-2055 > -- > > Key: SQOOP-3140 > URL: https://issues.apache.org/jira/browse/SQOOP-3140 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3140.patch > > > mapred.map.max.attempts is > deprecated(http://hadoop.apache.org/docs/r2.4.1/hadoop-project-dist/hadoop-common/DeprecatedProperties.html). > We need to instead, use mapreduce.map.maxattempts for the SQOOP-2055 fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SQOOP-3140) mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts - old property is used by SQOOP-2055
[ https://issues.apache.org/jira/browse/SQOOP-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3140: --- Attachment: (was: SQOOP-3104.patch) > mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts > - old property is used by SQOOP-2055 > -- > > Key: SQOOP-3140 > URL: https://issues.apache.org/jira/browse/SQOOP-3140 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > > mapred.map.max.attempts is > deprecated(http://hadoop.apache.org/docs/r2.4.1/hadoop-project-dist/hadoop-common/DeprecatedProperties.html). > We need to instead, use mapreduce.map.maxattempts for the SQOOP-2055 fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SQOOP-3140) mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts - old property is used by SQOOP-2055
[ https://issues.apache.org/jira/browse/SQOOP-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3140: --- Attachment: SQOOP-3104.patch > mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts > - old property is used by SQOOP-2055 > -- > > Key: SQOOP-3140 > URL: https://issues.apache.org/jira/browse/SQOOP-3140 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3104.patch > > > mapred.map.max.attempts is > deprecated(http://hadoop.apache.org/docs/r2.4.1/hadoop-project-dist/hadoop-common/DeprecatedProperties.html). > We need to instead, use mapreduce.map.maxattempts for the SQOOP-2055 fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SQOOP-3140) mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts - old property is used by SQOOP-2055
[ https://issues.apache.org/jira/browse/SQOOP-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3140: -- Assignee: Anna Szonyi > mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts > - old property is used by SQOOP-2055 > -- > > Key: SQOOP-3140 > URL: https://issues.apache.org/jira/browse/SQOOP-3140 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > > mapred.map.max.attempts is > deprecated(http://hadoop.apache.org/docs/r2.4.1/hadoop-project-dist/hadoop-common/DeprecatedProperties.html). > We need to instead, use mapreduce.map.maxattempts for the SQOOP-2055 fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SQOOP-3140) mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts - old property is used by SQOOP-2055
[ https://issues.apache.org/jira/browse/SQOOP-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3140: --- Description: mapred.map.max.attempts is deprecated(http://hadoop.apache.org/docs/r2.4.1/hadoop-project-dist/hadoop-common/DeprecatedProperties.html). We need to instead, use mapreduce.map.maxattempts for the SQOOP-2055 fix. > mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts > - old property is used by SQOOP-2055 > -- > > Key: SQOOP-3140 > URL: https://issues.apache.org/jira/browse/SQOOP-3140 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi > > mapred.map.max.attempts is > deprecated(http://hadoop.apache.org/docs/r2.4.1/hadoop-project-dist/hadoop-common/DeprecatedProperties.html). > We need to instead, use mapreduce.map.maxattempts for the SQOOP-2055 fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SQOOP-3140) mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts - old property is used by SQOOP-2055
Anna Szonyi created SQOOP-3140: -- Summary: mapred.map.max.attempts is deprecated. Instead, use mapreduce.map.maxattempts - old property is used by SQOOP-2055 Key: SQOOP-3140 URL: https://issues.apache.org/jira/browse/SQOOP-3140 Project: Sqoop Issue Type: Bug Reporter: Anna Szonyi -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SQOOP-3099) Remove all junit3 TestCase extension and test suites.
[ https://issues.apache.org/jira/browse/SQOOP-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3099: --- Attachment: SQOOP-3099-3.patch > Remove all junit3 TestCase extension and test suites. > -- > > Key: SQOOP-3099 > URL: https://issues.apache.org/jira/browse/SQOOP-3099 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3099-3.patch, SQOOP-3099.patch > > > We should no longer have the legacy junit3 execution paths, having to add > junit4 runners and adapters to make it work. > We need to remove all legacy class (Testclass.fail) references and add @Test, > @Before, etc. instead. > Also removed the junit3 suites. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3099) Remove all junit3 TestCase extension and test suites.
[ https://issues.apache.org/jira/browse/SQOOP-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3099: --- Attachment: (was: SQOOP-3099-2.patch) > Remove all junit3 TestCase extension and test suites. > -- > > Key: SQOOP-3099 > URL: https://issues.apache.org/jira/browse/SQOOP-3099 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3099.patch > > > We should no longer have the legacy junit3 execution paths, having to add > junit4 runners and adapters to make it work. > We need to remove all legacy class (Testclass.fail) references and add @Test, > @Before, etc. instead. > Also removed the junit3 suites. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3099) Remove all junit3 TestCase extension and test suites.
[ https://issues.apache.org/jira/browse/SQOOP-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3099: --- Attachment: SQOOP-3099-2.patch > Remove all junit3 TestCase extension and test suites. > -- > > Key: SQOOP-3099 > URL: https://issues.apache.org/jira/browse/SQOOP-3099 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3099-2.patch, SQOOP-3099.patch > > > We should no longer have the legacy junit3 execution paths, having to add > junit4 runners and adapters to make it work. > We need to remove all legacy class (Testclass.fail) references and add @Test, > @Before, etc. instead. > Also removed the junit3 suites. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SQOOP-3105) Postgres Tests should clean up after themselves
Anna Szonyi created SQOOP-3105: -- Summary: Postgres Tests should clean up after themselves Key: SQOOP-3105 URL: https://issues.apache.org/jira/browse/SQOOP-3105 Project: Sqoop Issue Type: Bug Reporter: Anna Szonyi Priority: Minor PostgresqlExportTest and PostgresqlImportTest should clean up the database after they run - created tables should be dropped after the tests have run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3104) Create test categories instead of test suites and naming conventions
[ https://issues.apache.org/jira/browse/SQOOP-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3104: --- Issue Type: Improvement (was: Bug) > Create test categories instead of test suites and naming conventions > > > Key: SQOOP-3104 > URL: https://issues.apache.org/jira/browse/SQOOP-3104 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi > > We are currently unsing test naming conventions to differentiate between > ManualTests, Unit tests and 3rd party tests. > Instead of this, we should use junit4 categories, so it's clear by looking at > a test where it fits. This would also remove the reliance on the test class > name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SQOOP-3104) Create test categories instead of test suites and naming conventions
Anna Szonyi created SQOOP-3104: -- Summary: Create test categories instead of test suites and naming conventions Key: SQOOP-3104 URL: https://issues.apache.org/jira/browse/SQOOP-3104 Project: Sqoop Issue Type: Bug Reporter: Anna Szonyi We are currently unsing test naming conventions to differentiate between ManualTests, Unit tests and 3rd party tests. Instead of this, we should use junit4 categories, so it's clear by looking at a test where it fits. This would also remove the reliance on the test class name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3099) Remove all junit3 TestCase extension and test suites.
[ https://issues.apache.org/jira/browse/SQOOP-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3099: --- Description: We should no longer have the legacy junit3 execution paths, having to add junit4 runners and adapters to make it work. We need to remove all legacy class (Testclass.fail) references and add @Test, @Before, etc. instead. Also removed the junit3 suites. was: We should no longer have the legacy junit3 execution paths, having to add junit4 runners and adapters to make it work. We need to remove all legacy class (Testclass.fail) references and add @Test, @Before, etc. instead. > Remove all junit3 TestCase extension and test suites. > -- > > Key: SQOOP-3099 > URL: https://issues.apache.org/jira/browse/SQOOP-3099 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3099.patch > > > We should no longer have the legacy junit3 execution paths, having to add > junit4 runners and adapters to make it work. > We need to remove all legacy class (Testclass.fail) references and add @Test, > @Before, etc. instead. > Also removed the junit3 suites. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-3099) Remove all junit3 TestCase extension and test suites.
[ https://issues.apache.org/jira/browse/SQOOP-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795512#comment-15795512 ] Anna Szonyi commented on SQOOP-3099: it's a little long, but it's all small changes (remove Testcase import, add @Test, @Before, etc.) > Remove all junit3 TestCase extension and test suites. > -- > > Key: SQOOP-3099 > URL: https://issues.apache.org/jira/browse/SQOOP-3099 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3099.patch > > > We should no longer have the legacy junit3 execution paths, having to add > junit4 runners and adapters to make it work. > We need to remove all legacy class (Testclass.fail) references and add @Test, > @Before, etc. instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3099) Remove all junit3 TestCase extension and test suites.
[ https://issues.apache.org/jira/browse/SQOOP-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3099: --- Attachment: SQOOP-3099.patch > Remove all junit3 TestCase extension and test suites. > -- > > Key: SQOOP-3099 > URL: https://issues.apache.org/jira/browse/SQOOP-3099 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3099.patch > > > We should no longer have the legacy junit3 execution paths, having to add > junit4 runners and adapters to make it work. > We need to remove all legacy class (Testclass.fail) references and add @Test, > @Before, etc. instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SQOOP-3099) Remove all junit3 TestCase extension and test suites.
[ https://issues.apache.org/jira/browse/SQOOP-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3099: -- Assignee: Anna Szonyi > Remove all junit3 TestCase extension and test suites. > -- > > Key: SQOOP-3099 > URL: https://issues.apache.org/jira/browse/SQOOP-3099 > Project: Sqoop > Issue Type: Improvement >Reporter: Anna Szonyi >Assignee: Anna Szonyi > > We should no longer have the legacy junit3 execution paths, having to add > junit4 runners and adapters to make it work. > We need to remove all legacy class (Testclass.fail) references and add @Test, > @Before, etc. instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SQOOP-3099) Remove all junit3 TestCase extension and test suites.
Anna Szonyi created SQOOP-3099: -- Summary: Remove all junit3 TestCase extension and test suites. Key: SQOOP-3099 URL: https://issues.apache.org/jira/browse/SQOOP-3099 Project: Sqoop Issue Type: Improvement Reporter: Anna Szonyi We should no longer have the legacy junit3 execution paths, having to add junit4 runners and adapters to make it work. We need to remove all legacy class (Testclass.fail) references and add @Test, @Before, etc. instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SQOOP-3098) TestImport#testManyColumns fails
Anna Szonyi created SQOOP-3098: -- Summary: TestImport#testManyColumns fails Key: SQOOP-3098 URL: https://issues.apache.org/jira/browse/SQOOP-3098 Project: Sqoop Issue Type: Bug Reporter: Anna Szonyi Currently testImport#testManyColumns is failing on trunk with the javac error "too many constants", however the exception gets swallowed in the test case, so it has been undetected thus far. If the test case is still a valid use-case, then the classwriter needs to be fixed, otherwise the test needs to be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3052: -- Assignee: Anna Szonyi > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi > Fix For: 1.4.7 > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3083) Fault injection targets no longer work after SQOOP-2983
[
https://issues.apache.org/jira/browse/SQOOP-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Szonyi updated SQOOP-3083:
---
Attachment: SQOOP-3083-2.patch
> Fault injection targets no longer work after SQOOP-2983
> ---
>
> Key: SQOOP-3083
> URL: https://issues.apache.org/jira/browse/SQOOP-3083
> Project: Sqoop
> Issue Type: Bug
>Reporter: Anna Szonyi
>Assignee: Anna Szonyi
> Attachments: SQOOP-3083-2.patch, SQOOP-3083.patch
>
>
> Fault injection target fails due to:
> compile-fault-inject:
> [echo] Start weaving aspects in place
> [iajc] OraOopTestCase.java:157 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTestCase.java:157 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTestCase.java:161 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTestCase.java:161 [error] Syntax error, insert "Finally" to
> complete TryStatement
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:56 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:56 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Duplicate local variable stmt
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "Finally"
> to complete TryStatement
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "Finally"
> to complete BlockStatements
> [iajc] }
> [iajc]
> [iajc] OracleData.java:240 [error] Syntax error on token "(", { expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OracleData.java:240 [error] Syntax error on token ")", ; expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OracleData.java:243 [error] Syntax error, insert "}" to complete
> Block
> [iajc] }
> [iajc]
> [iajc] OracleData.java:243 [error] Syntax error, insert "Finally" to
> complete BlockStatements
> [iajc] }
> [iajc]
> [iajc]
> [iajc] 17 errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SQOOP-3083) Fault injection targets no longer work after SQOOP-2983
[
https://issues.apache.org/jira/browse/SQOOP-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Szonyi updated SQOOP-3083:
---
Attachment: SQOOP-3083.patch
> Fault injection targets no longer work after SQOOP-2983
> ---
>
> Key: SQOOP-3083
> URL: https://issues.apache.org/jira/browse/SQOOP-3083
> Project: Sqoop
> Issue Type: Bug
>Reporter: Anna Szonyi
>Assignee: Anna Szonyi
> Attachments: SQOOP-3083.patch
>
>
> Fault injection target fails due to:
> compile-fault-inject:
> [echo] Start weaving aspects in place
> [iajc] OraOopTestCase.java:157 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTestCase.java:157 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTestCase.java:161 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTestCase.java:161 [error] Syntax error, insert "Finally" to
> complete TryStatement
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:56 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:56 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Duplicate local variable stmt
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "Finally"
> to complete TryStatement
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "Finally"
> to complete BlockStatements
> [iajc] }
> [iajc]
> [iajc] OracleData.java:240 [error] Syntax error on token "(", { expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OracleData.java:240 [error] Syntax error on token ")", ; expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OracleData.java:243 [error] Syntax error, insert "}" to complete
> Block
> [iajc] }
> [iajc]
> [iajc] OracleData.java:243 [error] Syntax error, insert "Finally" to
> complete BlockStatements
> [iajc] }
> [iajc]
> [iajc]
> [iajc] 17 errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SQOOP-3083) Fault injection targets no longer work after SQOOP-2983
[
https://issues.apache.org/jira/browse/SQOOP-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Szonyi reassigned SQOOP-3083:
--
Assignee: Anna Szonyi
> Fault injection targets no longer work after SQOOP-2983
> ---
>
> Key: SQOOP-3083
> URL: https://issues.apache.org/jira/browse/SQOOP-3083
> Project: Sqoop
> Issue Type: Bug
>Reporter: Anna Szonyi
>Assignee: Anna Szonyi
>
> Fault injection target fails due to:
> compile-fault-inject:
> [echo] Start weaving aspects in place
> [iajc] OraOopTestCase.java:157 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTestCase.java:157 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTestCase.java:161 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTestCase.java:161 [error] Syntax error, insert "Finally" to
> complete TryStatement
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:56 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:56 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Syntax error on token "(", {
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Duplicate local variable stmt
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:78 [error] Syntax error on token ")", ;
> expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "Finally"
> to complete TryStatement
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "}" to
> complete Block
> [iajc] }
> [iajc]
> [iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "Finally"
> to complete BlockStatements
> [iajc] }
> [iajc]
> [iajc] OracleData.java:240 [error] Syntax error on token "(", { expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OracleData.java:240 [error] Syntax error on token ")", ; expected
> [iajc] try (Statement stmt = conn.createStatement()) {
> [iajc]
> [iajc] OracleData.java:243 [error] Syntax error, insert "}" to complete
> Block
> [iajc] }
> [iajc]
> [iajc] OracleData.java:243 [error] Syntax error, insert "Finally" to
> complete BlockStatements
> [iajc] }
> [iajc]
> [iajc]
> [iajc] 17 errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SQOOP-3084) org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be changed after SQOOP-3051
[
https://issues.apache.org/jira/browse/SQOOP-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Szonyi updated SQOOP-3084:
---
Description: Due to ivy changes in 3051 the path of
org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
changed, as there is no longer a hadoop$\{hadoopversion\}test, just test (was:
Due to ivy changes in 3051 the path of
org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
changed, as there is no longer a hadoop $\{hadoopversion\}test, just test)
> org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
> changed after SQOOP-3051
> ---
>
> Key: SQOOP-3084
> URL: https://issues.apache.org/jira/browse/SQOOP-3084
> Project: Sqoop
> Issue Type: Bug
>Reporter: Anna Szonyi
>Assignee: Anna Szonyi
> Attachments: SQOOP-3084.patch
>
>
> Due to ivy changes in 3051 the path of
> org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
> changed, as there is no longer a hadoop$\{hadoopversion\}test, just test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SQOOP-3084) org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be changed after SQOOP-3051
[
https://issues.apache.org/jira/browse/SQOOP-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Szonyi updated SQOOP-3084:
---
Description: Due to ivy changes in 3051 the path of
org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
changed, as there is no longer a hadoop${hadoopversion}test, just test
> org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
> changed after SQOOP-3051
> ---
>
> Key: SQOOP-3084
> URL: https://issues.apache.org/jira/browse/SQOOP-3084
> Project: Sqoop
> Issue Type: Bug
>Reporter: Anna Szonyi
>Assignee: Anna Szonyi
> Attachments: SQOOP-3084.patch
>
>
> Due to ivy changes in 3051 the path of
> org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
> changed, as there is no longer a hadoop${hadoopversion}test, just test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SQOOP-3084) org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be changed after SQOOP-3051
[
https://issues.apache.org/jira/browse/SQOOP-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Szonyi updated SQOOP-3084:
---
Description: Due to ivy changes in 3051 the path of
org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
changed, as there is no longer a hadoop\$\{hadoopversion\}test, just test
(was: Due to ivy changes in 3051 the path of
org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
changed, as there is no longer a hadoop${hadoopversion}test, just test)
> org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
> changed after SQOOP-3051
> ---
>
> Key: SQOOP-3084
> URL: https://issues.apache.org/jira/browse/SQOOP-3084
> Project: Sqoop
> Issue Type: Bug
>Reporter: Anna Szonyi
>Assignee: Anna Szonyi
> Attachments: SQOOP-3084.patch
>
>
> Due to ivy changes in 3051 the path of
> org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
> changed, as there is no longer a hadoop\$\{hadoopversion\}test, just test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SQOOP-3084) org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be changed after SQOOP-3051
[
https://issues.apache.org/jira/browse/SQOOP-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Szonyi updated SQOOP-3084:
---
Description: Due to ivy changes in 3051 the path of
org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
changed, as there is no longer a hadoop $\{hadoopversion\}test, just test
(was: Due to ivy changes in 3051 the path of
org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
changed, as there is no longer a hadoop\$\{hadoopversion\}test, just test)
> org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
> changed after SQOOP-3051
> ---
>
> Key: SQOOP-3084
> URL: https://issues.apache.org/jira/browse/SQOOP-3084
> Project: Sqoop
> Issue Type: Bug
>Reporter: Anna Szonyi
>Assignee: Anna Szonyi
> Attachments: SQOOP-3084.patch
>
>
> Due to ivy changes in 3051 the path of
> org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be
> changed, as there is no longer a hadoop $\{hadoopversion\}test, just test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SQOOP-3084) org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be changed after SQOOP-3051
[ https://issues.apache.org/jira/browse/SQOOP-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3084: --- Attachment: SQOOP-3084.patch > org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be > changed after SQOOP-3051 > --- > > Key: SQOOP-3084 > URL: https://issues.apache.org/jira/browse/SQOOP-3084 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3084.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SQOOP-3084) org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be changed after SQOOP-3051
[ https://issues.apache.org/jira/browse/SQOOP-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3084: -- Assignee: Anna Szonyi > org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be > changed after SQOOP-3051 > --- > > Key: SQOOP-3084 > URL: https://issues.apache.org/jira/browse/SQOOP-3084 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3084.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SQOOP-3084) org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be changed after SQOOP-3051
Anna Szonyi created SQOOP-3084: -- Summary: org/aspectj/tools/ant/taskdefs/aspectjTaskdefs.properties path needs to be changed after SQOOP-3051 Key: SQOOP-3084 URL: https://issues.apache.org/jira/browse/SQOOP-3084 Project: Sqoop Issue Type: Bug Reporter: Anna Szonyi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SQOOP-3083) Fault injection targets no longer work after SQOOP-2983
Anna Szonyi created SQOOP-3083:
--
Summary: Fault injection targets no longer work after SQOOP-2983
Key: SQOOP-3083
URL: https://issues.apache.org/jira/browse/SQOOP-3083
Project: Sqoop
Issue Type: Bug
Reporter: Anna Szonyi
Fault injection target fails due to:
compile-fault-inject:
[echo] Start weaving aspects in place
[iajc] OraOopTestCase.java:157 [error] Syntax error on token "(", {
expected
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OraOopTestCase.java:157 [error] Syntax error on token ")", ;
expected
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OraOopTestCase.java:161 [error] Syntax error, insert "}" to
complete Block
[iajc] }
[iajc]
[iajc] OraOopTestCase.java:161 [error] Syntax error, insert "Finally" to
complete TryStatement
[iajc] }
[iajc]
[iajc] OraOopTypesTest.java:56 [error] Syntax error on token "(", {
expected
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OraOopTypesTest.java:56 [error] Syntax error on token ")", ;
expected
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OraOopTypesTest.java:78 [error] Syntax error on token "(", {
expected
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OraOopTypesTest.java:78 [error] Duplicate local variable stmt
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OraOopTypesTest.java:78 [error] Syntax error on token ")", ;
expected
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "}" to
complete Block
[iajc] }
[iajc]
[iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "Finally" to
complete TryStatement
[iajc] }
[iajc]
[iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "}" to
complete Block
[iajc] }
[iajc]
[iajc] OraOopTypesTest.java:157 [error] Syntax error, insert "Finally" to
complete BlockStatements
[iajc] }
[iajc]
[iajc] OracleData.java:240 [error] Syntax error on token "(", { expected
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OracleData.java:240 [error] Syntax error on token ")", ; expected
[iajc] try (Statement stmt = conn.createStatement()) {
[iajc]
[iajc] OracleData.java:243 [error] Syntax error, insert "}" to complete
Block
[iajc] }
[iajc]
[iajc] OracleData.java:243 [error] Syntax error, insert "Finally" to
complete BlockStatements
[iajc] }
[iajc]
[iajc]
[iajc] 17 errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat + add compatibility with SQOOP-3066
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Attachment: SQOOP-3081-2.patch > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat + add > compatibility with SQOOP-3066 > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3081-2.patch, SQOOP-3081-3.patch, SQOOP-3081.patch > > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code and compatible with SQOOP-3066. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat + add compatibility with SQOOP-3066
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Attachment: SQOOP-3081-3.patch > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat + add > compatibility with SQOOP-3066 > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3081-2.patch, SQOOP-3081-3.patch, SQOOP-3081.patch > > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code and compatible with SQOOP-3066. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Description: Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to make it consistent with the rest of the code and compatible with SQOOP-3066. was: Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to make it consistent with the rest of the code and add escaping to the rest of the column variables. > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3081.patch > > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code and compatible with SQOOP-3066. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat + add compatibility with SQOOP-3066
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Summary: use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat + add compatibility with SQOOP-3066 (was: use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat) > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat + add > compatibility with SQOOP-3066 > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3081.patch > > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code and compatible with SQOOP-3066. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Description: Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to make it consistent with the rest of the code and add escaping to the rest of the column variables. was: Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to make it consistent with the rest of the code and add escaping to the rest of the column variables. > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3081.patch > > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code and add escaping to the rest of > the column variables. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Attachment: SQOOP-3081.patch > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Attachments: SQOOP-3081.patch > > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code and add escaping to the rest of > the column variables. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Description: Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to make it consistent with the rest of the code and add escaping to the rest of the column variables. was: Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to make it consistent with the rest of the code. > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code and add escaping to the rest of > the column variables. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Description: Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to make it consistent with the rest of the code. was: Introduce OracleEscapeUtils.escapeIdentifiers In > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Description: Introduce OracleEscapeUtils.escapeIdentifiers In was: Changes made in 2990 were not covered by 3066 (probably wasn't found as it wasn't using OracleUtils.escapeIdentifier, just simple qoutes). Make the code consistent with the switches introduces by 3066. > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi > > Introduce OracleEscapeUtils.escapeIdentifiers In > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3081: -- Assignee: Anna Szonyi > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi >Assignee: Anna Szonyi > > Introduce OracleEscapeUtils.escapeIdentifiers In OracleUpsertOutputFormat to > make it consistent with the rest of the code. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Summary: use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat (was: use EscapeUtils to escape columns) > use OracleEscapeUtils.escapeIdentifier OracleUpsertOutputFormat > --- > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi > > Changes made in 2990 were not covered by 3066 (probably wasn't found as it > wasn't using OracleUtils.escapeIdentifier, just simple qoutes). > Make the code consistent with the switches introduces by 3066. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3081) use EscapeUtils to escape columns
[ https://issues.apache.org/jira/browse/SQOOP-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3081: --- Summary: use EscapeUtils to escape columns (was: Fix inconsistency between 3066 and 2990) > use EscapeUtils to escape columns > - > > Key: SQOOP-3081 > URL: https://issues.apache.org/jira/browse/SQOOP-3081 > Project: Sqoop > Issue Type: Bug >Reporter: Anna Szonyi > > Changes made in 2990 were not covered by 3066 (probably wasn't found as it > wasn't using OracleUtils.escapeIdentifier, just simple qoutes). > Make the code consistent with the switches introduces by 3066. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SQOOP-3081) Fix inconsistency between 3066 and 2990
Anna Szonyi created SQOOP-3081: -- Summary: Fix inconsistency between 3066 and 2990 Key: SQOOP-3081 URL: https://issues.apache.org/jira/browse/SQOOP-3081 Project: Sqoop Issue Type: Bug Reporter: Anna Szonyi Changes made in 2990 were not covered by 3066 (probably wasn't found as it wasn't using OracleUtils.escapeIdentifier, just simple qoutes). Make the code consistent with the switches introduces by 3066. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3051) Remove/delete obsolete profiles from build.xml
[ https://issues.apache.org/jira/browse/SQOOP-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3051: --- Attachment: SQOOP-3051-1.patch > Remove/delete obsolete profiles from build.xml > -- > > Key: SQOOP-3051 > URL: https://issues.apache.org/jira/browse/SQOOP-3051 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Critical > Fix For: 1.4.7 > > Attachments: SQOOP-3051-1.patch, SQOOP-3051.patch > > > As [SQOOP-3050] is implemented all the obsolete profiles/settings should be > eliminated to make the dependency tree and the whole build environment around > Sqoop trunk version simpler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3051) Remove/delete obsolete profiles from build.xml
[ https://issues.apache.org/jira/browse/SQOOP-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3051: --- Attachment: (was: SQOOP-3051-1.patch) > Remove/delete obsolete profiles from build.xml > -- > > Key: SQOOP-3051 > URL: https://issues.apache.org/jira/browse/SQOOP-3051 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Critical > Fix For: 1.4.7 > > Attachments: SQOOP-3051-1.patch, SQOOP-3051.patch > > > As [SQOOP-3050] is implemented all the obsolete profiles/settings should be > eliminated to make the dependency tree and the whole build environment around > Sqoop trunk version simpler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3051) Remove/delete obsolete profiles from build.xml
[ https://issues.apache.org/jira/browse/SQOOP-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3051: --- Attachment: SQOOP-3051-1.patch > Remove/delete obsolete profiles from build.xml > -- > > Key: SQOOP-3051 > URL: https://issues.apache.org/jira/browse/SQOOP-3051 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Critical > Fix For: 1.4.7 > > Attachments: SQOOP-3051-1.patch, SQOOP-3051.patch > > > As [SQOOP-3050] is implemented all the obsolete profiles/settings should be > eliminated to make the dependency tree and the whole build environment around > Sqoop trunk version simpler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-3050) Create an compile/execution profile which is capable of running all the available test (including the 3rd party tests)
[ https://issues.apache.org/jira/browse/SQOOP-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15721936#comment-15721936 ] Anna Szonyi commented on SQOOP-3050: hadoopversion=260, hbaseprofile=95 works for all third party test. > Create an compile/execution profile which is capable of running all the > available test (including the 3rd party tests) > -- > > Key: SQOOP-3050 > URL: https://issues.apache.org/jira/browse/SQOOP-3050 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Blocker > Fix For: 1.4.7 > > > The current stage of the trunk version (1.4.7-SANPSHOT) contains several > different profiles (defined on build.xml level), but none of them able to > execute all the available tests. Usually the problem appears on the level of > "integration/3rd party tests (good example here HCatalogImportTest). > The task would be to create a profile (with appropriate dependent library > version) which is capable of running all the available test cases, and if any > of those test cases needs to be triaged/fixed it should be done to within the > same scope. > The major goal of this JIRA would be to have at least one profile with we > would be able to release 1.4.7 with all tests in green. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SQOOP-3050) Create an compile/execution profile which is capable of running all the available test (including the 3rd party tests)
[ https://issues.apache.org/jira/browse/SQOOP-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi resolved SQOOP-3050. Resolution: Fixed > Create an compile/execution profile which is capable of running all the > available test (including the 3rd party tests) > -- > > Key: SQOOP-3050 > URL: https://issues.apache.org/jira/browse/SQOOP-3050 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Blocker > Fix For: 1.4.7 > > > The current stage of the trunk version (1.4.7-SANPSHOT) contains several > different profiles (defined on build.xml level), but none of them able to > execute all the available tests. Usually the problem appears on the level of > "integration/3rd party tests (good example here HCatalogImportTest). > The task would be to create a profile (with appropriate dependent library > version) which is capable of running all the available test cases, and if any > of those test cases needs to be triaged/fixed it should be done to within the > same scope. > The major goal of this JIRA would be to have at least one profile with we > would be able to release 1.4.7 with all tests in green. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-3067) Add an cmd line option to support split-by feature for database functions/expressions
[ https://issues.apache.org/jira/browse/SQOOP-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15721752#comment-15721752 ] Anna Szonyi commented on SQOOP-3067: As discussed with [~maugli], assigning this to me. > Add an cmd line option to support split-by feature for database > functions/expressions > - > > Key: SQOOP-3067 > URL: https://issues.apache.org/jira/browse/SQOOP-3067 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi > Fix For: 1.4.7 > > > Due to the fact, if the [SQOOP-2737] escaping feature is enabled, the > split-by column name is also escaped and quoted properly, we do need to have > an option for split-by which would accept DB related function/expressions, > but those expressions should not be quoted/escaped. > This feature is dependent from the [SQOOP-3066], so first that one has to be > implemented and merged to the source. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SQOOP-3067) Add an cmd line option to support split-by feature for database functions/expressions
[ https://issues.apache.org/jira/browse/SQOOP-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3067: -- Assignee: Anna Szonyi (was: Attila Szabo) > Add an cmd line option to support split-by feature for database > functions/expressions > - > > Key: SQOOP-3067 > URL: https://issues.apache.org/jira/browse/SQOOP-3067 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi > Fix For: 1.4.7 > > > Due to the fact, if the [SQOOP-2737] escaping feature is enabled, the > split-by column name is also escaped and quoted properly, we do need to have > an option for split-by which would accept DB related function/expressions, > but those expressions should not be quoted/escaped. > This feature is dependent from the [SQOOP-3066], so first that one has to be > implemented and merged to the source. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3051) Remove/delete obsolete profiles from build.xml
[ https://issues.apache.org/jira/browse/SQOOP-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3051: --- Attachment: SQOOP-3051.patch > Remove/delete obsolete profiles from build.xml > -- > > Key: SQOOP-3051 > URL: https://issues.apache.org/jira/browse/SQOOP-3051 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Critical > Fix For: 1.4.7 > > Attachments: SQOOP-3051.patch > > > As [SQOOP-3050] is implemented all the obsolete profiles/settings should be > eliminated to make the dependency tree and the whole build environment around > Sqoop trunk version simpler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3051) Remove/delete obsolete profiles from build.xml
[ https://issues.apache.org/jira/browse/SQOOP-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3051: --- Attachment: (was: SQOOP-3051.patch) > Remove/delete obsolete profiles from build.xml > -- > > Key: SQOOP-3051 > URL: https://issues.apache.org/jira/browse/SQOOP-3051 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Critical > Fix For: 1.4.7 > > > As [SQOOP-3050] is implemented all the obsolete profiles/settings should be > eliminated to make the dependency tree and the whole build environment around > Sqoop trunk version simpler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open
[ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: --- Assignee: (was: Anna Szonyi) > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer > friendly / open > --- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo > Fix For: 1.4.7 > > > The current trunk version can only be build with Ant/Ivy combination, which > has some painful limitations (resolve is slow / needs to be tweaked to use > only caches, the current profile / variable based settings are not working in > IDEs out of the box, the current solution does not download the related > sources, etc.) > It would be nice to provide a solution, which would give the possibility for > the developers to choose between the nowadays well used build infrsturctures > (e.g. Maven, Gradle, etc.). For this solution it would be also essential to > keep the different build files (if there is more then one) synchronized > easily, and the configuration wouldn't diverege by time. Test execution has > to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide > three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3051) Remove/delete obsolete profiles from build.xml
[ https://issues.apache.org/jira/browse/SQOOP-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3051: --- Attachment: SQOOP-3051.patch > Remove/delete obsolete profiles from build.xml > -- > > Key: SQOOP-3051 > URL: https://issues.apache.org/jira/browse/SQOOP-3051 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Anna Szonyi >Priority: Critical > Fix For: 1.4.7 > > Attachments: SQOOP-3051.patch > > > As [SQOOP-3050] is implemented all the obsolete profiles/settings should be > eliminated to make the dependency tree and the whole build environment around > Sqoop trunk version simpler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3056) Add ant ivy report target
[ https://issues.apache.org/jira/browse/SQOOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3056: --- Attachment: SQOOP-3056.patch > Add ant ivy report target > - > > Key: SQOOP-3056 > URL: https://issues.apache.org/jira/browse/SQOOP-3056 > Project: Sqoop > Issue Type: Sub-task >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Fix For: 1.4.7 > > Attachments: SQOOP-3056.patch > > > There are several versions of Avro coming into the project (1.74, 1.7.5, > 1.8.0) and they are incompatible, so we need to figure out which versions to > exclude from which project. > You should be able to call ant report and look at the generated graph or html > to figure out what are the transitive dependencies -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3055) SQOOP-3055 MYSQL tests are failing due to the tests ignoring specified username, password and dbname, trying to connect to specified host using "currentUser"
[
https://issues.apache.org/jira/browse/SQOOP-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anna Szonyi updated SQOOP-3055:
---
Attachment: SQOOP-3055-4.patch
> SQOOP-3055 MYSQL tests are failing due to the tests ignoring specified
> username, password and dbname, trying to connect to specified host using
> "currentUser"
> -
>
> Key: SQOOP-3055
> URL: https://issues.apache.org/jira/browse/SQOOP-3055
> Project: Sqoop
> Issue Type: Sub-task
>Reporter: Anna Szonyi
>Assignee: Anna Szonyi
> Fix For: 1.4.7
>
> Attachments: SQOOP-3055-2.patch, SQOOP-3055-3.patch,
> SQOOP-3055-4.patch, SQOOP-3055.patch
>
>
> MYSQL test are using option.setUser(MySQLTestUtils.getcurrentUser()), where
> MySQLTestUtils.getCurrentUser() return
> System.getenv("USER");
> or
> ..
> whoamiArgs[0] = "whoami";
> ..
> p = Runtime.getRuntime().exec(whoamiArgs);
> Whereas it should use the userName and userPass as specified if called with
> -D parameters (if they are specified, otherwise should fall back to ).
> Currently the tests could only run when using localhost + root.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SQOOP-3056) Add ant ivy report target
[ https://issues.apache.org/jira/browse/SQOOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3056: -- Assignee: Anna Szonyi > Add ant ivy report target > - > > Key: SQOOP-3056 > URL: https://issues.apache.org/jira/browse/SQOOP-3056 > Project: Sqoop > Issue Type: Sub-task >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Fix For: 1.4.7 > > > There are several versions of Avro coming into the project (1.74, 1.7.5, > 1.8.0) and they are incompatible, so we need to figure out which versions to > exclude from which project. > You should be able to call ant report and look at the generated graph or html > to figure out what are the transitive dependencies -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SQOOP-3057) Fix failing 3rd party Oracle tests
[ https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi reassigned SQOOP-3057: -- Assignee: Anna Szonyi > Fix failing 3rd party Oracle tests > -- > > Key: SQOOP-3057 > URL: https://issues.apache.org/jira/browse/SQOOP-3057 > Project: Sqoop > Issue Type: Sub-task >Reporter: Anna Szonyi >Assignee: Anna Szonyi > Fix For: 1.4.7 > > > Oracle tests are failing due to difference in the case of "id" and "msg" > between the table creation and verification steps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3057) Fix failing 3rd party Oracle tests
[ https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3057: --- Description: Oracle tests are failing due to difference in the case of "id" and "msg" between the table creation and verification steps. (was: Oracle tests are failing due to difference in the case of "id" and "msg" between the table creation and verification steps.) > Fix failing 3rd party Oracle tests > -- > > Key: SQOOP-3057 > URL: https://issues.apache.org/jira/browse/SQOOP-3057 > Project: Sqoop > Issue Type: Sub-task >Reporter: Anna Szonyi > Fix For: 1.4.7 > > > Oracle tests are failing due to difference in the case of "id" and "msg" > between the table creation and verification steps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SQOOP-3057) Fix failing 3rd party Oracle tests
[ https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3057: --- Description: Oracle tests are failing due to difference in the case of "id" and "msg" between the table creation and verification steps. > Fix failing 3rd party Oracle tests > -- > > Key: SQOOP-3057 > URL: https://issues.apache.org/jira/browse/SQOOP-3057 > Project: Sqoop > Issue Type: Sub-task >Reporter: Anna Szonyi > Fix For: 1.4.7 > > > Oracle tests are failing due to difference in the case of "id" and "msg" > between the table creation and verification steps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
