New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: '<=' not supported between instances of 'int' and 'str' if dask.dataframe use map_partitions for twice #8085
Comments
The full traceback is as follows:
If I add str col names on the original dataframe, then the program will run successfully. I found that it seems try to get min value from new column names I think this is a bug of dask...does anyone who have some commments of this? |
Thanks for reporting this issue and providing a nice reproducer @df19900725. Indeed it looks like our logic here Lines 5220 to 5233 in fb4e90a
isn't robust to mixed |
Sure. I will try to fix this. |
@df19900725 checking in here, did you have the chance to take a look at this, if so, would you like to open a PR with the fix? |
@ncclementi I find it was not easy to fix because if that |
Closed via #9485 |
What happened: dask.DataFrame use map_partitions to add a new column. But the first time it will be successfully transformed, but it will throw
TypeError: '<=' not supported between instances of 'int' and 'str'
for the second timeWhat you expected to happen: it should be get correct new column for the second time
Minimal Complete Verifiable Example:
Anything else we need to know?:
The first and the second 'print' will get correct result, however, the last one throws error:
Environment:
The text was updated successfully, but these errors were encountered: