Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-2022

Sqoop2: SqoopIDFUtils uses bit size instead of byteSize to check for INT/LONG/FLOAT/Double

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.99.5
    • Component/s: None
    • Labels:
      None

      Description

      From SQOOP-2018, Qian Xu found a good issue we have where we use BIT SIZE instead of BYTE size. we have to fix this.

      also see https://issues.apache.org/jira/browse/SQOOP-2023 to get more context

        Attachments

        1. SQOOP-2022-v5.patch
          46 kB
          Veena Basavaraj
        2. SQOOP-2022-v4.patch
          46 kB
          Veena Basavaraj
        3. SQOOP-2022-v3.patch
          43 kB
          Veena Basavaraj
        4. SQOOP-2022-v1.patch
          11 kB
          Veena Basavaraj
        5. SQOOP-2022.patch
          11 kB
          Veena Basavaraj

          Issue Links

          is a clone of

          Bug - A problem which impairs or prevents the functions of the product. SQOOP-2018 GenericJDBCConnector SqlTypes INTEGER should be set 4 bytes

          • Major - Major loss of function.
          • Resolved
          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. SQOOP-2027 Sqoop2: SqoopIDFUtils handling of decimal need to be fixed

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link RB

            Activity

              People

              • Assignee:
                vybs Veena Basavaraj
                Reporter:
                vybs Veena Basavaraj
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: