TZCONVERTOR SQL import failure

In cases where the data source provides a valid date but an "unacceptable" timestamp, SQL imports fail with an error message stating "Illegal instant due to time zone offset transition."

While this issue is not uncommon across various systems, we've found it necessary to employ additional functions to overcome this limitation without sacrificing performance.

Although we attempted to use a custom TDV function to handle the error, it adversely affected performance.

The library "org.joda.time" referenced by Tibco Data Virtualization for TZCONVERTOR suggests a workaround in “https://joda-time.sourceforge.net/faq.html#illegalinstant” to support such scenarios.

Given the diverse capabilities(ETL) of Data Virtualization and the variety of data sources, extending TZCONVERTOR to accommodate these scenarios is a product added value and reduce efforts to handle(pre-processing) "unacceptable" timestamps outside of TDV. In some datasources(excel, txt files, custom systems ...) is a challenge because are generated from custom partners systems or users.