You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Abhay (Jira)" <ji...@apache.org> on 2022/07/30 00:42:00 UTC

[jira] [Comment Edited] (HIVE-26438) Remove unnecessary optimization in canHandleQbForCbo() method

    [ https://issues.apache.org/jira/browse/HIVE-26438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573188#comment-17573188 ] 

Abhay edited comment on HIVE-26438 at 7/30/22 12:41 AM:
--------------------------------------------------------

[~zabetak] Can you review this change?

cc: [~jfs] 


was (Author: achennagiri):
[~zabetak] Can you review this change?

> Remove unnecessary optimization in canHandleQbForCbo() method
> -------------------------------------------------------------
>
>                 Key: HIVE-26438
>                 URL: https://issues.apache.org/jira/browse/HIVE-26438
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Abhay
>            Assignee: Abhay
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This ticket is an improvement on https://issues.apache.org/jira/browse/HIVE-26426.  The canHandleQbForCbo() checks whether Calcite handle the query or not and it returns null if the query can be handled; non-null reason string if it cannot be. 
> But currently, it returns an empty string if INFO Log is not enabled. This is probably a performance optimization that is not needed and can be simplified. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)