-
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-1460351: [v1.17 - v1.18] Can't create dataframe "withcolumn" when column value can have varying length #1725
Comments
Here is the stack trace: /br135_test.py:44: ../../../../miniconda3/envs/venv311/lib/python3.11/site-packages/snowflake/snowpark/_internal/telemetry.py:145: in wrap exp = <snowflake.snowpark._internal.analyzer.expression.CaseWhen object at 0x7f283d6541d0>
E snowflake.snowpark.mock.exceptions.SnowparkLocalTestingException: CaseWhen expressions have conflicting data types: StringType(13) != StringType(28) ../../../../miniconda3/envs/venv311/lib/python3.11/site-packages/snowflake/snowpark/mock/_plan.py:2003: SnowparkLocalTestingException |
thanking for reaching out! we will take a look at this ASAP |
hey @jeromesubs , we have fixed the issue in the latest release 1.19.0. please upgrade and let us know how it goes! |
Please answer these questions before submitting your issue. Thanks!
What version of Python are you using?
Python 3.11.8 (main, Feb 26 2024, 21:39:34) [GCC 11.2.0]
What are the Snowpark Python and pandas versions in the environment?
pandas==2.2.1
snowflake-snowpark-python==1.18.0
What did you do?
Create a dataframe
Create a second dataframe adding a new column with conditions, the column value can be one of two string of different length
What did you expect to see?
I would expect the second dataframe to be created without error
Here is the code:
The show command is where the test crash, but even by debugging and looking at df_result properties, you can see the error:
"CaseWhen expressions have conflicting data types: StringType(13) != StringType(28)"
The text was updated successfully, but these errors were encountered: