hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-21231) HiveJoinAddNotNullRule support for range predicates
Date Wed, 27 Mar 2019 19:58:00 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 27/Mar/19 19:57
            Start Date: 27/Mar/19 19:57
    Worklog Time Spent: 10m 
      Work Description: miklosgergely commented on pull request #580: HIVE-21231 HiveJoinAddNotNullRule
support for range predicates
URL: https://github.com/apache/hive/pull/580
 
 
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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

            Worklog Id:     (was: 219561)
            Time Spent: 10m
    Remaining Estimate: 0h

> HiveJoinAddNotNullRule support for range predicates
> ---------------------------------------------------
>
>                 Key: HIVE-21231
>                 URL: https://issues.apache.org/jira/browse/HIVE-21231
>             Project: Hive
>          Issue Type: Improvement
>          Components: CBO
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Miklos Gergely
>            Priority: Major
>              Labels: newbie, pull-request-available
>         Attachments: HIVE-21231.01.patch, HIVE-21231.02.patch, HIVE-21231.03.patch, HIVE-21231.04.patch,
HIVE-21231.05.patch, HIVE-21231.06.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> For instance, given the following query:
> {code:sql}
> SELECT t0.col0, t0.col1
> FROM
>   (
>     SELECT col0, col1 FROM tab
>   ) AS t0
>   INNER JOIN
>   (
>     SELECT col0, col1 FROM tab
>   ) AS t1
> ON t0.col0 < t1.col0 AND t0.col1 > t1.col1
> {code}
> we could still infer that col0 and col1 cannot be null for any of the inputs. Currently
we do not.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message