You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/10/07 02:32:00 UTC
[jira] [Work logged] (HIVE-24209) Incorrect search argument
conversion for NOT BETWEEN operation when vectorization is enabled
[ https://issues.apache.org/jira/browse/HIVE-24209?focusedWorklogId=496266&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-496266 ]
ASF GitHub Bot logged work on HIVE-24209:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Oct/20 02:31
Start Date: 07/Oct/20 02:31
Worklog Time Spent: 10m
Work Description: jcamachor merged pull request #1535:
URL: https://github.com/apache/hive/pull/1535
----------------------------------------------------------------
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: 496266)
Time Spent: 20m (was: 10m)
> Incorrect search argument conversion for NOT BETWEEN operation when vectorization is enabled
> --------------------------------------------------------------------------------------------
>
> Key: HIVE-24209
> URL: https://issues.apache.org/jira/browse/HIVE-24209
> Project: Hive
> Issue Type: Bug
> Components: Vectorization
> Reporter: Ganesha Shreedhara
> Assignee: Ganesha Shreedhara
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-24209.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We skipped adding GenericUDFOPNot UDF in filter expression for NOT BETWEEN operation when vectorization is enabled because of the improvement done as part of HIVE-15884. But, this is not handled during the conversion of filter expression to search argument due to which incorrect predicate gets pushed down to storage layer that leads to incorrect splits generation and incorrect result.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)