-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Failing Test]: Various TPC-DS queries throw NPEs using SparkRunner #28256
Comments
After a quick investigation with Interesting that seems it affects only Spark RDD runner with some types of pipelines, though there are no failures at VR tests. |
The CLI command to reproduce the issue:
|
@aromanenko-dev thanks for the root cause analysis. Do you use Beam schemas in TPCDS implementation ? |
@echauchot Yes, CSV or Parquet schema is converted into Beam schema to be able executed with Beam SQL. |
Full stacktrace:
|
yes timestamp is null in some cases |
Can be reproduced using CSV input files ? |
Yes, I have the same issue with CSV files. |
getting a different exception on |
ah yes, getting the NPE if I apply #28819 |
CC: @je-ik Since you worked on Group/Combine transform translations for original Spark RDD runner, could you take a look? Is it a Spark runner issue? |
Oh my, this is an old history. :) I created #29162, it seems to pass locally all tests and validatesRunner suites, can you try this patch? |
@je-ik Thanks! I quickly tested it with a couple of TPC-DS queries that were failing and it passes now. So, I think if ValidateRunner tests pass, we have to merge this fix. Though, it's strange that this issue was not caught by any of VR test running with SparkRunner |
Yes, I'd only like to walk the code again to be sure exactly what might be the impact of the fix. Yes, it is strange it was not caught by VR tests. I'll look into it. |
I don't have a background about the TPC-DS queries, do we have the input data that I can pass to the gradle command to reproduce the NPEs (the |
Ah, I see, |
I'm unable to reproduce the error locally. Complete command-line:
All attempts pass as |
@je-ik Hmm, interesting. A couple of notes:
|
Just to re-run the test multiple times to reveal any flakes.
I tried both, same results. |
Ah, I see. I need to remove the |
Yes, I'll fix this |
I'm obviously doing something wrong. Running the command like this
I get a success
but the outputs are empty
Accessing the bucket seems to be working fine, e.g.:
|
If the results are empty then it's very likely that the input was empty too (for some reasons) - |
Same results. Runs OK, but empty outputs. |
Update: I removed the last slash, and it failed! :)
command-line:
And I got the NPE:
|
I created an issue for that #29198 |
What happened?
Various TPC-DS queries started throwing NPEs with the SparkRunner some while back (see here):
Without looking further into the underlying root cause, this seems to be related to #27617.
Issue Failure
Failure: Test is flaky
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components
The text was updated successfully, but these errors were encountered: