Description
Is there an existing issue for this?
- I have searched the existing issues
Category of Bug / Issue
Converter bug
Current Behavior
We are encountering an issue where Oracle DDL scripts, specifically CHAR(2) data types, are not being correctly converted to STRING in Databricks SQL when using the latest version of Lakebridge. We've observed that NUMBER data types are successfully converting to BIGINT, and VARCHAR to STRING, but CHAR columns are being retained as CHAR in the converted script, which is not the desired behavior for Databricks.
Could you please provide an update on whether there are any recent developments or known issues with Lakebridge regarding the conversion of CHAR data types to STRING in Databricks SQL, or if the development team is actively working on a resolution for this specific conversion challenge?
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output or Exception details
Sample Query
Operating System
Windows
Version
latest via Databricks CLI