[GitHub] [sqoop] szvasas commented on issue #81: SQOOP-3441 Prepare Sqoop for Java 11 support

2019-06-05 Thread GitBox
szvasas commented on issue #81: SQOOP-3441 Prepare Sqoop for Java 11 support
URL: https://github.com/apache/sqoop/pull/81#issuecomment-499135494
 
 
   Hi Feró,
   
   Thanks for submitting this improvement, unfortunately I don't have time to 
post a full review just had one comment on the Gradle upgrade.
   Since we have the following wrapper task defined in build.gradle I think it 
would be good to maintain the version number in it:
   ```
   wrapper {
   gradleVersion = '4.9'
   }
   ```
   Then running `./gradlew wrapper` to make sure everything is fully updated to 
the version specified.
   There are also some guidelines provided here: 
https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:upgrading_wrapper
   
   (We could also remove the wrapper task and just run `./gradlew wrapper 
--gradle-version ` in the future.)


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [sqoop] fszabo2 opened a new pull request #81: SQOOP-3441 Prepare Sqoop for Java 11 support

2019-06-05 Thread GitBox
fszabo2 opened a new pull request #81: SQOOP-3441 Prepare Sqoop for Java 11 
support
URL: https://github.com/apache/sqoop/pull/81
 
 
   Contains the following minor fixes that came up when executing tests with 
java11:
   - Bumped gradle version from 4.9 to 5.3.1 (needed for jacoco plugin)
   - Fixed illegal access of constructor in a TestSqoopOptions
   - Removed the use of UrlClassLoader as it wasn't needed anyway (Accumulo 
mini cluster startup)


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[jira] [Created] (SQOOP-3441) Prepare Sqoop for Java 11 support

2019-06-05 Thread Fero Szabo (JIRA)
Fero Szabo created SQOOP-3441:
-

 Summary: Prepare Sqoop for Java 11 support
 Key: SQOOP-3441
 URL: https://issues.apache.org/jira/browse/SQOOP-3441
 Project: Sqoop
  Issue Type: Improvement
Reporter: Fero Szabo
Assignee: Fero Szabo


A couple of code changes will be required in order for Sqoop to work with 
Java11 and we'll also have to bump a couple of dependencies and the gradle 
version. 

I'm not sure what's required for ant, that is to be figured out in a separate 
Jira, if we keep the ant build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SQOOP-3438) Sqoop Import with create hcatalog table for ORC will not work with Hive3 as the table created would be a ACID table and transactional

2019-06-05 Thread Hudson (JIRA)


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

Hudson commented on SQOOP-3438:
---

SUCCESS: Integrated in Jenkins build Sqoop-hadoop200 #1259 (See 
[https://builds.apache.org/job/Sqoop-hadoop200/1259/])
SQOOP-3438: Sqoop Import with create hcatalog table for ORC will not (bogi: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=be260e3096a6a2710e661c7fe33f6b402ce66476])
* (edit) src/java/org/apache/sqoop/SqoopOptions.java
* (edit) src/java/org/apache/sqoop/mapreduce/hcat/SqoopHCatUtilities.java
* (edit) src/java/org/apache/sqoop/tool/BaseSqoopTool.java
* (edit) src/test/org/apache/sqoop/hcat/HCatalogTestUtils.java
* (edit) src/test/org/apache/sqoop/hcat/HCatalogImportTest.java
* (edit) src/docs/user/hcatalog.txt


