[HIVE-18873] Skipping predicate pushdown for MR silently at HiveInputFormat can cause storage handlers to produce erroneous result

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 4.0.0-alpha-1
• Assignee: Ankit Singhal
• Reporter: Ankit Singhal
• Created: 06/Mar/18 17:34
• Updated: 17/Nov/22 08:54
• Resolved: 05/Sep/18 22:47

Description

// disable filter pushdown for mapreduce when there are more than one table aliases,

    // since we don't clone jobConf per alias

    if (mrwork != null && mrwork.getAliases() != null && mrwork.getAliases().size() > 1 &&

      jobConf.get(ConfVars.HIVE_EXECUTION_ENGINE.varname).equals("mr")) {

      return;

    }

I believe this needs to be handled at OpProcFactory so that hive doesn't believe that predicate is handled by storage handler.

Issue Links

• is caused by: HIVE-15680 Incorrect results when hive.optimize.index.filter=true and same ORC table is referenced twice in query
• is related to: HIVE-20500 Accumulo query failing