[jira] [Commented] (SQOOP-2933) Sqoop2: Ensure that the buffered writer is always closed in the RepositoryDumpTool

2016-05-25 Thread Sqoop QA bot (JIRA) 

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

Sqoop QA bot commented on SQOOP-2933:
-

Testing file 
[SQOOP-2933.patch|https://issues.apache.org/jira/secure/attachment/12806246/SQOOP-2933.patch]
 against branch sqoop2 took 1:25:26.733862.

{color:red}Overall:{color} -1 due to an error(s), see details below:

{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:red}ERROR:{color} Patch does not add/modify any test case
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All unit tests passed (executed 1760 tests)
{color:green}SUCCESS:{color} Test coverage did not decreased 
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/2378/artifact/patch-process/cobertura_report.txt])
{color:green}SUCCESS:{color} No new findbugs warnings 
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/2378/artifact/patch-process/findbugs_report.txt])
{color:green}SUCCESS:{color} All integration tests passed (executed 231 tests)

Console output is available 
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/2378/console].

This message is automatically generated.

> Sqoop2: Ensure that the buffered writer is always closed in the 
> RepositoryDumpTool
> --
>
> Key: SQOOP-2933
> URL: https://issues.apache.org/jira/browse/SQOOP-2933
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Attachments: SQOOP-2933.patch
>
>
> We may not properly close the bufferedwriter if an exception is thrown before 
> close, we should use a try-with-resources to fix that



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

[jira] [Created] (SQOOP-2935) Support complex types with HCatatog integration

2016-05-25 Thread Venkat Ranganathan (JIRA) 
Venkat Ranganathan created SQOOP-2935:
-

 Summary: Support complex types with HCatatog integration
 Key: SQOOP-2935
 URL: https://issues.apache.org/jira/browse/SQOOP-2935
 Project: Sqoop
  Issue Type: Bug
  Components: hive-integration
Affects Versions: 1.4.6
Reporter: Venkat Ranganathan
Assignee: Venkat Ranganathan


Currently we support only primitive types with HCatalog integration.   We 
should support complex datatypes also.   The first step is to treat them as 
JSON serialized strings during import and export and convert them as needed.



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

Re: Sqoop 1.99.7

2016-05-25 Thread Jarek Jarcec Cecho 
There doesn’t seems to be any objections, so let’s do the release. Thanks for 
volunteering to be the release manager Abe!

I’m happy to be a release mentor since this will be your first release if that 
is fine with you.

Jarcec

> On May 20, 2016, at 10:37 AM, Abraham Fine  wrote:
> 
> I would be open to driving the release.
> 
> Abe
> 
>> On May 20, 2016, at 08:20, Abraham Elmahrek  wrote:
>> 
>> +1 for a new release.
>> 
>> On Fri, May 20, 2016 at 7:08 AM Jarek Jarcec Cecho 
>> wrote:
>> 
>>> Any volunteers to drive that release? :)
>>> 
>>> Jarcec
>>> 
 On May 18, 2016, at 1:49 PM, Abraham Fine  wrote:
 
 I agree.
 
 
> On May 18, 2016, at 11:24, Jarek Jarcec Cecho 
>>> wrote:
> 
> +dev@sqoop
> 
> I see plenty of new features available in the head of sqoop2 branch, so
>>> perhaps it would make sense to do a release?
> 
> Jarcec
> 
>> On May 10, 2016, at 12:33 AM, ssvinarc...@cybervisiontech.com wrote:
>> 
>> Hi all,
>> 
>> Could somebody say when will be released Sqoop 1.99.7?
>> 
>> Thanks,
>> Sergey!
> 
 
>>> 
>>> 
>

Re: Review Request 47860: SQOOP-2933: Sqoop2: Ensure that the buffered writer is always closed in the RepositoryDumpTool

2016-05-25 Thread Boglarka Egyed 

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


Ship it!




Ship It!

- Boglarka Egyed


