Author: Thomas Tauber-Marshall <firstname.lastname@example.org>
Date: Wed Feb 8 11:18:23 2017 -0800
IMPALA-4895: Memory limit exceeded in test_outer_joins
A recent change (
IMPALA-3524) removed a 'CATCH' section for a
mem limit exceeded error because the other changes in the patch
reduced the memory requirements for that particular query and
the error was no longer being hit.
This seemed okay because the point of the test wasn't to trigger
the mem limit exceeded error, and I manually verified that the
situation was the test was addressing was still covered even
without the error being hit.
It turns out, though, that the test still hits the error in some
situations (local-filesystem and non-partitioned-aggs-and-joins
The fix is to make the test more permissive by adding '_NO_ERROR'
as one of the options in the 'CATCH: ANY_OF' section, so that it
passes whether or not the mem limit is exceeded.
Reviewed-by: Dan Hecht <email@example.com>
Tested-by: Impala Public Jenkins