CDA parquet file not represent column as CLOB

We have found that users have a clob value in the UI but when the parquet file comes from CDA Reader it does not present the schema as a clob so the field creates as varchar and fails to import the data because there is to many characters to fit in the varchar field.  How are folks handling this scenario?