sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-456) Generated Java class does not distinguish date and timestamp in Oracle DB
Date Tue, 02 Jul 2013 17:51:20 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698034#comment-13698034

Jarek Jarcec Cecho commented on SQOOP-456:

Hi [~jleech],
thank you very much for your feedback! Sqoop should always follow the data types provided
by the JDBC drivers (or the overrides on command line) and that should be accomplished by
the property {{Doracle.jdbc.V8Compatible}}. If this is not the case and sqoop is still using
different type than please create a new JIRA with description on what circumstances this occurs
and we will be more than happy to take a look!

> Generated Java class does not distinguish date and timestamp in Oracle DB 
> --------------------------------------------------------------------------
>                 Key: SQOOP-456
>                 URL: https://issues.apache.org/jira/browse/SQOOP-456
>             Project: Sqoop
>          Issue Type: Bug
>          Components: codegen
>            Reporter: Cheolsoo Park
>            Priority: Minor
> In genereated Java class, both date and timestamp are considered as timestamps. For examples,
the following getter method is generated for a date column:
> {code:xml} 
> public void readFields(ResultSet __dbResults) throws SQLException {
>   this.__cur_result_set = __dbResults;
>   this.DATA_COL0 = JdbcWritableBridge.readTimestamp(1, __dbResults);
> }
> {code}
> This happens because both date and timestamp is labeled as Types.TIMESTAMP by ConnManager.
The fix seems straightforward. In ClassWriter, the new method getColTypeNamesForTable introduced
by Bilung at SQOOP-352 should replace getColTypes(). 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message