On May 25, 2016, 10:41 p.m., Abraham Fine wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47860/
> ---
> 
> (Updated May 25, 2016, 10:41 p.m.)
> 
> 
> Review request for Sqoop.
> 
> 
> Bugs: SQOOP-2933
> https://issues.apache.org/jira/browse/SQOOP-2933
> 
> 
> Repository: sqoop-sqoop2
> 
> 
> Description
> ---
> 
> Sqoop2: Ensure that the buffered writer is always closed in the 
> RepositoryDumpTool
> 
> 
> Diffs
> -
> 
>   tools/src/main/java/org/apache/sqoop/tools/tool/RepositoryDumpTool.java 
> e0d1173 
> 
> Diff: https://reviews.apache.org/r/47860/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Abraham Fine
> 
>

Re: Review Request 47859: SQOOP-2934: Sqoop2: ConfigInputSerialization should properly handle an unknown input type when restoring configuration

2016-05-25 Thread Boglarka Egyed 

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


Ship it!




Ship It!

- Boglarka Egyed


On May 25, 2016, 10:32 p.m., Abraham Fine wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47859/
> ---
> 
> (Updated May 25, 2016, 10:32 p.m.)
> 
> 
> Review request for Sqoop.
> 
> 
> Bugs: SQOOP-2934
> https://issues.apache.org/jira/browse/SQOOP-2934
> 
> 
> Repository: sqoop-sqoop2
> 
> 
> Description
> ---
> 
> Sqoop2: ConfigInputSerialization should properly handle an unknown input type 
> when restoring configuration
> 
> 
> Diffs
> -
> 
>   
> common/src/main/java/org/apache/sqoop/json/util/ConfigInputSerialization.java 
> 71527ff 
>   common/src/main/java/org/apache/sqoop/json/util/SerializationError.java 
> 8479db1 
> 
> Diff: https://reviews.apache.org/r/47859/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Abraham Fine
> 
>

[jira] [Updated] (SQOOP-2933) Sqoop2: Ensure that the buffered writer is always closed in the RepositoryDumpTool

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine updated SQOOP-2933:

Attachment: SQOOP-2933.patch

> Sqoop2: Ensure that the buffered writer is always closed in the 
> RepositoryDumpTool
> --
>
> Key: SQOOP-2933
> URL: https://issues.apache.org/jira/browse/SQOOP-2933
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Attachments: SQOOP-2933.patch
>
>
> We may not properly close the bufferedwriter if an exception is thrown before 
> close, we should use a try-with-resources to fix that



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

[jira] [Assigned] (SQOOP-2933) Sqoop2: Ensure that the buffered writer is always closed in the RepositoryDumpTool

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine reassigned SQOOP-2933:
---

Assignee: Abraham Fine

> Sqoop2: Ensure that the buffered writer is always closed in the 
> RepositoryDumpTool
> --
>
> Key: SQOOP-2933
> URL: https://issues.apache.org/jira/browse/SQOOP-2933
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> We may not properly close the bufferedwriter if there is a crash, we should 
> use a try-with-resources to fix that



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

Review Request 47860: SQOOP-2933: Sqoop2: Ensure that the buffered writer is always closed in the RepositoryDumpTool

2016-05-25 Thread Abraham Fine 

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

Review request for Sqoop.


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


Repository: sqoop-sqoop2


Description
---

Sqoop2: Ensure that the buffered writer is always closed in the 
RepositoryDumpTool


Diffs
-

  tools/src/main/java/org/apache/sqoop/tools/tool/RepositoryDumpTool.java 
e0d1173 

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


Testing
---


Thanks,

Abraham Fine

[jira] [Updated] (SQOOP-2933) Sqoop2: Ensure that the buffered writer is always closed in the RepositoryDumpTool

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine updated SQOOP-2933:

Description: We may not properly close the bufferedwriter if an exception 
is thrown before close, we should use a try-with-resources to fix that  (was: 
We may not properly close the bufferedwriter if there is a crash, we should use 
a try-with-resources to fix that)

