[jira] [Updated] (SQOOP-3054) Get FileSystem from parameter "--target-dir"
[ https://issues.apache.org/jira/browse/SQOOP-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Cao updated SQOOP-3054: Priority: Critical (was: Major) > Get FileSystem from parameter "--target-dir" > > > Key: SQOOP-3054 > URL: https://issues.apache.org/jira/browse/SQOOP-3054 > Project: Sqoop > Issue Type: Bug > Components: connectors >Affects Versions: 1.4.6 > Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2+Hive 1.2.1 >Reporter: Ying Cao >Priority: Critical > Fix For: 1.4.7 > > Attachments: SQOOP-3054.patch > > > FileSystems gets from conf , update to get filesystem from parateter > "--target-dir" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-3028) Include stack trace in the logging of exceptions in ExportTool
[ https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686497#comment-15686497 ] Hudson commented on SQOOP-3028: --- FAILURE: Integrated in Jenkins build Sqoop-hadoop23 #1271 (See [https://builds.apache.org/job/Sqoop-hadoop23/1271/]) SQOOP-3028: Include stack trace in the logging of exceptions in (maugli: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=c08c194eb9a34733305535a9512f3b642ef33f95]) * (edit) src/java/org/apache/sqoop/tool/ExportTool.java > Include stack trace in the logging of exceptions in ExportTool > -- > > Key: SQOOP-3028 > URL: https://issues.apache.org/jira/browse/SQOOP-3028 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Boglarka Egyed >Priority: Trivial > Fix For: 1.4.7 > > Attachments: SQOOP-3028.patch > > > Currently only the message of the IOException/Export is logged in runExport > method. Although it's possible to rethrow the root cause as a runtime > exception it would be nice to improve to add an option which makes possible > to have the improved logging details without an additional exception (as that > could be problematic on tooling side). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-3028) Include stack trace in the logging of exceptions in ExportTool
[ https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686487#comment-15686487 ] Hudson commented on SQOOP-3028: --- FAILURE: Integrated in Jenkins build Sqoop-hadoop20 #1069 (See [https://builds.apache.org/job/Sqoop-hadoop20/1069/]) SQOOP-3028: Include stack trace in the logging of exceptions in (maugli: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=c08c194eb9a34733305535a9512f3b642ef33f95]) * (edit) src/java/org/apache/sqoop/tool/ExportTool.java > Include stack trace in the logging of exceptions in ExportTool > -- > > Key: SQOOP-3028 > URL: https://issues.apache.org/jira/browse/SQOOP-3028 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Boglarka Egyed >Priority: Trivial > Fix For: 1.4.7 > > Attachments: SQOOP-3028.patch > > > Currently only the message of the IOException/Export is logged in runExport > method. Although it's possible to rethrow the root cause as a runtime > exception it would be nice to improve to add an option which makes possible > to have the improved logging details without an additional exception (as that > could be problematic on tooling side). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-3028) Include stack trace in the logging of exceptions in ExportTool
[ https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686471#comment-15686471 ] Hudson commented on SQOOP-3028: --- FAILURE: Integrated in Jenkins build Sqoop-hadoop200 #1075 (See [https://builds.apache.org/job/Sqoop-hadoop200/1075/]) SQOOP-3028: Include stack trace in the logging of exceptions in (maugli: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=c08c194eb9a34733305535a9512f3b642ef33f95]) * (edit) src/java/org/apache/sqoop/tool/ExportTool.java > Include stack trace in the logging of exceptions in ExportTool > -- > > Key: SQOOP-3028 > URL: https://issues.apache.org/jira/browse/SQOOP-3028 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Boglarka Egyed >Priority: Trivial > Fix For: 1.4.7 > > Attachments: SQOOP-3028.patch > > > Currently only the message of the IOException/Export is logged in runExport > method. Although it's possible to rethrow the root cause as a runtime > exception it would be nice to improve to add an option which makes possible > to have the improved logging details without an additional exception (as that > could be problematic on tooling side). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2973) Is sqoop version 1.4.6 is compatible with hbase version 1.2.1?
[
https://issues.apache.org/jira/browse/SQOOP-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686459#comment-15686459
]
Eric Lin commented on SQOOP-2973:
-
Hi [~vasas],
Thanks for the update. I have compiled the trunk version of Sqoop with
{code}
ant -Dhadoopversion=260 -Dhbaseprofile=95
{code}
According to build.xml file, hbaseprofile=95 for hadoopversion=260 will build
against hbase 1.2.0:
{code}
{code}
I checked the built output jar files, they are all for hbsae 1.2.0 version, so
in theory that should work right? What did I do wrong or do I need to change
the build file somehow?
Thanks
> Is sqoop version 1.4.6 is compatible with hbase version 1.2.1?
> ---
>
> Key: SQOOP-2973
> URL: https://issues.apache.org/jira/browse/SQOOP-2973
> Project: Sqoop
> Issue Type: Bug
> Environment: Haddop version 2.7.2
>Reporter: Rajib Mandal
>
> We are getting below error while importing data from Oracle to Hbase
> error Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.hadoop.hbase.HTableDescriptor.addFamily(Lorg/apache/hadoop/hbase/HColumnDescriptor;)V
>
> The command executed
> sqoop import --connect jdbc:oracle:thin:@//orcl. --username sysdba
> --password --table GENDER2 --columns "EMPLOYEE_ID,FIRST_NAME,GENDER"
> --hbase-table employee --column-family GENDER2 --hbase-row-key EMPLOYEE_ID
> --hbase-create-table
> Is there any way to resolve this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SQOOP-3028) Include stack trace in the logging of exceptions in ExportTool
[ https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686401#comment-15686401 ] Hudson commented on SQOOP-3028: --- FAILURE: Integrated in Jenkins build Sqoop-hadoop100 #1034 (See [https://builds.apache.org/job/Sqoop-hadoop100/1034/]) SQOOP-3028: Include stack trace in the logging of exceptions in (maugli: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=c08c194eb9a34733305535a9512f3b642ef33f95]) * (edit) src/java/org/apache/sqoop/tool/ExportTool.java > Include stack trace in the logging of exceptions in ExportTool > -- > > Key: SQOOP-3028 > URL: https://issues.apache.org/jira/browse/SQOOP-3028 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Boglarka Egyed >Priority: Trivial > Fix For: 1.4.7 > > Attachments: SQOOP-3028.patch > > > Currently only the message of the IOException/Export is logged in runExport > method. Although it's possible to rethrow the root cause as a runtime > exception it would be nice to improve to add an option which makes possible > to have the improved logging details without an additional exception (as that > could be problematic on tooling side). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-3028) Include stack trace in the logging of exceptions in ExportTool
[ https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686397#comment-15686397 ] Attila Szabo commented on SQOOP-3028: - Thank you [~BoglarkaEgyed] for this contribution! > Include stack trace in the logging of exceptions in ExportTool > -- > > Key: SQOOP-3028 > URL: https://issues.apache.org/jira/browse/SQOOP-3028 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Boglarka Egyed >Priority: Trivial > Fix For: 1.4.7 > > Attachments: SQOOP-3028.patch > > > Currently only the message of the IOException/Export is logged in runExport > method. Although it's possible to rethrow the root cause as a runtime > exception it would be nice to improve to add an option which makes possible > to have the improved logging details without an additional exception (as that > could be problematic on tooling side). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-3028) Include stack trace in the logging of exceptions in ExportTool
[ https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686393#comment-15686393 ] ASF subversion and git services commented on SQOOP-3028: Commit c08c194eb9a34733305535a9512f3b642ef33f95 in sqoop's branch refs/heads/trunk from [~maugli] [ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=c08c194 ] SQOOP-3028: Include stack trace in the logging of exceptions in ExportTool (Boglarka Egyed via Attila Szabo) > Include stack trace in the logging of exceptions in ExportTool > -- > > Key: SQOOP-3028 > URL: https://issues.apache.org/jira/browse/SQOOP-3028 > Project: Sqoop > Issue Type: Improvement >Reporter: Attila Szabo >Assignee: Boglarka Egyed >Priority: Trivial > Fix For: 1.4.7 > > Attachments: SQOOP-3028.patch > > > Currently only the message of the IOException/Export is logged in runExport > method. Although it's possible to rethrow the root cause as a runtime > exception it would be nice to improve to add an option which makes possible > to have the improved logging details without an additional exception (as that > could be problematic on tooling side). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 53946: Include stack trace in the logging of exceptions in ExportTool
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/53946/#review156561 --- Ship it! - Attila Szabo On Nov. 21, 2016, 2:18 p.m., Boglarka Egyed wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/53946/ > --- > > (Updated Nov. 21, 2016, 2:18 p.m.) > > > Review request for Sqoop and Attila Szabo. > > > Bugs: SQOOP-3028 > https://issues.apache.org/jira/browse/SQOOP-3028 > > > Repository: sqoop-trunk > > > Description > --- > > Include stack trace in the logging of exceptions in ExportTool > > > Diffs > - > > src/java/org/apache/sqoop/tool/ExportTool.java bd51c30 > > Diff: https://reviews.apache.org/r/53946/diff/ > > > Testing > --- > > No specific test case needed > > > Thanks, > > Boglarka Egyed > >
[jira] [Created] (SQOOP-3056) Add ant ivy report target
Anna Szonyi created SQOOP-3056: -- Summary: 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 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] [Created] (SQOOP-3055) MYSQL tests are failing unless using localhost + root
Anna Szonyi created SQOOP-3055:
--
Summary: MYSQL tests are failing unless using localhost + root
Key: SQOOP-3055
URL: https://issues.apache.org/jira/browse/SQOOP-3055
Project: Sqoop
Issue Type: Sub-task
Reporter: Anna Szonyi
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
