[SQOOP-2027] Sqoop2: SqoopIDFUtils handling of decimal need to be fixed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.99.5
• Assignee: Veena Basavaraj
• Reporter: Veena Basavaraj
• Created: 20/Jan/15 20:14
• Updated: 23/Jan/15 20:48
• Resolved: 23/Jan/15 20:00

Description

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

public class Decimal extends AbstractNumber {

  /**
   * Number of valid numbers.
   */
  private Long precision;

  /**
   * Number of decimal places.
   */
  private Long scale;

IDF java handling today is very lame!

  public static Object toDecimal(String csvString, Column column) {
    return new BigDecimal(csvString);
  }

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

Issue Links

• is a clone of: SQOOP-2022 Sqoop2: SqoopIDFUtils uses bit size instead of byteSize to check for INT/LONG/FLOAT/Double
• is cloned by: SQOOP-2035 Sqoop2: KiteConnector From side need to send BigDecimal for decimal type and JODA for date type in Object array
• links to: RB