[jira] [Work logged] (HIVE-25852) Introduce IN clauses at the very end of query planning

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-25852?focusedWorklogId=744671&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-744671 ]

ASF GitHub Bot logged work on HIVE-25852:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Mar/22 00:17
            Start Date: 20/Mar/22 00:17
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #2928:
URL: https://github.com/apache/hive/pull/2928#issuecomment-1073134928


   This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
   Feel free to reach out on the dev@hive.apache.org list if the patch is in need of reviews.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscribe@hive.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 744671)
    Time Spent: 0.5h  (was: 20m)

> Introduce IN clauses at the very end of query planning
> ------------------------------------------------------
>
>                 Key: HIVE-25852
>                 URL: https://issues.apache.org/jira/browse/HIVE-25852
>             Project: Hive
>          Issue Type: Bug
>          Components: CBO
>    Affects Versions: 4.0.0
>            Reporter: Alessandro Solimando
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Calcite "explodes" IN clauses into the equivalent OR form, and therefore it does not handle such clauses in most of the codebase (notably in _RexSimplify_).
> In Hive, the same happens, but _HivePointLookupOptimizerRule_ re-introduces IN clauses, and it happens in _applyPreJoinOrderingTransforms_ phase, which is pretty early and which mixes several other rules which might not fully support IN (notably, _HiveReduceExpressionsRule_ which is based on _RexSimplify_).
> The problem will become even harder in later versions of Calcite (current is 1.25) based on SARG, which does not support IN clauses.
> IN clauses can be converted into efficient runtime operators, we therefore want to keep them in the final plan, intuitively we just want this translation to happen in a later step, in order to leave the rest of the codebase (Hive and Calcite) unaware of IN clauses.
> The goal of the ticket is as follows:
> # re-convert the output expression of _HivePointLookupOptimizerRule_ into the OR form (keep the logic as-is to benefit from the rule)
> # add a rule, in the last step of the planning process, that only converts eligible OR expressions into IN clauses



--
This message was sent by Atlassian Jira
(v8.20.1#820001)