Skip to content

Conversation

@rxin
Copy link
Contributor

@rxin rxin commented Aug 31, 2015

They don't bring much value since we now have better unit test coverage for hash joins. This will also help reduce the test time.

@vanzin
Copy link
Contributor

vanzin commented Aug 31, 2015

I have a different approach in #8437 (which doesn't get rid of the tests here).

@rxin
Copy link
Contributor Author

rxin commented Aug 31, 2015

@vanzin we can have both, can't we? I don't think HashJoinCompatibilitySuite is testing much here, given we added more tests for hash joins. In general, operator tests should be done not at the end-to-end level. The Hive tests are great in the beginning to beef up our test coverage with little effort, but their values are decreasing everyday.

@vanzin
Copy link
Contributor

vanzin commented Aug 31, 2015

Sure, I was just wondering because the reasoning on the bug is "to make the tests run faster" and not "the test doesn't really add value".

@SparkQA
Copy link

SparkQA commented Sep 1, 2015

Test build #41843 has finished for PR 8542 at commit 46b7112.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@asfgit asfgit closed this in d65656c Sep 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants