Jim Apple has posted comments on this change. Change subject: IMPALA-4904,IMPALA-4914: whitelist workload "targeted-stress" for exhaustive tests ......................................................................
Patch Set 3: (2 comments) http://gerrit.cloudera.org:8080/#/c/6002/3//COMMIT_MSG Commit Message: Line 7: IMPALA-4904,IMPALA-4914: whitelist workload "targeted-stress" for exhaustive tests > Can you please suggest a meaningful header that summarizes the patch that a I agree this loses some information, but I think it's the right tradeoff: IMPALA-4904,IMPALA-4914: add targeted-stress to exhaustive tests http://gerrit.cloudera.org:8080/#/c/6002/3/tests/stress/test_ddl_stress.py File tests/stress/test_ddl_stress.py: Line 59 > No change in ordering of DDL calls. The CREATE DATABASE that is executed no Given the number of catalog race conditions we tend to see, I think it is possible that this changes the test meaning. My feeling is that it would be good to test both things: multiple tables in one DB and multiple tables each with its own DB. If this method and TEST_IDS were left unchanged, would the test fail? -- To view, visit http://gerrit.cloudera.org:8080/6002 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ie6bd5bbd380e636d680368e908519b042d79dfec Gerrit-PatchSet: 3 Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-Owner: Michael Brown <mi...@cloudera.com> Gerrit-Reviewer: David Knupp <dkn...@cloudera.com> Gerrit-Reviewer: Jim Apple <jbapple-imp...@apache.org> Gerrit-Reviewer: Michael Brown <mi...@cloudera.com> Gerrit-Reviewer: Tim Armstrong <tarmstr...@cloudera.com> Gerrit-HasComments: Yes