> Sqoop Import with create hcatalog table for ORC will not work with Hive3 as 
> the table created would be a ACID table and transactional
> -
>
> Key: SQOOP-3438
> URL: https://issues.apache.org/jira/browse/SQOOP-3438
> Project: Sqoop
>  Issue Type: Improvement
>  Components: hive-integration
>Affects Versions: 1.4.7
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
> Fix For: 1.5.0
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> PROBLEM: Running a sqoop import command with the option 
> --create-hcatalog-table will not work due to the following reasons
> When create-hcatalog-table is used it creates the table as a Managed ACID 
> table.
> HCatalog does not support transactional or bucketing table
> So customer who need to create a ORC based table cannot use sqoop to create a 
> ORC based table which means their existing code where if in case they use 
> sqoop to create these tables would fail.
> The current workaround is a two step process
> 1. Create the ORC table in hive with the keyword external and set 
> transactional to false
> 2. Then use the sqoop command to load the data into the orc table.
> The request is to add in an extra argument in the sqoop command line to 
> specify that the table is external (example: --hcatalog-external-table )so we 
> can use the option --hcatalog-storage-stanza "stored as orc tblproperties 
> (\"transactional\"=\"false\")".
> 
> Thank you [~mbalakrishnan] for your findings. This ticket is created based on 
> your work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (SQOOP-3438) Sqoop Import with create hcatalog table for ORC will not work with Hive3 as the table created would be a ACID table and transactional

2019-06-05 Thread Boglarka Egyed (JIRA)


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

Boglarka Egyed resolved SQOOP-3438.
---
   Resolution: Fixed
Fix Version/s: 1.5.0

Thank you [~dionusos] for your contribution! Your change is now merged to trunk.

> Sqoop Import with create hcatalog table for ORC will not work with Hive3 as 
> the table created would be a ACID table and transactional
> -
>
> Key: SQOOP-3438
> URL: https://issues.apache.org/jira/browse/SQOOP-3438
> Project: Sqoop
>  Issue Type: Improvement
>  Components: hive-integration
>Affects Versions: 1.4.7
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
> Fix For: 1.5.0
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> PROBLEM: Running a sqoop import command with the option 
> --create-hcatalog-table will not work due to the following reasons
> When create-hcatalog-table is used it creates the table as a Managed ACID 
> table.
> HCatalog does not support transactional or bucketing table
> So customer who need to create a ORC based table cannot use sqoop to create a 
> ORC based table which means their existing code where if in case they use 
> sqoop to create these tables would fail.
> The current workaround is a two step process
> 1. Create the ORC table in hive with the keyword external and set 
> transactional to false
> 2. Then use the sqoop command to load the data into the orc table.
> The request is to add in an extra argument in the sqoop command line to 
> specify that the table is external (example: --hcatalog-external-table )so we 
> can use the option --hcatalog-storage-stanza "stored as orc tblproperties 
> (\"transactional\"=\"false\")".
> 
> Thank you [~mbalakrishnan] for your findings. This ticket is created based on 
> your work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SQOOP-3438) Sqoop Import with create hcatalog table for ORC will not work with Hive3 as the table created would be a ACID table and transactional

2019-06-05 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on SQOOP-3438:


Commit be260e3096a6a2710e661c7fe33f6b402ce66476 in sqoop's branch 
refs/heads/trunk from Denes Bodo
[ https://gitbox.apache.org/repos/asf?p=sqoop.git;h=be260e3 ]

SQOOP-3438: Sqoop Import with create hcatalog table for ORC will not work with 
Hive3 as the table created would be a ACID table and transactional

(Denes Bodo via Boglarka Egyed)


> Sqoop Import with create hcatalog table for ORC will not work with Hive3 as 
> the table created would be a ACID table and transactional
> -
>
> Key: SQOOP-3438
> URL: https://issues.apache.org/jira/browse/SQOOP-3438
> Project: Sqoop
>  Issue Type: Improvement
>  Components: hive-integration
>Affects Versions: 1.4.7
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> PROBLEM: Running a sqoop import command with the option 
> --create-hcatalog-table will not work due to the following reasons
> When create-hcatalog-table is used it creates the table as a Managed ACID 
> table.
> HCatalog does not support transactional or bucketing table
> So customer who need to create a ORC based table cannot use sqoop to create a 
> ORC based table which means their existing code where if in case they use 
> sqoop to create these tables would fail.
> The current workaround is a two step process
> 1. Create the ORC table in hive with the keyword external and set 
> transactional to false
> 2. Then use the sqoop command to load the data into the orc table.
> The request is to add in an extra argument in the sqoop command line to 
> specify that the table is external (example: --hcatalog-external-table )so we 
> can use the option --hcatalog-storage-stanza "stored as orc tblproperties 
> (\"transactional\"=\"false\")".
> 
> Thank you [~mbalakrishnan] for your findings. This ticket is created based on 
> your work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] [sqoop] ebogi merged pull request #80: SQOOP-3438 Sqoop Import with create hcatalog table for ORC will not w…

2019-06-05 Thread GitBox
ebogi merged pull request #80: SQOOP-3438 Sqoop Import with create hcatalog 
table for ORC will not w…
URL: https://github.com/apache/sqoop/pull/80
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services