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
[SPARK-13031] [SQL] cleanup codegen and improve test coverage #10977
Conversation
What's the bug? |
When there is no aggregate functions, it did not generate the output using resultExpression, which have only literals (I was mislead by the comment in AggregateIterator). |
Thanks - can you add a test case that would catch this? In the long run, we should beef up our own test coverage and don't want to rely on HiveCompatibilitySuite. |
The way we managed HiveCompatibilitySuite is actually better than our unit tests (sql query and golden results in text format). Even if we don't want to be compatible with Hive, it's still good to have those tests (don't call them HiveCompatibilitySuite), and also managed in similar way. |
Sure it's a good idea to use that golden file infrastructure. Given we don't have that yet, can you just add a test case? |
The issue here is that we want test cases that are targeted for specific problems, and the Hive ones are not (they are just a giant blackbox we took to bootstrap coverage, and not to mention that a targeted test helps you catch problems with aggregations earlier without rerunning the entire Hive suite). |
Test build #50351 has finished for PR 10977 at commit
|
This reverts commit 70a7c7e.
@rxin Added. |
LGTM |
Test build #50359 has finished for PR 10977 at commit
|
Test build #2473 has finished for PR 10977 at commit
|
I've merged this. |
This PR re-open #10944 and fix the bug.