Hi @rizwan with regards to this recent issue, the fix is not yet available.
Our engineering team is performing a comprehensive audit of advanced database features (such as user-defined data types) to make sure that we’d be able to handle them across-the-board. Timeline-wise, I will be able to provide an update (with clearer timelines) around early March. After we make the fix, we’ll be sure to include it in the release notes and reply to that original issue too.
For anything else related to that (eg. you discover different data types or other features), please feel free to reply to the issue for awareness. Thanks!