[
https://issues.apache.org/jira/browse/HIVE-29765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102117#comment-18102117
]
Stamatis Zampetakis commented on HIVE-29765:
--------------------------------------------
After checking the code the unparse method may not be relevant only for the
Optimized SQL entry but also for pushing computations to the JDBC storage
handler. If that is true then if we start generating NOT BETWEEN expressions
fixing the unparse method is critical for getting correct results when we are
pushing such expressions to the JDBC storage handler.
> 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)
