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

Fix OracleManager to apply localTimeZone correctly in case of Date objects too

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

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

      Description

      In the current implementation OraOop and OracleManager are different from the POV of setting sessionTimeZone in oracle.

      OracleManager does not set the TimeZone in java, and neither the default timeZone on the Oracle connection.

      Thus when the local timezone realted data is retrieved by Sqoop as not a String object, but as a Date, the timeZone information is lost, and this could cause confusion/bogus behaviour on user side.

      The goal is to get inline the two implementation.

        Attachments

          Activity

            People

            • Assignee:
              maugli Attila Szabo
              Reporter:
              maugli Attila Szabo

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment