Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-6143

Oracle TIMESTAMP WITH TIME ZONE is emitted as GMT during snapshot rather than the specified TZ


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.1.3.Final, 2.2.0.Alpha3
    • 1.9.7.Final, 2.0.1.Final, 2.1.2.Final, 2.2.0.Alpha2
    • oracle-connector
    • None

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      What behaviour do you expect?

      When inserting a a record into a table with a TIMESTAMP WITH TIME ZONE column, the format of the timestamp is different between the snapshot and streaming records. These values should be identical if the inserted values are identical.

      <Your answer>

      What behaviour do you see?

      With the insert value 2010-12-01 23:12:56.788 -12:44, the snapshot emits a value of 2010-12-02T11:56:56.788000Z while the streaming phase emits a value of 2010-12-01T23:12:56.788-12:44.

      Per the documentation, a TIMESTAMP WITH TIME ZONE field should be emitted as:

      A string representation of a timestamp with timezone information.

      While neither value in either phase is incorrect for the timepoint, there is no reason that these should be formatted differently for the same value

            ccranfor@redhat.com Chris Cranford
            ccranfor@redhat.com Chris Cranford
            0 Vote for this issue
            4 Start watching this issue