[jira] [Commented] (SQOOP-2728) Sqoop2: Avoid casting after calling getObject on ResultSet
[ https://issues.apache.org/jira/browse/SQOOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061839#comment-15061839 ] Hudson commented on SQOOP-2728: --- SUCCESS: Integrated in Sqoop2 #975 (See [https://builds.apache.org/job/Sqoop2/975/]) SQOOP-2728: Sqoop2: Avoid casting after calling getObject on ResultSet (jarcec: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git=commit=c5962f8e154a0e7b334236a71687a39f5c40d340]) * connector/connector-generic-jdbc/src/main/java/org/apache/sqoop/connector/jdbc/GenericJdbcExtractor.java > Sqoop2: Avoid casting after calling getObject on ResultSet > -- > > Key: SQOOP-2728 > URL: https://issues.apache.org/jira/browse/SQOOP-2728 > Project: Sqoop > Issue Type: Bug >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 1.99.7 > > Attachments: SQOOP-2728.patch > > > Oracle may returna non java ee standard datatype if getObject is called on a > resultset. We should use getTimestamp, getDate... in the extractor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2728) Sqoop2: Avoid casting after calling getObject on ResultSet
[
https://issues.apache.org/jira/browse/SQOOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061780#comment-15061780
]
Sqoop QA bot commented on SQOOP-2728:
-
Testing file
[SQOOP-2728.patch|https://issues.apache.org/jira/secure/attachment/12777900/SQOOP-2728.patch]
against branch sqoop2 took 1:05:19.580116.
{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 1646 tests)
{color:green}SUCCESS:{color} Test coverage did not decreased
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/2025/artifact/patch-process/cobertura_report.txt])
{color:green}SUCCESS:{color} No new findbugs warnings
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/2025/artifact/patch-process/findbugs_report.txt])
{color:green}SUCCESS:{color} All integration tests passed (executed 145 tests)
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/2025/console].
This message is automatically generated.
> Sqoop2: Avoid casting after calling getObject on ResultSet
> --
>
> Key: SQOOP-2728
> URL: https://issues.apache.org/jira/browse/SQOOP-2728
> Project: Sqoop
> Issue Type: Bug
>Reporter: Abraham Fine
>Assignee: Abraham Fine
> Fix For: 1.99.7
>
> Attachments: SQOOP-2728.patch
>
>
> Oracle may returna non java ee standard datatype if getObject is called on a
> resultset. We should use getTimestamp, getDate... in the extractor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SQOOP-2728) Sqoop2: Avoid casting after calling getObject on ResultSet
[ https://issues.apache.org/jira/browse/SQOOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061792#comment-15061792 ] Jarek Jarcec Cecho commented on SQOOP-2728: --- Absence of unit tests seems reasonable in this patch - the fact that existing unit tests passes without changes is actually positive sign. > Sqoop2: Avoid casting after calling getObject on ResultSet > -- > > Key: SQOOP-2728 > URL: https://issues.apache.org/jira/browse/SQOOP-2728 > Project: Sqoop > Issue Type: Bug >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 1.99.7 > > Attachments: SQOOP-2728.patch > > > Oracle may returna non java ee standard datatype if getObject is called on a > resultset. We should use getTimestamp, getDate... in the extractor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2728) Sqoop2: Avoid casting after calling getObject on ResultSet
[ https://issues.apache.org/jira/browse/SQOOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061793#comment-15061793 ] Jarek Jarcec Cecho commented on SQOOP-2728: --- +1 > Sqoop2: Avoid casting after calling getObject on ResultSet > -- > > Key: SQOOP-2728 > URL: https://issues.apache.org/jira/browse/SQOOP-2728 > Project: Sqoop > Issue Type: Bug >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 1.99.7 > > Attachments: SQOOP-2728.patch > > > Oracle may returna non java ee standard datatype if getObject is called on a > resultset. We should use getTimestamp, getDate... in the extractor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2728) Sqoop2: Avoid casting after calling getObject on ResultSet
[ https://issues.apache.org/jira/browse/SQOOP-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061797#comment-15061797 ] ASF subversion and git services commented on SQOOP-2728: Commit c5962f8e154a0e7b334236a71687a39f5c40d340 in sqoop's branch refs/heads/sqoop2 from [~jarcec] [ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=c5962f8 ] SQOOP-2728: Sqoop2: Avoid casting after calling getObject on ResultSet (Abraham Fine via Jarek Jarcec Cecho) > Sqoop2: Avoid casting after calling getObject on ResultSet > -- > > Key: SQOOP-2728 > URL: https://issues.apache.org/jira/browse/SQOOP-2728 > Project: Sqoop > Issue Type: Bug >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 1.99.7 > > Attachments: SQOOP-2728.patch > > > Oracle may returna non java ee standard datatype if getObject is called on a > resultset. We should use getTimestamp, getDate... in the extractor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SQOOP-2749) xmltype not working in Sqoop
Arun Chowdary created SQOOP-2749: Summary: xmltype not working in Sqoop Key: SQOOP-2749 URL: https://issues.apache.org/jira/browse/SQOOP-2749 Project: Sqoop Issue Type: Test Reporter: Arun Chowdary Hi, I'm trying to import a column from oracle which consists of xml files, of datatype HUGECLOB using Sqoop. However I'm receiving an error "Cannot resolve SQL Type 1009". Below is the sqoop command used. sqoop import --jdbc connection --username --password --query "select xmltype(xmlfilecolumn) from table where $CONDITIONS" --target dir Appreciate your help! Regards Arun -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SQOOP-2719) Sqoop2: Ensure the GenericJDBCConnector integration tests work against MySQL, PostgreSQL, and Oracle
[ https://issues.apache.org/jira/browse/SQOOP-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abraham Fine resolved SQOOP-2719. - Resolution: Fixed > Sqoop2: Ensure the GenericJDBCConnector integration tests work against MySQL, > PostgreSQL, and Oracle > > > Key: SQOOP-2719 > URL: https://issues.apache.org/jira/browse/SQOOP-2719 > Project: Sqoop > Issue Type: Bug >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 1.99.7 > > Attachments: SQOOP-2719.patch > > > The GenericJDBCConnector should function with MySQL, PostgreSQL, or Oracle. > This patch makes the integration tests compatible with all 3 databases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2719) Sqoop2: Ensure the GenericJDBCConnector integration tests work against MySQL, PostgreSQL, and Oracle
[ https://issues.apache.org/jira/browse/SQOOP-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15062965#comment-15062965 ] Abraham Fine commented on SQOOP-2719: - [~jarcec] marked resolved > Sqoop2: Ensure the GenericJDBCConnector integration tests work against MySQL, > PostgreSQL, and Oracle > > > Key: SQOOP-2719 > URL: https://issues.apache.org/jira/browse/SQOOP-2719 > Project: Sqoop > Issue Type: Bug >Reporter: Abraham Fine >Assignee: Abraham Fine > Fix For: 1.99.7 > > Attachments: SQOOP-2719.patch > > > The GenericJDBCConnector should function with MySQL, PostgreSQL, or Oracle. > This patch makes the integration tests compatible with all 3 databases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2739) Sqoop2: Use resource name instead of resource id in authorization engine
[ https://issues.apache.org/jira/browse/SQOOP-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063624#comment-15063624 ] ASF subversion and git services commented on SQOOP-2739: Commit f4909a5634b085c9291efb95e1dd3b8579f4b1b5 in sqoop's branch refs/heads/sqoop2 from [~jarcec] [ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=f4909a5 ] SQOOP-2739: Sqoop2: Use resource name instead of resource id in authorization engine (Colin Ma via Jarek Jarcec Cecho) > Sqoop2: Use resource name instead of resource id in authorization engine > > > Key: SQOOP-2739 > URL: https://issues.apache.org/jira/browse/SQOOP-2739 > Project: Sqoop > Issue Type: Sub-task >Reporter: Colin Ma >Assignee: Colin Ma > Fix For: 1.99.7 > > Attachments: SQOOP-2739.001.patch > > > Use resource name instead of resource id in authorization engine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2739) Sqoop2: Use resource name instead of resource id in authorization engine
[ https://issues.apache.org/jira/browse/SQOOP-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063623#comment-15063623 ] Jarek Jarcec Cecho commented on SQOOP-2739: --- +1, overriding the absence of unit tests > Sqoop2: Use resource name instead of resource id in authorization engine > > > Key: SQOOP-2739 > URL: https://issues.apache.org/jira/browse/SQOOP-2739 > Project: Sqoop > Issue Type: Sub-task >Reporter: Colin Ma >Assignee: Colin Ma > Fix For: 1.99.7 > > Attachments: SQOOP-2739.001.patch > > > Use resource name instead of resource id in authorization engine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2739) Sqoop2: Use resource name instead of resource id in authorization engine
[
https://issues.apache.org/jira/browse/SQOOP-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063341#comment-15063341
]
Sqoop QA bot commented on SQOOP-2739:
-
Testing file
[SQOOP-2739.001.patch|https://issues.apache.org/jira/secure/attachment/12778398/SQOOP-2739.001.patch]
against branch sqoop2 took 1:00:47.681394.
{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 1646 tests)
{color:green}SUCCESS:{color} Test coverage did not decreased
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/2026/artifact/patch-process/cobertura_report.txt])
{color:green}SUCCESS:{color} No new findbugs warnings
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/2026/artifact/patch-process/findbugs_report.txt])
{color:green}SUCCESS:{color} All integration tests passed (executed 145 tests)
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/2026/console].
This message is automatically generated.
> Sqoop2: Use resource name instead of resource id in authorization engine
>
>
> Key: SQOOP-2739
> URL: https://issues.apache.org/jira/browse/SQOOP-2739
> Project: Sqoop
> Issue Type: Sub-task
>Reporter: Colin Ma
>Assignee: Colin Ma
> Fix For: 1.99.7
>
> Attachments: SQOOP-2739.001.patch
>
>
> Use resource name instead of resource id in authorization engine
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SQOOP-2739) Sqoop2: Use resource name instead of resource id in authorization engine
[ https://issues.apache.org/jira/browse/SQOOP-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Ma updated SQOOP-2739: Attachment: SQOOP-2739.001.patch A simple update without review board. > Sqoop2: Use resource name instead of resource id in authorization engine > > > Key: SQOOP-2739 > URL: https://issues.apache.org/jira/browse/SQOOP-2739 > Project: Sqoop > Issue Type: Sub-task >Reporter: Colin Ma >Assignee: Colin Ma > Fix For: 1.99.7 > > Attachments: SQOOP-2739.001.patch > > > Use resource name instead of resource id in authorization engine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SQOOP-2701) Sqoop2: Command "show job" doesn't work after removing support for ids:
[
https://issues.apache.org/jira/browse/SQOOP-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063276#comment-15063276
]
Colin Ma commented on SQOOP-2701:
-
[~jarcec], I think this problem is already fixed in SQOOP-2692 or SQOOP-2734.
> Sqoop2: Command "show job" doesn't work after removing support for ids:
> ---
>
> Key: SQOOP-2701
> URL: https://issues.apache.org/jira/browse/SQOOP-2701
> Project: Sqoop
> Issue Type: Sub-task
>Reporter: Jarek Jarcec Cecho
>Assignee: Colin Ma
> Fix For: 1.99.7
>
>
> Here is the exception that I'm getting:
> {code}
> sqoop:000> show job
> Exception has occurred during processing command
> Exception: org.apache.sqoop.common.SqoopException Message: CLIENT_0001:Server
> has returned exception
> Stack trace:
>at org.apache.sqoop.client.request.ResourceRequest
> (ResourceRequest.java:137)
>at org.apache.sqoop.client.request.ResourceRequest
> (ResourceRequest.java:69)
>at org.apache.sqoop.client.request.ResourceRequest
> (ResourceRequest.java:179)
>at org.apache.sqoop.client.request.LinkResourceRequest
> (LinkResourceRequest.java:53)
>at org.apache.sqoop.client.request.SqoopResourceRequests
> (SqoopResourceRequests.java:126)
>at org.apache.sqoop.client.SqoopClient (SqoopClient.java:311)
>at org.apache.sqoop.shell.ShowJobFunction (ShowJobFunction.java:98)
>at org.apache.sqoop.shell.ShowJobFunction (ShowJobFunction.java:71)
>at org.apache.sqoop.shell.SqoopFunction (SqoopFunction.java:51)
>at org.apache.sqoop.shell.SqoopCommand (SqoopCommand.java:134)
>at org.apache.sqoop.shell.SqoopCommand (SqoopCommand.java:110)
>at org.codehaus.groovy.tools.shell.Command$execute (null:-1)
>at org.codehaus.groovy.tools.shell.Shell (Shell.groovy:101)
>at org.codehaus.groovy.tools.shell.Groovysh (Groovysh.groovy:-1)
>at sun.reflect.NativeMethodAccessorImpl
> (NativeMethodAccessorImpl.java:-2)
>at sun.reflect.NativeMethodAccessorImpl
> (NativeMethodAccessorImpl.java:57)
>at sun.reflect.DelegatingMethodAccessorImpl
> (DelegatingMethodAccessorImpl.java:43)
>at java.lang.reflect.Method (Method.java:606)
>at org.codehaus.groovy.reflection.CachedMethod (CachedMethod.java:90)
>at groovy.lang.MetaMethod (MetaMethod.java:324)
>at groovy.lang.MetaClassImpl (MetaClassImpl.java:1208)
>at org.codehaus.groovy.runtime.ScriptBytecodeAdapter
> (ScriptBytecodeAdapter.java:130)
>at org.codehaus.groovy.tools.shell.Groovysh (Groovysh.groovy:254)
>at sun.reflect.NativeMethodAccessorImpl
> (NativeMethodAccessorImpl.java:-2)
>at sun.reflect.NativeMethodAccessorImpl
> (NativeMethodAccessorImpl.java:57)
>at sun.reflect.DelegatingMethodAccessorImpl
> (DelegatingMethodAccessorImpl.java:43)
>at java.lang.reflect.Method (Method.java:606)
>at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce
> (PogoMetaMethodSite.java:207)
>at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite
> (PogoMetaMethodSite.java:56)
>at org.codehaus.groovy.runtime.callsite.AbstractCallSite
> (AbstractCallSite.java:161)
>at org.codehaus.groovy.tools.shell.Groovysh (Groovysh.groovy:153)
>at org.codehaus.groovy.tools.shell.Shell (Shell.groovy:119)
>at org.codehaus.groovy.tools.shell.Shell$leftShift$0 (null:-1)
>at org.codehaus.groovy.tools.shell.ShellRunner (ShellRunner.groovy:94)
>at org.codehaus.groovy.tools.shell.InteractiveShellRunner
> (InteractiveShellRunner.groovy:-1)
>at sun.reflect.NativeMethodAccessorImpl
> (NativeMethodAccessorImpl.java:-2)
>at sun.reflect.NativeMethodAccessorImpl
> (NativeMethodAccessorImpl.java:57)
>at sun.reflect.DelegatingMethodAccessorImpl
> (DelegatingMethodAccessorImpl.java:43)
>at java.lang.reflect.Method (Method.java:606)
>at org.codehaus.groovy.reflection.CachedMethod (CachedMethod.java:90)
>at groovy.lang.MetaMethod (MetaMethod.java:324)
>at groovy.lang.MetaClassImpl (MetaClassImpl.java:1208)
>at org.codehaus.groovy.runtime.ScriptBytecodeAdapter
> (ScriptBytecodeAdapter.java:130)
>at org.codehaus.groovy.runtime.ScriptBytecodeAdapter
> (ScriptBytecodeAdapter.java:150)
>at org.codehaus.groovy.tools.shell.InteractiveShellRunner
> (InteractiveShellRunner.groovy:123)
>at sun.reflect.NativeMethodAccessorImpl
> (NativeMethodAccessorImpl.java:-2)
>at sun.reflect.NativeMethodAccessorImpl
> (NativeMethodAccessorImpl.java:57)
>at sun.reflect.DelegatingMethodAccessorImpl
>
