Temporary get the workaround back for TIMESTAMP field in jdbc.

Author: shunping

sdks/python/apache_beam/io/external/xlang_jdbcio_it_test.py

@@ -36,6 +36,8 @@
 from apache_beam.testing.test_pipeline import TestPipeline
 from apache_beam.testing.util import assert_that
 from apache_beam.testing.util import equal_to
+from apache_beam.typehints.schemas import LogicalType
+from apache_beam.typehints.schemas import MillisInstant
 from apache_beam.utils.timestamp import Timestamp
 
 # pylint: disable=wrong-import-order, wrong-import-position, ungrouped-imports
@@ -239,6 +241,10 @@ def test_xlang_jdbc_write_read(self, database):
 
     config = self.jdbc_configs[database]
 
+    # Register MillisInstant logical type to override the mapping from Timestamp
+    # originally handled by MicrosInstant.
+    LogicalType.register_logical_type(MillisInstant)
+
     with TestPipeline() as p:
       p.not_use_test_runner_api = True
       _ = (
@@ -349,6 +355,10 @@ def custom_row_equals(expected, actual):
               classpath=config['classpath'],
           ))
 
+    # Register MillisInstant logical type to override the mapping from Timestamp
+    # originally handled by MicrosInstant.
+    LogicalType.register_logical_type(MillisInstant)
+
     # Run read pipeline with custom schema
     with TestPipeline() as p:
       p.not_use_test_runner_api = True