[
https://issues.apache.org/jira/browse/SQOOP-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-2035:
-----------------------------------
Description: At this point, we do not see the JDBC Connector sending
BigDecimal for objects that are Sqoop Decimal type, as we prescribe JODA for
date objects, we need BigDecimal for decimal objects. (was: we need to handle
scale and precision and make sure we instantiate the bigDecimal correctly
We also need to make scale and precision mandatory to avoid confusion for
connectors while they map their types
{code}
public class Decimal extends AbstractNumber {
/**
* Number of valid numbers.
*/
private Long precision;
/**
* Number of decimal places.
*/
private Long scale;
{code}
IDF java handling today is very lame!
{code}
public static Object toDecimal(String csvString, Column column) {
return new BigDecimal(csvString);
}
{code}
3. there is no single unit test today with the values for precision and scale,
so we need to define what those values are for Long )
> Sqoop2: JDBC Connector and KiteConnector need to send BigDecimal for decimal
> type in Object array
> --------------------------------------------------------------------------------------------------
>
> Key: SQOOP-2035
> URL: https://issues.apache.org/jira/browse/SQOOP-2035
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
>
> At this point, we do not see the JDBC Connector sending BigDecimal for
> objects that are Sqoop Decimal type, as we prescribe JODA for date objects,
> we need BigDecimal for decimal objects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
