[ https://issues.apache.org/jira/browse/IMPALA-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anuj Phadke resolved IMPALA-5586. --------------------------------- Resolution: Fixed Fix Version/s: Impala 2.10.0 https://github.com/apache/incubator-impala/commit/7ccbfe47fe1a0b693f6d94ae4b1062a0e3b66e88 > Null-aware anti-join can take a long time to cancel > --------------------------------------------------- > > Key: IMPALA-5586 > URL: https://issues.apache.org/jira/browse/IMPALA-5586 > Project: IMPALA > Issue Type: Bug > Components: Backend > Affects Versions: Impala 2.10.0 > Reporter: Tim Armstrong > Assignee: Anuj Phadke > Priority: Minor > Labels: ramp-up > Fix For: Impala 2.10.0 > > > Queries with a null-aware anti-join joining on a large number of NULLs can > take a long time to cancel if threads are stuck in > PartitionedHashJoinNode::EvaluateNullProbe(). > Reproduction: > # Run this query against tpch_parquet: > {code} > select l_orderkey, l_partkey, l_suppkey, l_linenumber > from lineitem > where if(l_orderkey % 2 = 0, NULL, l_partkey) not in ( > select p_partkey > from part > where p_retailprice < l_extendedprice * l_tax) > order by 1,2,3,4 > {code} > # Cancel it > # See Impala still consuming CPU in EvaluateNullProbe() for a long time after > cancellation -- This message was sent by Atlassian JIRA (v6.4.14#64029)