You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "David Robson (JIRA)" <ji...@apache.org> on 2013/01/27 11:35:13 UTC

[jira] [Updated] (SQOOP-830) HBase import formatting BigDecimal inconsistently

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

David Robson updated SQOOP-830:
-------------------------------

    Attachment: SQOOP-830.patch
    
> HBase import formatting BigDecimal inconsistently
> -------------------------------------------------
>
>                 Key: SQOOP-830
>                 URL: https://issues.apache.org/jira/browse/SQOOP-830
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: David Robson
>            Assignee: David Robson
>         Attachments: SQOOP-830.patch
>
>
> When importing into HBase the toString() method is called on every field via the ToStringPutTransformer class.
> When the field is mapped as a BigDecimal - as it is with number fields in Oracle - this results in inconsistent formats in HBase.
> For example - create the following in Oracle:
> CREATE TABLE employee(id number primary key, test_number number);
> INSERT INTO employee values(1, 0.000001);
> INSERT INTO employee values(2, 0.0000001);
> COMMIT;
> Then run an import:
> sqoop import --connect jdbc:oracle:thin:@//HOSTNAME/SERVICE --username USERNAME --table EMPLOYEE --password PASSWORD --hbase-table EMPLOYEE --column-family tst --hbase-create-table
> The value for row 1 is "0.000001" while row 2 is "1E-7".

--
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