Open scottiegarcia opened 11 months ago
@taylorfturner Running the latest release against this code snippet still errors. For what its worth, the change from @SchadtJ gets this sample script to work fine, although I haven't tested past that
I thought another change that was recently merged addressed this, but I might have been mistaken.
My change is just a type-cast, so that we remove the categorical dtype when we calculate precision. Doing this felt somewhat hacky. However, since it's done for data that is only used in the precision calculation, it seems fine.
I'm still getting familiar with the codebase, but one thing I was wondering is does it make sense to output precision if we are using categorical data?
My change is just a type-cast, so that we remove the categorical dtype when we calculate precision. Doing this felt somewhat hacky. However, since it's done for data that is only used in the precision calculation, it seems fine.
Got it -- yeah, slightly hacky but I see what you're doing for sure, @SchadtJ
General Information:
Describe the bug:
On occasion, some categorical columns produce the following error when profiling
To Reproduce:
This error is coming from a categorical variable detailing the year + month that the data is coming from. Weirdly enough, we are only seeing this error occur in October. If you update the
202210
value to202211
then it profiles successfully. And updating to202110
also errors.Expected behavior:
Profile these specific categorical columns successfully.
Screenshots:
Additional context: