-
Notifications
You must be signed in to change notification settings - Fork 240
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] test_csv_infer_schema_timestamp_ntz fails #9325
Comments
Tests were introduced in #9159. cc: @andygrove |
There is a regression or change in behavior in Spark 3.5.0. Here is a repro case.
Both 3.4.0 and 3.5.0 produce the same CSV file:
The read works fine with 3.4.0 and produces this result:
The read in 3.5.0 fails with:
This only fails when |
Another observation is that this works fine with |
I filed a bug against Spark: |
There is also a bug in the plugin: |
The Spark bug is fixed in 3.5.1 |
I can confirm that this test passes on Spark-3.5.1 |
I can confirm that this is not reproducible on Spark 3.5.0 either. |
[jira] [Updated] (SPARK-44025) CSV Table Read Error with CharType(length) column https://www.mail-archive.com/[email protected]/msg349889.html I'm getting similar issue after upgrading from Spark 3.3.0 to 3.5.0. and not even working in 3.5.1. Please help me fix the issue. Driver stacktrace: My DB tables : (NOTE : I'm getting issue only for char column types. )CREATE TABLE CREATE TABLE My Test Codepublic class TestTimeZone {
} Data In CSV file"operator" same is working with spark 3.3.0 +--------+ |
@marreddy I don't see anything in the error that is related to the RAPIDS plugin for Apache Spark. You appear to be running on windows and we don't support windows at all, not to mention the stack trace does not include anything related to this project. You might want to ask on the apache-spark users mailing list or one of the other resources for asking questions https://spark.apache.org/community.html |
The following tests failed in a recent integration test run for 23.10:
Some of the tests failed like:
Others failed with:
The text was updated successfully, but these errors were encountered: