Sqoop
  1. Sqoop
  2. SQOOP-906

Sqoop is always calling ConnectionManager.datetimeToQueryString with TIMESTAMP column type

    Details

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

      Description

      One user on CDH mailing list has risen issue with incremental import using lastmodified mode. Sqoop seems to be generating queries including TO_TIMESTAMP function even for column that is defined as Types.DATE. This is causing issues with Oracle Connector. The connector seems to be correctly written as appropriate OracleManager.datetimeToQueryString seems to be expected condition based on the column type. Unfortunately the caller code is always passing in Types.TIMESTAMP value instead of the original value. I think that we should fix that.

      1. SQOOP-906.txt
        5 kB
        Raghav Kumar Gautam
      2. SQOOP-906.txt
        13 kB
        Raghav Kumar Gautam
      3. SQOOP-906.txt
        11 kB
        Raghav Kumar Gautam
      4. SQOOP-906.4.txt
        14 kB
        Raghav Kumar Gautam

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Raghav Kumar Gautam
              Reporter:
              Jarek Jarcec Cecho
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development