> Sqoop2: Ensure that the buffered writer is always closed in the 
> RepositoryDumpTool
> --
>
> Key: SQOOP-2933
> URL: https://issues.apache.org/jira/browse/SQOOP-2933
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Attachments: SQOOP-2933.patch
>
>
> We may not properly close the bufferedwriter if an exception is thrown before 
> close, we should use a try-with-resources to fix that



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

[jira] [Updated] (SQOOP-2934) Sqoop2: ConfigInputSerialization should properly handle an unknown input type when restoring configuration

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine updated SQOOP-2934:

Attachment: SQOOP-2934.patch

> Sqoop2: ConfigInputSerialization should properly handle an unknown input type 
> when restoring configuration
> --
>
> Key: SQOOP-2934
> URL: https://issues.apache.org/jira/browse/SQOOP-2934
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
> Attachments: SQOOP-2934.patch
>
>
> Our current code would throw a null pointer exception, we should throw a 
> meaningful exception



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

Review Request 47859: SQOOP-2934: Sqoop2: ConfigInputSerialization should properly handle an unknown input type when restoring configuration

2016-05-25 Thread Abraham Fine 

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

Review request for Sqoop.


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


Repository: sqoop-sqoop2


Description
---

Sqoop2: ConfigInputSerialization should properly handle an unknown input type 
when restoring configuration


Diffs
-

  common/src/main/java/org/apache/sqoop/json/util/ConfigInputSerialization.java 
71527ff 
  common/src/main/java/org/apache/sqoop/json/util/SerializationError.java 
8479db1 

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


Testing
---


Thanks,

Abraham Fine

[jira] [Assigned] (SQOOP-2934) Sqoop2: ConfigInputSerialization should properly handle an unknown input type when restoring configuration

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine reassigned SQOOP-2934:
---

Assignee: Abraham Fine

> Sqoop2: ConfigInputSerialization should properly handle an unknown input type 
> when restoring configuration
> --
>
> Key: SQOOP-2934
> URL: https://issues.apache.org/jira/browse/SQOOP-2934
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Attachments: SQOOP-2934.patch
>
>
> Our current code would throw a null pointer exception, we should throw a 
> meaningful exception



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

[jira] [Updated] (SQOOP-2934) Sqoop2: ConfigInputSerialization should properly handle an unknown input type when restoring configuration

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine updated SQOOP-2934:

Affects Version/s: 1.99.6

> Sqoop2: ConfigInputSerialization should properly handle an unknown input type 
> when restoring configuration
> --
>
> Key: SQOOP-2934
> URL: https://issues.apache.org/jira/browse/SQOOP-2934
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>
> Our current code would throw a null pointer exception, we should throw a 
> meaningful exception



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

[jira] [Updated] (SQOOP-2933) Sqoop2: Ensure that the buffered writer is always closed in the RepositoryDumpTool

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine updated SQOOP-2933:

Affects Version/s: 1.99.6

> Sqoop2: Ensure that the buffered writer is always closed in the 
> RepositoryDumpTool
> --
>
> Key: SQOOP-2933
> URL: https://issues.apache.org/jira/browse/SQOOP-2933
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>
> We may not properly close the bufferedwriter if there is a crash, we should 
> use a try-with-resources to fix that



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

[jira] [Created] (SQOOP-2934) Sqoop2: ConfigInputSerialization should properly handle an unknown input type when restoring configuration

2016-05-25 Thread Abraham Fine (JIRA) 
Abraham Fine created SQOOP-2934:
---

 Summary: Sqoop2: ConfigInputSerialization should properly handle 
an unknown input type when restoring configuration
 Key: SQOOP-2934
 URL: https://issues.apache.org/jira/browse/SQOOP-2934
 Project: Sqoop
  Issue Type: Bug
Reporter: Abraham Fine


Our current code would throw a null pointer exception, we should throw a 
meaningful exception



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

[jira] [Updated] (SQOOP-2932) Sqoop2: Avro support for HdfsConnector

2016-05-25 Thread Szabolcs Vasas (JIRA) 

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

Szabolcs Vasas updated SQOOP-2932:
--
Description: 
We should be able to read and write Avro files using the HdfsConnector.


  was:we should be able to read and write parquet files from the hdfsconnector.


> Sqoop2: Avro support for HdfsConnector
> --
>
> Key: SQOOP-2932
> URL: https://issues.apache.org/jira/browse/SQOOP-2932
> Project: Sqoop
>  Issue Type: New Feature
>Affects Versions: 1.99.6
>Reporter: Szabolcs Vasas
>Assignee: Abraham Fine
> Fix For: 1.99.7
>
>
> We should be able to read and write Avro files using the HdfsConnector.



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

[jira] [Assigned] (SQOOP-2932) Sqoop2: Avro support for HdfsConnector

2016-05-25 Thread Szabolcs Vasas (JIRA) 

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

Szabolcs Vasas reassigned SQOOP-2932:
-

Assignee: Szabolcs Vasas  (was: Abraham Fine)

> Sqoop2: Avro support for HdfsConnector
> --
>
> Key: SQOOP-2932
> URL: https://issues.apache.org/jira/browse/SQOOP-2932
> Project: Sqoop
>  Issue Type: New Feature
>Affects Versions: 1.99.6
>Reporter: Szabolcs Vasas
>Assignee: Szabolcs Vasas
> Fix For: 1.99.7
>
>
> We should be able to read and write Avro files using the HdfsConnector.



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

[jira] [Created] (SQOOP-2932) Sqoop2: Avro support for HdfsConnector

2016-05-25 Thread Szabolcs Vasas (JIRA) 
Szabolcs Vasas created SQOOP-2932:
-

 Summary: Sqoop2: Avro support for HdfsConnector
 Key: SQOOP-2932
 URL: https://issues.apache.org/jira/browse/SQOOP-2932
 Project: Sqoop
  Issue Type: New Feature
Affects Versions: 1.99.6
Reporter: Szabolcs Vasas
Assignee: Abraham Fine
 Fix For: 1.99.7


we should be able to read and write parquet files from the hdfsconnector.



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

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

2016-05-25 Thread Szabolcs Vasas (JIRA) 

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

Szabolcs Vasas resolved SQOOP-2928.
---
Resolution: Not A Problem

The database create and upgrade scripts work fine on MySQL you just have to 
specify the Database Hostname field in CM the following way:

mysql.server?sessionVariables=sql_mode='ANSI_QUOTES'

> 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
>
> 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] [Updated] (SQOOP-2931) Sqoop2: Document requiring sql_mode='ANSI_QUOTES' for MySQL repositories

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine updated SQOOP-2931:

Labels: Newbie  (was: )

> Sqoop2: Document requiring sql_mode='ANSI_QUOTES' for MySQL repositories
> 
>
> Key: SQOOP-2931
> URL: https://issues.apache.org/jira/browse/SQOOP-2931
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>  Labels: Newbie
>




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

[jira] [Updated] (SQOOP-2931) Sqoop2: Document requiring sql_mode='ANSI_QUOTES' for MySQL repositories

2016-05-25 Thread Abraham Fine (JIRA) 

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

Abraham Fine updated SQOOP-2931:

Affects Version/s: 1.99.6

> Sqoop2: Document requiring sql_mode='ANSI_QUOTES' for MySQL repositories
> 
>
> Key: SQOOP-2931
> URL: https://issues.apache.org/jira/browse/SQOOP-2931
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.99.6
>Reporter: Abraham Fine
>  Labels: Newbie
>




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

[jira] [Created] (SQOOP-2931) Sqoop2: Document requiring sql_mode='ANSI_QUOTES' for MySQL repositories

2016-05-25 Thread Abraham Fine (JIRA) 
Abraham Fine created SQOOP-2931:
---

 Summary: Sqoop2: Document requiring sql_mode='ANSI_QUOTES' for 
MySQL repositories
 Key: SQOOP-2931
 URL: https://issues.apache.org/jira/browse/SQOOP-2931
 Project: Sqoop
  Issue Type: Bug
Reporter: Abraham Fine






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

[jira] [Commented] (SQOOP-2930) Sqoop job exec not overriding the saved job generic properties

2016-05-25 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on SQOOP-2930:
---

GitHub user git-rbanerjee opened a pull request:

https://github.com/apache/sqoop/pull/20

SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not overriding the saved pr…

…operties .

SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not overriding the saved 
properties .

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/git-rbanerjee/sqoop-1 patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sqoop/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit 3e091d1adf378b0ce73c0e63e42693aab1f2158f
Author: CodeR 
Date:   2016-05-25T07:02:09Z

SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not overriding the saved 
properties .

SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not overriding the saved 
properties .




> Sqoop job exec not overriding the saved job generic properties
> --
>
> Key: SQOOP-2930
> URL: https://issues.apache.org/jira/browse/SQOOP-2930
> Project: Sqoop
>  Issue Type: Bug
>Reporter: Rabin Banerjee
> Attachments: fixpatch_v1.patch
>
>
> Sqoop job exec not overriding the saved job generic properties .
> sqoop job -Dorg.apache.sqoop.xyz=xyz --create job1 -- import .. 
> sqoop job -Dorg.apache.sqoop.xyz=abc --exec job1
> exec is not overriding the xyz with abc



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

[GitHub] sqoop pull request: SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not ...

2016-05-25 Thread git-rbanerjee 
GitHub user git-rbanerjee opened a pull request:

https://github.com/apache/sqoop/pull/20

SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not overriding the saved pr…

…operties .

SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not overriding the saved 
properties .

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/git-rbanerjee/sqoop-1 patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sqoop/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit 3e091d1adf378b0ce73c0e63e42693aab1f2158f
Author: CodeR 
Date:   2016-05-25T07:02:09Z

SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not overriding the saved 
properties .

SQOOP-2930 & SQOOP-1933 :: Sqoop job exec not overriding the saved 
properties .




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (SQOOP-2930) Sqoop job exec not overriding the saved job generic properties

2016-05-25 Thread Rabin Banerjee (JIRA) 

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

Rabin Banerjee updated SQOOP-2930:
--
Attachment: fixpatch_v1.patch

Fix V1

> Sqoop job exec not overriding the saved job generic properties
> --
>
> Key: SQOOP-2930
> URL: https://issues.apache.org/jira/browse/SQOOP-2930
> Project: Sqoop
>  Issue Type: Bug
>Reporter: Rabin Banerjee
> Attachments: fixpatch_v1.patch
>
>
> Sqoop job exec not overriding the saved job generic properties .
> sqoop job -Dorg.apache.sqoop.xyz=xyz --create job1 -- import .. 
> sqoop job -Dorg.apache.sqoop.xyz=abc --exec job1
> exec is not overriding the xyz with abc



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

[jira] [Commented] (SQOOP-2930) Sqoop job exec not overriding the saved job generic properties

2016-05-25 Thread Rabin Banerjee (JIRA) 

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

Rabin Banerjee commented on SQOOP-2930:
---

https://issues.apache.org/jira/browse/SQOOP-1933 Can be also resolved with this.

> Sqoop job exec not overriding the saved job generic properties
> --
>
> Key: SQOOP-2930
> URL: https://issues.apache.org/jira/browse/SQOOP-2930
> Project: Sqoop
>  Issue Type: Bug
>Reporter: Rabin Banerjee
>
> Sqoop job exec not overriding the saved job generic properties .
> sqoop job -Dorg.apache.sqoop.xyz=xyz --create job1 -- import .. 
> sqoop job -Dorg.apache.sqoop.xyz=abc --exec job1
> exec is not overriding the xyz with abc



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

[jira] [Created] (SQOOP-2930) Sqoop job exec not overriding the saved job generic properties

2016-05-25 Thread Rabin Banerjee (JIRA) 
Rabin Banerjee created SQOOP-2930:
-

 Summary: Sqoop job exec not overriding the saved job generic 
properties
 Key: SQOOP-2930
 URL: https://issues.apache.org/jira/browse/SQOOP-2930
 Project: Sqoop
  Issue Type: Bug
Reporter: Rabin Banerjee


Sqoop job exec not overriding the saved job generic properties .

