Hey Hung, before dropping the table, there are a few other things you could try. One option is to point your DLT logic to a new table with the updated FLOAT column, just to confirm everything works with the new schema—this helps isolate whether the issue is with the existing table’s metadata. You could also try adding .option("mergeSchema", "true") to your writeStream if you’re using custom logic (though in DLT it's sometimes limited). Another thing to check is whether any expectations or schema hints are applied—if so, try removing or updating them to match the new FLOAT type. You can even add a schema_hints argument in the @Dlt.table decorator to force it to recognize reference_score as a FLOAT. Sometimes these little tweaks can help DLT adjust without a full reset. Let me know if you want help testing one of these approaches!

Regards,

Brahma