-
Notifications
You must be signed in to change notification settings - Fork 116
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
SNOW-1529368: JOIN followed by SELECT doesn't work as expected #1899
Comments
Diagnosis: Table specific columns don’t need a random prefix as they don't cause name conflicts. |
I played around with this a little and find this only occurrs when at least one side of the join is a Table instead of a DataFrame. |
Found that this specific issue is due to both tables having the same name. Additionally, it also occurrs when we have a column name conflict and we're missing an |
I think there's still a behavior difference with live connection in that live connection doesn't error out due to the lack of a |
The behavior difference is that live connection calls out the error more clearly:
the emulator only says this:
|
thanks @sfc-gh-pkommini for the updates. closing the issue as this is not a bug. |
Please answer these questions before submitting your issue. Thanks!
3.10
Script with
local_testing
session:Script with live connection:
I expect to see table with selected column, instead I get an error and when I print
df_join.columns
, this is what I get. But this is not what we expect. Let me know if I'm missing something here.Meanwhile, live connection's output is:
The text was updated successfully, but these errors were encountered: