Upgrade caused column type change resulting in profiler error about openmetadata HOT 4 CLOSED

@pmbrull this should be part of 1.3.2, if its a regression

from openmetadata.

@ayush-shah any updates here?

from openmetadata.

@harshach will be validating the same tomorrow, this seems to be an issue where we are safely evaluating an expression node and assigning a data type, but when it comes to profiler, on running metrics over DataFrames the data comes in as String because of pandas' default property, will validate the same and push a fix tomorrow

from openmetadata.

Quick update here: we can assign the types to dataframe which previously were by default stored as object, this brings us to bunch of errors around unique and distinct count computation won't work as expected, we will need to serialize the same and compute over it

Targeted to be up on this Tuesday

from openmetadata.