-
Notifications
You must be signed in to change notification settings - Fork 914
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
[BUG] Inconsistence issue between pandas and cudf #17654
Comments
Thank you for raising this issue. However, this bug is already fixed as of (cudfdev) pgali@viking-prod-206:/raid/pgali/cudf$ git diff
diff --git a/test.py b/test.py
index 3e0115caf8..6f0ace419b 100644
--- a/test.py
+++ b/test.py
@@ -29,8 +29,8 @@ def demonstrate_merge_issue():
pandas_long_select_num = pandas_long_select_num.rename(columns={'symbol': 'long_num'}).reset_index()
print("pandas long_select_num columns:", pandas_long_select_num.columns)
- pandas_short_df = pandas_short_df.merge(pandas_long_select_num, on='time', how='left')
- print("pandas short_df columns after merge:", pandas_short_df.columns)
+ pandas_short_df_merged = pandas_short_df.merge(pandas_long_select_num, on='time', how='left')
+ print("pandas short_df columns after merge:", pandas_short_df_merged.columns)
# Use cudf to create DataFrame
cudf_long_df = cudf.DataFrame.from_pandas(pandas_long_df) output:
|
thank you so much!! |
Describe the bug
When I switch from pandas to cudf, I find a inconsistence issue in merge() function.
Running the same code in pandas and in cudf, I got different results.
Steps/Code to reproduce bug
Demo code:
Result:
Expected behavior
I think running the same operation should get the same result in these two packages, so that more devs can easily switch to cudf to speed up computation.
I don't really know detailed code of cudf, and I don't know if it's an expected behavior. Thanks!
Environment overview (please complete the following information)
Environment details
Click here to see environment details
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: