Hey Sungwoo!
On 11/12/20 10:23 AM, Sungwoo Park wrote:
Hi Zoltan,
I used the same hive-site.xml for the previous test (which was okay) and
the new test (which failed), so my guess is that it is perhaps due to a
commit since the previous test. Let me try later to identify the commit
that fails query 14, with the hope that identifying such a commit might be
useful in debugging.
That would definetly help - if you could share the 2 commit hashes; it might be
possible that we could guess it from the commit message or something.
Another question: is HIVE-24360 part of a solution to the problem of
hive.optimize.shared.work.dppunion?
I have tried the latest commit (which includes HIVE-24360) using the TPC-DS
benchmark, and it seems like the problem still exists.
Yes, HIVE-24360 should have fixed that - do you still see an exception coming
from tez-api reporting edge errors?
I will also pick these changes for a smaller benchmark run soon...but I'm not running any right now. Could also note for which query you've seen the exception - so that I
could also check it.
Could you please open a jira about this - and add the actual exception
trace/etc if available?
cheers,
Zoltan
Cheers,
--- Sungwoo
On Mon, Nov 9, 2020 at 6:18 PM Zoltan Haindrich <k...@rxd.hu> wrote:
Hey Sungwoo!
Regarding Q14 / "java.lang.RuntimeException: equivalence mapping violation"
From the stack trace you shared it seems like the mapper have already
seen both the filter and the ast node earlier - and they are in separate
mapping groups. (Which is
unfortunate) I think it won't be simple to track that down - it will
definetly need some debugging.
The best would be to have a repro query for it...
note: we already run q14 in TestTezPerf*Driver - could it might be
possible that we've disabled some features in the hive-site.xml for these
tests; and that's why we
haven't seen it before?
cheers,
Zoltan