sqoop job -Dorg.apache.sqoop.xyz=xyz --create job1 -- import .. 

sqoop job -Dorg.apache.sqoop.xyz=abc --exec job1

exec is not overriding the xyz with abc



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

[jira] [Commented] (SQOOP-1933) CryptoFileLoader does not work for saved jobs

2016-05-25 Thread Rabin Banerjee (JIRA) 

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

Rabin Banerjee commented on SQOOP-1933:
---

[~jarcec] I have check the issue, and attached a patch, [~SQLEngineer] Check if 
it works.

> CryptoFileLoader does not work for saved jobs
> -
>
> Key: SQOOP-1933
> URL: https://issues.apache.org/jira/browse/SQOOP-1933
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.4.5
> Environment: Red Hat Enterprise Linux Server release 6.3 (Santiago)
>Reporter: Karthik S
> Fix For: 1.4.7
>
> Attachments: fixpatch_v1.patch
>
>
> I am able to use the CryptoFile Loader to read encrypted passwords from a 
> simple import command. However, the same command does not work from saved jobs
> The below command works. There are no problems with it. It successfully 
> decrypts the password and imports into hdfs
> sqoop import 
> -Dorg.apache.sqoop.credentials.loader.class=org.apache.sqoop.util.password.CryptoFileLoader
>  -Dorg.apache.sqoop.credentials.loader.crypto.passphrase=sqooppass --driver 
> com.mysql.jdbc.Driver --connect jdbc:mysql://00.00.000.000:/test 
> --username user --password-file /user/user1/temp.txt  --table emp 
> --target-dir /user/user1/karthik/e129 --split-by emp_id
> However, When i try using saved jobs, it does not work.
> sqoop job 
> -Dorg.apache.sqoop.credentials.loader.class=org.apache.sqoop.util.password.CryptoFileLoader
>  -Dorg.apache.sqoop.credentials.loader.crypto.passphrase=sqooppass --create 
> job9 -- import --driver com.mysql.jdbc.Driver --connect 
> jdbc:mysql://00.00.000.000:3306/test --username user --password-file 
> /user/user1/temp.txt  --table emp --target-dir /user/user1/karthik/e130 
> --split-by emp_id
> sqoop job -exec job9 -- --target-dir /user/user1/emp_103
> It gives error 
> 14/12/22 15:39:48 ERROR sqoop.Sqoop: Got exception running Sqoop: 
> java.lang.RuntimeException: Unable to fetch password from file.
> java.lang.RuntimeException: Unable to fetch password from file.
> at 
> org.apache.sqoop.SqoopOptions.loadPasswordProperty(SqoopOptions.java:667)
> at org.apache.sqoop.SqoopOptions.loadProperties(SqoopOptions.java:617)
> at 
> org.apache.sqoop.metastore.hsqldb.HsqldbJobStorage.read(HsqldbJobStorage.java:299)
> at org.apache.sqoop.tool.JobTool.execJob(JobTool.java:198)
> at org.apache.sqoop.tool.JobTool.run(JobTool.java:283)
> at org.apache.sqoop.Sqoop.run(Sqoop.java:143)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:179)
> at org.apache.sqoop.Sqoop.runTool(Sqoop.java:218)
> at org.apache.sqoop.Sqoop.runTool(Sqoop.java:227)
> at org.apache.sqoop.Sqoop.main(Sqoop.java:236)
> Caused by: java.io.IOException: Can't decrypt the password
> at 
> org.apache.sqoop.util.password.CryptoFileLoader.loadPassword(CryptoFileLoader.java:151)
> at 
> org.apache.sqoop.util.CredentialsUtil.fetchPasswordFromLoader(CredentialsUtil.java:81)
> at 
> org.apache.sqoop.SqoopOptions.loadPasswordProperty(SqoopOptions.java:664)
> ... 10 more
> Caused by: javax.crypto.BadPaddingException: Given final block not properly 
> padded
> at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)
> at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)
> at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)
> at javax.crypto.Cipher.doFinal(Cipher.java:2087)
> at 
> org.apache.sqoop.util.password.CryptoFileLoader.loadPassword(CryptoFileLoader.java:149)
> ... 12 more



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

