[jira] [Commented] (SQOOP-3059) sqoop import into hive converting decimals to decimals

[Ying Cao (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707481#comment-15707481
 ] 

Ying Cao commented on SQOOP-3059:
-

[~bleeapache]
[~usblee]
I found the decimal type mapping is invoked by SQOOP-380, do you have any 
suggestion for mapping of decimal? By default it will converting to double. 
Thanks

> sqoop import into hive converting decimals to decimals
> --
>
> Key: SQOOP-3059
> URL: https://issues.apache.org/jira/browse/SQOOP-3059
> Project: Sqoop
>  Issue Type: Improvement
>  Components: hive-integration
> Environment: Redhat 6.6, Sqoop 1.4.6
>Reporter: Ying Cao
>Priority: Minor
>
> By default sqoop import into hive converting decimals to double, Decimal type 
> provide more accurate values wider range than Double, so by default way some 
> data will be truncated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SQOOP-2928) Sqoop2: Fix MySQL repository creation

[Brian Albright (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706847#comment-15706847
 ] 

Brian Albright commented on SQOOP-2928:
---

Your solution to this bug is...reconfigure your MySQL server?

Veto - this needs a real fix.

> Sqoop2: Fix MySQL repository creation
> -
>
> Key: SQOOP-2928
> URL: https://issues.apache.org/jira/browse/SQOOP-2928
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Szabolcs Vasas
>Assignee: Szabolcs Vasas
>  Labels: newbie
> Fix For: no-release
>
>
> Currently the MySQL repository creation/update fails with the following error:
> Can't execute query: CREATE DATABASE IF NOT EXISTS"SQOOP"
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error 
> in your SQL syntax; check the manual that corresponds to your MySQL server 
> version for the right syntax to use near '"SQOOP"' at line 1
> MySQL uses the nonstandard ` (backtick) character instead of " to quote 
> system identifiers so the database creation command constant has to be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SQOOP-3057) Fix failing 3rd party Oracle tests

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706211#comment-15706211
 ] 

Hudson commented on SQOOP-3057:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop100 #1038 (See 
[https://builds.apache.org/job/Sqoop-hadoop100/1038/])
SQOOP-3057: Fixing 3rd party Oracle tests failing due to invalid case of 
(maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=916cae19f8851f72e425f7d7bbdbdd92f5fe1bc5])
* (edit) src/test/com/cloudera/sqoop/manager/OracleExportTest.java
* (edit) src/test/org/apache/sqoop/manager/oracle/OracleCallExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java


> 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
>
> Attachments: SQOOP-3057.patch
>
>
> 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] [Commented] (SQOOP-3057) Fix failing 3rd party Oracle tests

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706141#comment-15706141
 ] 

Hudson commented on SQOOP-3057:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop23 #1275 (See 
[https://builds.apache.org/job/Sqoop-hadoop23/1275/])
SQOOP-3057: Fixing 3rd party Oracle tests failing due to invalid case of 
(maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=916cae19f8851f72e425f7d7bbdbdd92f5fe1bc5])
* (edit) src/test/org/apache/sqoop/manager/oracle/OracleCallExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/OracleExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java


> 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
>
> Attachments: SQOOP-3057.patch
>
>
> 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] [Commented] (SQOOP-3057) Fix failing 3rd party Oracle tests

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706125#comment-15706125
 ] 

Hudson commented on SQOOP-3057:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop20 #1073 (See 
[https://builds.apache.org/job/Sqoop-hadoop20/1073/])
SQOOP-3057: Fixing 3rd party Oracle tests failing due to invalid case of 
(maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=916cae19f8851f72e425f7d7bbdbdd92f5fe1bc5])
* (edit) src/test/com/cloudera/sqoop/manager/OracleExportTest.java
* (edit) src/test/org/apache/sqoop/manager/oracle/OracleCallExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java


> 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
>
> Attachments: SQOOP-3057.patch
>
>
> 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)

Re: Review Request 54168: SQOOP-3057 3rd party Oracle tests are failing

[Attila Szabo]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54168/#review157286
---


Ship it!




Ship It!

- Attila Szabo


On Nov. 29, 2016, 4:52 p.m., Anna Szonyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54168/
> ---
> 
> (Updated Nov. 29, 2016, 4:52 p.m.)
> 
> 
> Review request for Sqoop, Attila Szabo and Szabolcs Vasas.
> 
> 
> Bugs: SQOOP-3057
> https://issues.apache.org/jira/browse/SQOOP-3057
> 
> 
> Repository: sqoop-trunk
> 
> 
> Description
> ---
> 
> 3rd party Oracle tests are failing due to incorrect case of "id" "msg" 
> between verification and table creations (verify needs upper, oracle creates 
> lowercase names). Currently the OracleManagerTest:testOracleImport test is 
> failing as it seems tha passing of timezone is incorrect - it should be fixed 
> in a different JIRA. + Fixed an incorrect import
> 
> 
> Diffs
> -
> 
>   src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java 2e2448a 
>   src/test/com/cloudera/sqoop/manager/OracleExportTest.java e716510 
>   src/test/org/apache/sqoop/manager/oracle/OracleCallExportTest.java 431df0f 
> 
> Diff: https://reviews.apache.org/r/54168/diff/
> 
> 
> Testing
> ---
> 
> ran ant clean test, ant clean test -Dhadoopversion=260 -Dhbaseprofile=95 
> -Dthirdparty=true -Dsqoop.thirdparty.lib.dir=$3RD_PARTY_LIB  
> -Dmaxmemory=2048m -DtargetJavaVersion=1.7 -DjavaVersion=1.7 
> -Djava.security.egd=file:///dev/./urandom 
> -Dsqoop.test.oracle.connectstring=$ORACLE_CONN 
> -Dmapred.child.java.opts="-Djava.security.egd=file:/dev/../dev/urandom" 
> -Dtest.timeout=100 -Dtestcase=Oracle*Test
> 
> 
> Thanks,
> 
> Anna Szonyi
> 
>

[jira] [Commented] (SQOOP-3057) Fix failing 3rd party Oracle tests

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706103#comment-15706103
 ] 

Hudson commented on SQOOP-3057:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop200 #1079 (See 
[https://builds.apache.org/job/Sqoop-hadoop200/1079/])
SQOOP-3057: Fixing 3rd party Oracle tests failing due to invalid case of 
(maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=916cae19f8851f72e425f7d7bbdbdd92f5fe1bc5])
* (edit) src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java
* (edit) src/test/com/cloudera/sqoop/manager/OracleExportTest.java
* (edit) src/test/org/apache/sqoop/manager/oracle/OracleCallExportTest.java


> 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
>
> Attachments: SQOOP-3057.patch
>
>
> 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] [Commented] (SQOOP-3057) Fix failing 3rd party Oracle tests

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706057#comment-15706057
 ] 

ASF subversion and git services commented on SQOOP-3057:


Commit 916cae19f8851f72e425f7d7bbdbdd92f5fe1bc5 in sqoop's branch 
refs/heads/trunk from [~maugli]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=916cae1 ]

SQOOP-3057: Fixing 3rd party Oracle tests failing
due to invalid case of column names

(Anna Szonyi via Attila Szabo)


> 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
>
> Attachments: SQOOP-3057.patch
>
>
> 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] [Commented] (SQOOP-3057) Fix failing 3rd party Oracle tests

[Attila Szabo (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706059#comment-15706059
 ] 

Attila Szabo commented on SQOOP-3057:
-

HI [~szonyi],

Thanks for the contribution!

> 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
>
> Attachments: SQOOP-3057.patch
>
>
> 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

[Attila Szabo (JIRA)]

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

Attila Szabo updated SQOOP-3057:

Attachment: SQOOP-3057.patch

> 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
>
> Attachments: SQOOP-3057.patch
>
>
> 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)

Re: Review Request 54168: SQOOP-3057 3rd party Oracle tests are failing

[Szabolcs Vasas]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54168/#review157279
---


Ship it!




Ship It!

- Szabolcs Vasas


On Nov. 29, 2016, 4:52 p.m., Anna Szonyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54168/
> ---
> 
> (Updated Nov. 29, 2016, 4:52 p.m.)
> 
> 
> Review request for Sqoop, Attila Szabo and Szabolcs Vasas.
> 
> 
> Bugs: SQOOP-3057
> https://issues.apache.org/jira/browse/SQOOP-3057
> 
> 
> Repository: sqoop-trunk
> 
> 
> Description
> ---
> 
> 3rd party Oracle tests are failing due to incorrect case of "id" "msg" 
> between verification and table creations (verify needs upper, oracle creates 
> lowercase names). Currently the OracleManagerTest:testOracleImport test is 
> failing as it seems tha passing of timezone is incorrect - it should be fixed 
> in a different JIRA. + Fixed an incorrect import
> 
> 
> Diffs
> -
> 
>   src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java 2e2448a 
>   src/test/com/cloudera/sqoop/manager/OracleExportTest.java e716510 
>   src/test/org/apache/sqoop/manager/oracle/OracleCallExportTest.java 431df0f 
> 
> Diff: https://reviews.apache.org/r/54168/diff/
> 
> 
> Testing
> ---
> 
> ran ant clean test, ant clean test -Dhadoopversion=260 -Dhbaseprofile=95 
> -Dthirdparty=true -Dsqoop.thirdparty.lib.dir=$3RD_PARTY_LIB  
> -Dmaxmemory=2048m -DtargetJavaVersion=1.7 -DjavaVersion=1.7 
> -Djava.security.egd=file:///dev/./urandom 
> -Dsqoop.test.oracle.connectstring=$ORACLE_CONN 
> -Dmapred.child.java.opts="-Djava.security.egd=file:/dev/../dev/urandom" 
> -Dtest.timeout=100 -Dtestcase=Oracle*Test
> 
> 
> Thanks,
> 
> Anna Szonyi
> 
>

Review Request 54168: SQOOP-3057 3rd party Oracle tests are failing

[Anna Szonyi]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54168/
---

Review request for Sqoop, Attila Szabo and Szabolcs Vasas.


Bugs: SQOOP-3057
https://issues.apache.org/jira/browse/SQOOP-3057


Repository: sqoop-trunk


Description
---

3rd party Oracle tests are failing due to incorrect case of "id" "msg" between 
verification and table creations (verify needs upper, oracle creates lowercase 
names). Currently the OracleManagerTest:testOracleImport test is failing as it 
seems tha passing of timezone is incorrect - it should be fixed in a different 
JIRA. + Fixed an incorrect import


Diffs
-

  src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java 2e2448a 
  src/test/com/cloudera/sqoop/manager/OracleExportTest.java e716510 
  src/test/org/apache/sqoop/manager/oracle/OracleCallExportTest.java 431df0f 

Diff: https://reviews.apache.org/r/54168/diff/


Testing
---

ran ant clean test, ant clean test -Dhadoopversion=260 -Dhbaseprofile=95 
-Dthirdparty=true -Dsqoop.thirdparty.lib.dir=$3RD_PARTY_LIB  -Dmaxmemory=2048m 
-DtargetJavaVersion=1.7 -DjavaVersion=1.7 
-Djava.security.egd=file:///dev/./urandom 
-Dsqoop.test.oracle.connectstring=$ORACLE_CONN 
-Dmapred.child.java.opts="-Djava.security.egd=file:/dev/../dev/urandom" 
-Dtest.timeout=100 -Dtestcase=Oracle*Test


Thanks,

Anna Szonyi

[jira] [Commented] (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"

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705624#comment-15705624
 ] 

Hudson commented on SQOOP-3055:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop23 #1274 (See 
[https://builds.apache.org/job/Sqoop-hadoop23/1274/])
SQOOP-3055: Fixing MySQL tests failing due to ignored test (maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=48cecdc99e45514adff5b9ea8112f5fb366aee14])
* (edit) src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java
* (edit) src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java
* (edit) src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java
* (edit) 
src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java
* (edit) build.xml
* (edit) src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java


> 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] [Commented] (SQOOP-3056) Add ant ivy report target

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705623#comment-15705623
 ] 

Hudson commented on SQOOP-3056:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop23 #1274 (See 
[https://builds.apache.org/job/Sqoop-hadoop23/1274/])
SQOOP-3056: Add ant ivy report target (maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=f9d76fd4a3558d6a1b03b52c9a8b1b2a703d6e50])
* (edit) build.xml


> 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] [Commented] (SQOOP-3056) Add ant ivy report target

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705610#comment-15705610
 ] 

Hudson commented on SQOOP-3056:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop20 #1072 (See 
[https://builds.apache.org/job/Sqoop-hadoop20/1072/])
SQOOP-3056: Add ant ivy report target (maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=f9d76fd4a3558d6a1b03b52c9a8b1b2a703d6e50])
* (edit) build.xml


> 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] [Commented] (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"

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705611#comment-15705611
 ] 

Hudson commented on SQOOP-3055:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop20 #1072 (See 
[https://builds.apache.org/job/Sqoop-hadoop20/1072/])
SQOOP-3055: Fixing MySQL tests failing due to ignored test (maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=48cecdc99e45514adff5b9ea8112f5fb366aee14])
* (edit) src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java
* (edit) src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java
* (edit) build.xml
* (edit) src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java
* (edit) src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java
* (edit) 
src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java


> 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] [Commented] (SQOOP-3056) Add ant ivy report target

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705565#comment-15705565
 ] 

Hudson commented on SQOOP-3056:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop200 #1078 (See 
[https://builds.apache.org/job/Sqoop-hadoop200/1078/])
SQOOP-3056: Add ant ivy report target (maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=f9d76fd4a3558d6a1b03b52c9a8b1b2a703d6e50])
* (edit) build.xml


> 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] [Commented] (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"

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705566#comment-15705566
 ] 

Hudson commented on SQOOP-3055:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop200 #1078 (See 
[https://builds.apache.org/job/Sqoop-hadoop200/1078/])
SQOOP-3055: Fixing MySQL tests failing due to ignored test (maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=48cecdc99e45514adff5b9ea8112f5fb366aee14])
* (edit) src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java
* (edit) src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java
* (edit) src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java
* (edit) build.xml
* (edit) src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java
* (edit) 
src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java


> 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)

Re: Review Request 54030: SQOOP-3055 MySQL tests are failing due to the tests ignoring specified username, password and dbname, trying to connect to specified db using "currentUser"

[Szabolcs Vasas]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54030/#review157251
---




src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java (line 22)


I think it would be better to use org.apache.commons.lang.StringUtils for 
example, jodd.util seems to be a weird package for me.


Hi Anna,
Thank you for fixing the test cases, I have just minor comment to your patch.

- Szabolcs Vasas


On Nov. 29, 2016, 12:44 p.m., Anna Szonyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54030/
> ---
> 
> (Updated Nov. 29, 2016, 12:44 p.m.)
> 
> 
> Review request for Sqoop, Attila Szabo and Szabolcs Vasas.
> 
> 
> Bugs: SQOOP-3055
> https://issues.apache.org/jira/browse/SQOOP-3055
> 
> 
> Repository: sqoop-trunk
> 
> 
> Description
> ---
> 
> SQOOP-3055 MySQL tests are ignoring specified username, password and dbname, 
> trying to connect to specified db using currentuser (using 
> System.getEnv("USER") or whoami). You should now be able to specify the user 
> (and will have to when running Mysql tests), password, hostname and database 
> name for the MSQL tests (and they won't ignore it and use current users 
> anymore).
> 
> 
> Diffs
> -
> 
>   build.xml 6e8d393 
>   src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java 79e90e2 
>   src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java d0f0c50 
>   src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java 86b9aab 
>   src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java bad3c29 
>   src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java 675b6b8 
>   src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java 935d948 
>   src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java df78142 
>   src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java 0af79d6 
>   src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java 6bf939b 
>   src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java 
> 87cd389 
> 
> Diff: https://reviews.apache.org/r/54030/diff/
> 
> 
> Testing
> ---
> 
> Ran all MySQL tests with hadoopversion 260 and hbaseprofile 95: ant test 
> -Dhadoopversion=260 -Dhbaseprofile=95 -Dthirdparty=true 
> -Dsqoop.thirdparty.lib.dir=3rdpartylibdir 
> -Dsqoop.test.mysql.connectstring.host_url=mysqlhost 
> -Dsqoop.test.mysql.databasename=sqoop_repo -Dsqoop.test.mysql.password=sqoop 
> -Dsqoop.test.mysql.username=sqoop
> 
> 
> Thanks,
> 
> Anna Szonyi
> 
>

[jira] [Commented] (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"

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705524#comment-15705524
 ] 

Hudson commented on SQOOP-3055:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop100 #1037 (See 
[https://builds.apache.org/job/Sqoop-hadoop100/1037/])
SQOOP-3055: Fixing MySQL tests failing due to ignored test (maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=48cecdc99e45514adff5b9ea8112f5fb366aee14])
* (edit) src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java
* (edit) src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java
* (edit) 
src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java
* (edit) src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java
* (edit) src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java
* (edit) src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java
* (edit) build.xml


> 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] [Commented] (SQOOP-3056) Add ant ivy report target

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705523#comment-15705523
 ] 

Hudson commented on SQOOP-3056:
---

FAILURE: Integrated in Jenkins build Sqoop-hadoop100 #1037 (See 
[https://builds.apache.org/job/Sqoop-hadoop100/1037/])
SQOOP-3056: Add ant ivy report target (maugli: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=f9d76fd4a3558d6a1b03b52c9a8b1b2a703d6e50])
* (edit) build.xml


> 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] [Commented] (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"

[Attila Szabo (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705472#comment-15705472
 ] 

Attila Szabo commented on SQOOP-3055:
-

Hi [~szonyi],

Thanks for your contribution! It's very important that all of our test cases 
receive the right configuration/settings.

Thanks,
[~maugli]


> 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] [Commented] (SQOOP-3056) Add ant ivy report target

[Attila Szabo (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705465#comment-15705465
 ] 

Attila Szabo commented on SQOOP-3056:
-

Hi [~szonyi],

Thanks for your contribution here! It's a very nice convenience feature for the 
ant build.

Thanks,
[~maugli]

> 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] [Commented] (SQOOP-3056) Add ant ivy report target

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705460#comment-15705460
 ] 

ASF subversion and git services commented on SQOOP-3056:


Commit f9d76fd4a3558d6a1b03b52c9a8b1b2a703d6e50 in sqoop's branch 
refs/heads/trunk from [~maugli]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=f9d76fd ]

SQOOP-3056: Add ant ivy report target

(Anna Szonyi via Attila Szabo)


> 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] [Commented] (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"

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SQOOP-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705459#comment-15705459
 ] 

ASF subversion and git services commented on SQOOP-3055:


Commit 48cecdc99e45514adff5b9ea8112f5fb366aee14 in sqoop's branch 
refs/heads/trunk from [~maugli]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=48cecdc ]

SQOOP-3055: Fixing MySQL tests failing due to
ignored test inputs/configuration

(Anna Szonyi via Attila Szabo)


> 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)

Re: Review Request 54156: SQOOP-3056 Add report ivy report target to build

[Erzsebet Szilagyi]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54156/#review157248
---


Ship it!




Thank you for this useful feature!

- Erzsebet Szilagyi


On Nov. 29, 2016, 1:35 p.m., Anna Szonyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54156/
> ---
> 
> (Updated Nov. 29, 2016, 1:35 p.m.)
> 
> 
> Review request for Sqoop, Attila Szabo and Szabolcs Vasas.
> 
> 
> Bugs: SQOOP-3056
> https://issues.apache.org/jira/browse/SQOOP-3056
> 
> 
> Repository: sqoop-trunk
> 
> 
> Description
> ---
> 
> Add report ivy report target to ant, as it's difficult to tell where 
> dependencies come from - you should be able to generate an html and graph 
> report to figure out where the transitive dependencies come from.
> 
> 
> Diffs
> -
> 
>   build.xml 6e8d393 
> 
> Diff: https://reviews.apache.org/r/54156/diff/
> 
> 
> Testing
> ---
> 
> ran ant report and checked the output html & graph (with yEd), ran ant clean 
> test, ant compile
> 
> 
> Thanks,
> 
> Anna Szonyi
> 
>

Re: Review Request 54156: SQOOP-3056 Add report ivy report target to build

[Attila Szabo]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54156/#review157250
---


Ship it!




Ship It!

- Attila Szabo


On Nov. 29, 2016, 12:35 p.m., Anna Szonyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54156/
> ---
> 
> (Updated Nov. 29, 2016, 12:35 p.m.)
> 
> 
> Review request for Sqoop, Attila Szabo and Szabolcs Vasas.
> 
> 
> Bugs: SQOOP-3056
> https://issues.apache.org/jira/browse/SQOOP-3056
> 
> 
> Repository: sqoop-trunk
> 
> 
> Description
> ---
> 
> Add report ivy report target to ant, as it's difficult to tell where 
> dependencies come from - you should be able to generate an html and graph 
> report to figure out where the transitive dependencies come from.
> 
> 
> Diffs
> -
> 
>   build.xml 6e8d393 
> 
> Diff: https://reviews.apache.org/r/54156/diff/
> 
> 
> Testing
> ---
> 
> ran ant report and checked the output html & graph (with yEd), ran ant clean 
> test, ant compile
> 
> 
> Thanks,
> 
> Anna Szonyi
> 
>

Re: Review Request 54156: SQOOP-3056 Add report ivy report target to build

[Szabolcs Vasas]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54156/#review157247
---


Ship it!




Hi Anna,

Thank you for this small useful feature and the tip to use yEd for exploring 
the dependency graph, it is very useful!

- Szabolcs Vasas


On Nov. 29, 2016, 12:35 p.m., Anna Szonyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54156/
> ---
> 
> (Updated Nov. 29, 2016, 12:35 p.m.)
> 
> 
> Review request for Sqoop, Attila Szabo and Szabolcs Vasas.
> 
> 
> Bugs: SQOOP-3056
> https://issues.apache.org/jira/browse/SQOOP-3056
> 
> 
> Repository: sqoop-trunk
> 
> 
> Description
> ---
> 
> Add report ivy report target to ant, as it's difficult to tell where 
> dependencies come from - you should be able to generate an html and graph 
> report to figure out where the transitive dependencies come from.
> 
> 
> Diffs
> -
> 
>   build.xml 6e8d393 
> 
> Diff: https://reviews.apache.org/r/54156/diff/
> 
> 
> Testing
> ---
> 
> ran ant report and checked the output html & graph (with yEd), ran ant clean 
> test, ant compile
> 
> 
> Thanks,
> 
> Anna Szonyi
> 
>

Re: Review Request 54030: SQOOP-3055 MySQL tests are failing due to the tests ignoring specified username, password and dbname, trying to connect to specified db using "currentUser"

[Anna Szonyi]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54030/
---

(Updated Nov. 29, 2016, 12:44 p.m.)


Review request for Sqoop, Attila Szabo and Szabolcs Vasas.


Changes
---

review: fix 5 missing spaces issue


Bugs: SQOOP-3055
https://issues.apache.org/jira/browse/SQOOP-3055


Repository: sqoop-trunk


Description
---

SQOOP-3055 MySQL tests are ignoring specified username, password and dbname, 
trying to connect to specified db using currentuser (using 
System.getEnv("USER") or whoami). You should now be able to specify the user 
(and will have to when running Mysql tests), password, hostname and database 
name for the MSQL tests (and they won't ignore it and use current users 
anymore).


Diffs (updated)
-

  build.xml 6e8d393 
  src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java 79e90e2 
  src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java d0f0c50 
  src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java 86b9aab 
  src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java bad3c29 
  src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java 675b6b8 
  src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java 935d948 
  src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java df78142 
  src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java 0af79d6 
  src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java 6bf939b 
  src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java 
87cd389 

Diff: https://reviews.apache.org/r/54030/diff/


Testing
---

Ran all MySQL tests with hadoopversion 260 and hbaseprofile 95: ant test 
-Dhadoopversion=260 -Dhbaseprofile=95 -Dthirdparty=true 
-Dsqoop.thirdparty.lib.dir=3rdpartylibdir 
-Dsqoop.test.mysql.connectstring.host_url=mysqlhost 
-Dsqoop.test.mysql.databasename=sqoop_repo -Dsqoop.test.mysql.password=sqoop 
-Dsqoop.test.mysql.username=sqoop


Thanks,

Anna Szonyi

Review Request 54156: SQOOP-3056 Add report ivy report target to build

[Anna Szonyi]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54156/
---

Review request for Sqoop, Attila Szabo and Szabolcs Vasas.


Bugs: SQOOP-3056
https://issues.apache.org/jira/browse/SQOOP-3056


Repository: sqoop-trunk


Description
---

Add report ivy report target to ant, as it's difficult to tell where 
dependencies come from - you should be able to generate an html and graph 
report to figure out where the transitive dependencies come from.


Diffs
-

  build.xml 6e8d393 

Diff: https://reviews.apache.org/r/54156/diff/


Testing
---

ran ant report and checked the output html & graph (with yEd), ran ant clean 
test, ant compile


Thanks,

Anna Szonyi

Re: Review Request 54030: SQOOP-3055 MySQL tests are failing due to the tests ignoring specified username, password and dbname, trying to connect to specified db using "currentUser"

[Attila Szabo]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54030/#review157228
---


Fix it, then Ship it!





src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java (line 10)


Please also add back the five missing spaces please!

We don't need any changes on this line.

Thanks!


- Attila Szabo


On Nov. 29, 2016, 11:22 a.m., Anna Szonyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54030/
> ---
> 
> (Updated Nov. 29, 2016, 11:22 a.m.)
> 
> 
> Review request for Sqoop and Attila Szabo.
> 
> 
> Bugs: SQOOP-3055
> https://issues.apache.org/jira/browse/SQOOP-3055
> 
> 
> Repository: sqoop-trunk
> 
> 
> Description
> ---
> 
> SQOOP-3055 MySQL tests are ignoring specified username, password and dbname, 
> trying to connect to specified db using currentuser (using 
> System.getEnv("USER") or whoami). You should now be able to specify the user 
> (and will have to when running Mysql tests), password, hostname and database 
> name for the MSQL tests (and they won't ignore it and use current users 
> anymore).
> 
> 
> Diffs
> -
> 
>   build.xml 6e8d393 
>   src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java 79e90e2 
>   src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java d0f0c50 
>   src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java 86b9aab 
>   src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java bad3c29 
>   src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java 675b6b8 
>   src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java 935d948 
>   src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java df78142 
>   src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java 0af79d6 
>   src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java 6bf939b 
>   src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java 
> 87cd389 
> 
> Diff: https://reviews.apache.org/r/54030/diff/
> 
> 
> Testing
> ---
> 
> Ran all MySQL tests with hadoopversion 260 and hbaseprofile 95: ant test 
> -Dhadoopversion=260 -Dhbaseprofile=95 -Dthirdparty=true 
> -Dsqoop.thirdparty.lib.dir=3rdpartylibdir 
> -Dsqoop.test.mysql.connectstring.host_url=mysqlhost 
> -Dsqoop.test.mysql.databasename=sqoop_repo -Dsqoop.test.mysql.password=sqoop 
> -Dsqoop.test.mysql.username=sqoop
> 
> 
> Thanks,
> 
> Anna Szonyi
> 
>

[jira] [Updated] (SQOOP-3056) Add ant ivy report target

[Anna Szonyi (JIRA)]

 [ 
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"

[Anna Szonyi (JIRA)]

 [ 
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)

Re: Review Request 54030: SQOOP-3055 MySQL tests are failing due to the tests ignoring specified username, password and dbname, trying to connect to specified db using "currentUser"

[Anna Szonyi]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54030/
---

(Updated Nov. 29, 2016, 11:22 a.m.)


Review request for Sqoop and Attila Szabo.


Changes
---

Removed  from Licence header


Bugs: SQOOP-3055
https://issues.apache.org/jira/browse/SQOOP-3055


Repository: sqoop-trunk


Description
---

SQOOP-3055 MySQL tests are ignoring specified username, password and dbname, 
trying to connect to specified db using currentuser (using 
System.getEnv("USER") or whoami). You should now be able to specify the user 
(and will have to when running Mysql tests), password, hostname and database 
name for the MSQL tests (and they won't ignore it and use current users 
anymore).


Diffs (updated)
-

  build.xml 6e8d393 
  src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java 79e90e2 
  src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java d0f0c50 
  src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java 86b9aab 
  src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java bad3c29 
  src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java 675b6b8 
  src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java 935d948 
  src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java df78142 
  src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java 0af79d6 
  src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java 6bf939b 
  src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java 
87cd389 

Diff: https://reviews.apache.org/r/54030/diff/


Testing
---

Ran all MySQL tests with hadoopversion 260 and hbaseprofile 95: ant test 
-Dhadoopversion=260 -Dhbaseprofile=95 -Dthirdparty=true 
-Dsqoop.thirdparty.lib.dir=3rdpartylibdir 
-Dsqoop.test.mysql.connectstring.host_url=mysqlhost 
-Dsqoop.test.mysql.databasename=sqoop_repo -Dsqoop.test.mysql.password=sqoop 
-Dsqoop.test.mysql.username=sqoop


Thanks,

Anna Szonyi

Re: Review Request 54030: SQOOP-3055 MySQL tests are failing due to the tests ignoring specified username, password and dbname, trying to connect to specified db using "currentUser"

[Attila Szabo]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54030/#review157220
---


Fix it, then Ship it!





src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java (lines 9 - 11)


Could we please remove this, and stick to the standard formatting of the 
Apache License header?


Hi Anna,

The changes looks goood. I've only found one tiny problem around a license 
header? Could you please fix that?

Otherwise it looks good!

- Attila Szabo


On Nov. 25, 2016, 11:02 a.m., Anna Szonyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54030/
> ---
> 
> (Updated Nov. 25, 2016, 11:02 a.m.)
> 
> 
> Review request for Sqoop and Attila Szabo.
> 
> 
> Bugs: SQOOP-3055
> https://issues.apache.org/jira/browse/SQOOP-3055
> 
> 
> Repository: sqoop-trunk
> 
> 
> Description
> ---
> 
> SQOOP-3055 MySQL tests are ignoring specified username, password and dbname, 
> trying to connect to specified db using currentuser (using 
> System.getEnv("USER") or whoami). You should now be able to specify the user 
> (and will have to when running Mysql tests), password, hostname and database 
> name for the MSQL tests (and they won't ignore it and use current users 
> anymore).
> 
> 
> Diffs
> -
> 
>   build.xml 6e8d393 
>   src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java 79e90e2 
>   src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java d0f0c50 
>   src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java 86b9aab 
>   src/test/com/cloudera/sqoop/manager/MySQLAllTablesTest.java bad3c29 
>   src/test/com/cloudera/sqoop/manager/MySQLCompatTest.java 675b6b8 
>   src/test/com/cloudera/sqoop/manager/MySQLFreeFormQueryTest.java 935d948 
>   src/test/com/cloudera/sqoop/manager/MySQLLobAvroImportTest.java df78142 
>   src/test/com/cloudera/sqoop/manager/MySQLTestUtils.java 0af79d6 
>   src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java 6bf939b 
>   src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java 
> 87cd389 
> 
> Diff: https://reviews.apache.org/r/54030/diff/
> 
> 
> Testing
> ---
> 
> Ran all MySQL tests with hadoopversion 260 and hbaseprofile 95: ant test 
> -Dhadoopversion=260 -Dhbaseprofile=95 -Dthirdparty=true 
> -Dsqoop.thirdparty.lib.dir=3rdpartylibdir 
> -Dsqoop.test.mysql.connectstring.host_url=mysqlhost 
> -Dsqoop.test.mysql.databasename=sqoop_repo -Dsqoop.test.mysql.password=sqoop 
> -Dsqoop.test.mysql.username=sqoop
> 
> 
> Thanks,
> 
> Anna Szonyi
> 
>

[jira] [Created] (SQOOP-3064) Custom Query with Order by Clause is not working with microsoft sql connector

[Senthil Ganesh (JIRA)]

Senthil Ganesh created SQOOP-3064:
-

 Summary: Custom Query with Order by Clause is not working with 
microsoft sql connector
 Key: SQOOP-3064
 URL: https://issues.apache.org/jira/browse/SQOOP-3064
 Project: Sqoop
  Issue Type: Bug
Reporter: Senthil Ganesh


016-10-17 12:43:57  INFO: [APPSDK_Msg_1762] 
BoundingValsQuery: SELECT MIN(EMPNO), MAX(EMPNO) FROM (SELECT DISTINCT 
"dbo"."EMP_TGT"."EMPNO","dbo"."EMP_TGT"."ENAME","dbo"."EMP_TGT"."JOB","dbo"."EMP_TGT"."MGR","dbo"."EMP_TGT"."HIREDATE","dbo"."EMP_TGT"."SAL","dbo"."EMP_TGT"."COMM","dbo"."EMP_TGT"."DEPTNO"
 FROM "dbo"."EMP_TGT" where (1 = 1) ORDER BY "dbo"."EMP_TGT"."ENAME" ASC) AS t1
2016-10-17 12:43:57  INFO: [APPSDK_Msg_1762] 
Cleaning up the staging area 
/tmp/hadoop-yarn/staging/adpqa/.staging/job_1474990333046_0695
2016-10-17 12:43:57  INFO: [APPSDK_Msg_1762] 
PriviledgedActionException as:adpqa (auth:PROXY) via adpqa (auth:KERBEROS) 
cause:java.io.IOException: com.microsoft.sqlserver.jdbc.SQLServerException: The 
ORDER BY clause is invalid in views, inline functions, derived tables, 
subqueries, and common table expressions, unless TOP, OFFSET or FOR XML is also 
specified.
2016-10-17 12:43:57  INFO: [APPSDK_Msg_1762] 
Encountered IOException running import job: java.io.IOException: 
com.microsoft.sqlserver.jdbc.SQLServerException: The ORDER BY clause is invalid 
in views, inline functions, derived tables, subqueries, and common table 
expressions, unless TOP, OFFSET or FOR XML is also specified.
2016-10-17 12:43:57  INFO: [APPSDK_Msg_1762] at 
org.apache.sqoop.mapreduce.db.DataDrivenDBInputFormat.getSplits(DataDrivenDBInputFormat.java:203)
2016-10-17 12:43:57  INFO: [APPSDK_Msg_1762] at 
org.apache.hadoop.mapreduce.JobSubmitter.writeNewSplits(JobSubmitter.java:305)
2016-10-17 12:43:57  INFO: [APPSDK_Msg_1762] at 


Thanks & Regards,
Rohith



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SQOOP-3063) CDH 5U8- TDCH FLOAT value 2.26e-308 is not working

[Senthil Ganesh (JIRA)]

Senthil Ganesh created SQOOP-3063:
-

 Summary: CDH 5U8- TDCH FLOAT value 2.26e-308 is not working
 Key: SQOOP-3063
 URL: https://issues.apache.org/jira/browse/SQOOP-3063
 Project: Sqoop
  Issue Type: Bug
Reporter: Senthil Ganesh


sqoop import --password ** --map-column-java 
col1_byteint=Integer,col2_smallint=Integer,col3_integer=Integer,col6_float=Double,col9_char=String,col10_varchar=String,col11_char_cs=String,col12_varchar_cs=String,col16_bigint=Long,col_key=Integer
 --connect jdbc:teradata://10.65.43.30/database=dwtera,charset=UTF8 --username 
dwtera --driver com.teradata.jdbc.TeraDriver --as-avrodatafile --split-by 
col_key --where 
0.000226
 = TD_all_dtype_sqoop_src.col6_float --columns 
col1_byteint,col2_smallint,col3_integer,col4_decimal,col5_dec_no_length,col6_float,col9_char,col10_varchar,col11_char_cs,col12_varchar_cs,col13_date,col14_time,col15_timestamp,col16_bigint,col_key
 --compress --table TD_all_dtype_sqoop_src --target-dir 
hdfs://ivlhdp258.informatica.com:8020/blaze/workdir/29619794428028430/W29619794428028430_Read_TD_all_dtype_sqoop_src_sqoop_m_07_all_dtyp_td_flter_td_no_byte_varbyte1/staged_files


016-09-17 11:11:17  INFO: [APPSDK_Msg_1762] 
SQOOP_HOME is unset. May not be able to find all job dependencies.
2016-09-17 11:11:17  INFO: [APPSDK_Msg_1762] 
Connecting to ResourceManager at ivlhdp258.informatica.com/10.65.147.72:8032
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762] 
Using read commited transaction isolation
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762] 
BoundingValsQuery: SELECT MIN(col_key), MAX(col_key) FROM 
TD_all_dtype_sqoop_src WHERE ( 
0.000226
 = TD_all_dtype_sqoop_src.col6_float )
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762] 
Cleaning up the staging area 
/tmp/hadoop-yarn/staging/qamercury/.staging/job_1473759670660_0183
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762] 
PriviledgedActionException as:qamercury (auth:PROXY) via yarn (auth:SIMPLE) 
cause:java.io.IOException: java.sql.SQLException: [Teradata Database] [TeraJDBC 
15.10.00.09] [Error 3753] [SQLState 22003] Too many digits in integer or 
decimal constant.
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762] 
Encountered IOException running import job: java.io.IOException: 
java.sql.SQLException: [Teradata Database] [TeraJDBC 15.10.00.09] [Error 3753] 
[SQLState 22003] Too many digits in integer or decimal constant.
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762]  
at 
org.apache.sqoop.mapreduce.db.DataDrivenDBInputFormat.getSplits(DataDrivenDBInputFormat.java:203)
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762]  
at 
org.apache.hadoop.mapreduce.JobSubmitter.writeNewSplits(JobSubmitter.java:305)
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762]  
at org.apache.hadoop.mapreduce.JobSubmitter.writeSplits(JobSubmitter.java:322)
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762]  
at 
org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:200)
2016-09-17 11:11:20  INFO: [APPSDK_Msg_1762]  
at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1307)


Thanks & Regards,
Rohith



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)