-RE: [jira] [Created] (SQOOP-830) HBase import formatting BigDecimal inconsistently
I was thinking of changing this to use "toPlainString()" instead of "toString()" on BigDecimals as it seems confusing to have some numbers stored as normal decimals and other stored in scientific notation.
Does anyone have any input on this? Do you think this would break anyone's processes? It seems like either one can be converted to a BigDecimal using the constructor so I don't think it will break anything. Is anyone storing BigDecimals in HBase and has any input?
Dell | R&D, Quest Software
office +61 3 9811 8082
Quest Software is now part of Dell
From: David Robson (JIRA) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 16 January 2013 10:12 AM
To: [EMAIL PROTECTED]
Subject: [jira] [Created] (SQOOP-830) HBase import formatting BigDecimal inconsistently
David Robson created SQOOP-830:
Summary: HBase import formatting BigDecimal inconsistently
Issue Type: Bug
Reporter: David Robson
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