Hi @Brahmareddy ,

Thanks for your input. I've already tried explicitly casting the column to FLOAT as suggested, but the error still persists, and I'm stuck with the same schema merge issue. I'm not too keen on triggering a full refresh on the entire table just yet, as I'd like to explore any alternatives first.

Have you come across any other workarounds or tweaks—perhaps some configuration change or a hidden trick—that could help resolve this without resorting to a full refresh? Any further insights or suggestions would be much appreciated!