[
https://issues.apache.org/jira/browse/HIVE-29765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101354#comment-18101354
]
Ruben Q L commented on HIVE-29765:
----------------------------------
Thanks for the info [~zabetak] !
Even if we remove the "OPTIMIZED SQL entry from EXPLAIN EXTENDED", just for the
sake of correctness, shouldn't we make sure that the "unparse" method is valid?
I guess it wouldn't harm to merge the patch.
> HiveBetween#unparse ignores negated flag
> ----------------------------------------
>
> Key: HIVE-29765
> URL: https://issues.apache.org/jira/browse/HIVE-29765
> Project: Hive
> Issue Type: Bug
> Reporter: Ruben Q L
> Assignee: Ruben Q L
> Priority: Major
> Labels: pull-request-available
>
> HiveBetween first operand is a boolean "negated" flag. When it is disabled
> (default) the operator represents a standard BETWEEN. When it is enabled, the
> operator represents a NOT BETWEEN. However, in the HiveBetween#unparse method
> the flag is not considered, so in all cases it is unparsed as a "BETWEEN"
> (even when the flag is activated).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
