[
https://issues.apache.org/jira/browse/HIVE-18873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599033#comment-16599033
]
Josh Elser commented on HIVE-18873:
-----------------------------------
{quote}I am not sure why Hive pushes down such predicates to storage handler.
{quote}
Gotcha. Sorry, I didn't get that the first time.
{quote}hive has already made sure if the predicate couldn't be pushed it will
apply the whole predicate itself therefore it is safe for Accumulo handler to
ignore it.
{quote}
Trying to understand... we want to apply whatever predicates we can in a
storage handler, but continue quietly if the storage handler cannot process
one? Under the assumption that Hive is ensuring the results are accurate
anyways? (e.g. we'd want to check that all storage handlers work this way)
> 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
> Attachments: HIVE-18873.2.patch, HIVE-18873.2_reattach.patch,
> HIVE-18873.3.patch, HIVE-18873.patch
>
>
> {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)
