mataralhawiti commented on issue #35738: URL: https://github.com/apache/beam/issues/35738#issuecomment-3237938059
hey @shunping apologies for the late response. #### redacted versison our pipeline, can be found here: https://gist.github.com/mataralhawiti/e7354d3ed7bd076ee1289787adde3fb1 ### Here what I've tried so far: workaround = force the registration of JDBC logical types before pipeline starts ```LogicalType.register_logical_type(MillisInstant)``` - #### print out - Beam 2.67 - without workaround : ``` from apache_beam.typehints.schemas import LogicalType logging.info("***************** - : %s", LogicalType._known_logical_types.get_logical_type_by_urn('beam:logical_type:javasdk_date:v1')) from apache_beam.io.jdbc import JdbcDateType logging.info("############ - : %s", LogicalType._known_logical_types.get_logical_type_by_urn('beam:logical_type:javasdk_date:v1')) with beam.Pipeline(options=pipeline_options) as p: pass # output INFO:root:***************** - : <class 'apache_beam.io.jdbc.JdbcDateType'> INFO:root:############ - : <class 'apache_beam.io.jdbc.JdbcDateType'> ``` - #### Run the pipeline - Beam 2.67 - without workaround Failed with the same original error. - #### Run the pipeline - Beam 2.67 - workaround : Failed with the same original error. - #### Run the pipeline - Beam **2.64** (old version) - with workaround : Run successfully -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
