You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ankit Singhal (JIRA)" <ji...@apache.org> on 2018/03/06 17:49:00 UTC
[jira] [Updated] (HIVE-18873) Skipping predicate pushdown for MR
silently at HiveInputFormat can cause storage handlers to produce erroneous
result
[ https://issues.apache.org/jira/browse/HIVE-18873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ankit Singhal updated HIVE-18873:
---------------------------------
Summary: Skipping predicate pushdown for MR silently at HiveInputFormat can cause storage handlers to produce erroneous result (was: Skipping predicate pushdown silently at HiveInputFormat can cause storage handlers to produce erroneous result)
> Skipping predicate pushdown for MR silently at HiveInputFormat can cause storage handlers to produce erroneous result
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-18873
> URL: https://issues.apache.org/jira/browse/HIVE-18873
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Priority: Major
> Fix For: 3.0.0
>
>
> {code:java}
> // 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;
> }
> {code}
> I believe this needs to be handled at OpProcFactory so that hive doesn't believe that predicate is handled by storage handler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)