[
https://issues.apache.org/jira/browse/CALCITE-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621157#comment-16621157
]
Julian Hyde commented on CALCITE-2555:
--------------------------------------
Of course I don't have statistics. And neither do you.
For instance, I know that Hive developers use Calcite. Most of them never them
never touch Calcite, or see a Calcite plan. Some Hive developers use Calcite
for specific features, contribute to those features on occasion, but mostly it
just works, and every release they have to figure out whether the new features
are worth it, and what changes may break their assumptions.
Then there is a large pool of people who are product managers and architects.
They will never run Calcite, but they read the documentation to figure out
whether Calcite is a good fit for their product.
Expressing in SQL is just as clear to insiders, and is understandable for
people who are not insiders. I don't see a reason not to use it.
> RexSimplify: >=(true, null) could be simplified to null
> -------------------------------------------------------
>
> Key: CALCITE-2555
> URL: https://issues.apache.org/jira/browse/CALCITE-2555
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.17.0
> Reporter: Vladimir Sitnikov
> Assignee: Julian Hyde
> Priority: Major
> Labels: newbie
> Fix For: 1.18.0
>
>
> {code:java}
> @Test public void simplifyComparisonWithNull() {
> checkSimplify2(ge(trueLiteral, falseLiteral), "true", "true");
> checkSimplify2(ge(trueLiteral, nullBool), "null", "false");
> checkSimplify2(ge(nullBool, nullBool), "null", "false");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