[jira] [Updated] (SQOOP-1933) CryptoFileLoader does not work for saved jobs

2016-05-25 Thread Rabin Banerjee (JIRA) 

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

Rabin Banerjee updated SQOOP-1933:
--
Attachment: fixpatch_v1.patch

Fix Patch

> CryptoFileLoader does not work for saved jobs
> -
>
> Key: SQOOP-1933
> URL: https://issues.apache.org/jira/browse/SQOOP-1933
> Project: Sqoop
>  Issue Type: Bug
>Affects Versions: 1.4.5
> Environment: Red Hat Enterprise Linux Server release 6.3 (Santiago)
>Reporter: Karthik S
> Fix For: 1.4.7
>
> Attachments: fixpatch_v1.patch
>
>
> I am able to use the CryptoFile Loader to read encrypted passwords from a 
> simple import command. However, the same command does not work from saved jobs
> The below command works. There are no problems with it. It successfully 
> decrypts the password and imports into hdfs
> sqoop import 
> -Dorg.apache.sqoop.credentials.loader.class=org.apache.sqoop.util.password.CryptoFileLoader
>  -Dorg.apache.sqoop.credentials.loader.crypto.passphrase=sqooppass --driver 
> com.mysql.jdbc.Driver --connect jdbc:mysql://00.00.000.000:/test 
> --username user --password-file /user/user1/temp.txt  --table emp 
> --target-dir /user/user1/karthik/e129 --split-by emp_id
> However, When i try using saved jobs, it does not work.
> sqoop job 
> -Dorg.apache.sqoop.credentials.loader.class=org.apache.sqoop.util.password.CryptoFileLoader
>  -Dorg.apache.sqoop.credentials.loader.crypto.passphrase=sqooppass --create 
> job9 -- import --driver com.mysql.jdbc.Driver --connect 
> jdbc:mysql://00.00.000.000:3306/test --username user --password-file 
> /user/user1/temp.txt  --table emp --target-dir /user/user1/karthik/e130 
> --split-by emp_id
> sqoop job -exec job9 -- --target-dir /user/user1/emp_103
> It gives error 
> 14/12/22 15:39:48 ERROR sqoop.Sqoop: Got exception running Sqoop: 
> java.lang.RuntimeException: Unable to fetch password from file.
> java.lang.RuntimeException: Unable to fetch password from file.
> at 
> org.apache.sqoop.SqoopOptions.loadPasswordProperty(SqoopOptions.java:667)
> at org.apache.sqoop.SqoopOptions.loadProperties(SqoopOptions.java:617)
> at 
> org.apache.sqoop.metastore.hsqldb.HsqldbJobStorage.read(HsqldbJobStorage.java:299)
> at org.apache.sqoop.tool.JobTool.execJob(JobTool.java:198)
> at org.apache.sqoop.tool.JobTool.run(JobTool.java:283)
> at org.apache.sqoop.Sqoop.run(Sqoop.java:143)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:179)
> at org.apache.sqoop.Sqoop.runTool(Sqoop.java:218)
> at org.apache.sqoop.Sqoop.runTool(Sqoop.java:227)
> at org.apache.sqoop.Sqoop.main(Sqoop.java:236)
> Caused by: java.io.IOException: Can't decrypt the password
> at 
> org.apache.sqoop.util.password.CryptoFileLoader.loadPassword(CryptoFileLoader.java:151)
> at 
> org.apache.sqoop.util.CredentialsUtil.fetchPasswordFromLoader(CredentialsUtil.java:81)
> at 
> org.apache.sqoop.SqoopOptions.loadPasswordProperty(SqoopOptions.java:664)
> ... 10 more
> Caused by: javax.crypto.BadPaddingException: Given final block not properly 
> padded
> at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)
> at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)
> at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)
> at javax.crypto.Cipher.doFinal(Cipher.java:2087)
> at 
> org.apache.sqoop.util.password.CryptoFileLoader.loadPassword(CryptoFileLoader.java:149)
> ... 12 more



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