[
https://issues.apache.org/jira/browse/CALCITE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256715#comment-14256715
]
Mehant Baid commented on CALCITE-547:
-------------------------------------
Can you please add test for this case?
- For testing I am planning to add a query which looks like: "select t.a.b
from foo" and check the return type of the expression (t.a.b) for nullability.
However could you please point me to an example where I can use ITEM operators
whose SqlTypeName is ANY. Most of the examples I found were using values(1) as
the data source.
Can you please move typeFactory to the next line so typeFactory and
createSqlType are on the same line?
- Done.
> Fix return type of item operator when operand type is not known
> ---------------------------------------------------------------
>
> Key: CALCITE-547
> URL: https://issues.apache.org/jira/browse/CALCITE-547
> Project: Calcite
> Issue Type: Bug
> Reporter: Mehant Baid
> Assignee: Mehant Baid
> Attachments: CALCITE-547.patch
>
>
> While inferring the return type of the item operator (SqlItemOperator.
> inferReturnType()) when the SqlTypeName of the operand is ANY we set the
> nullability of return type to be false. Since the type of the operand is not
> known at this point we cannot know the return type and its nullability.
> Setting nullability to false was causing wrong results in Drill when we were
> performing count(item op), Calcite would set nullability to be false and the
> count(item op) would get replaced with count(0) causing wrong results if the
> column is eventually resolved to be nullable and has nulls in it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
