[
https://issues.apache.org/jira/browse/CALCITE-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938355#comment-17938355
]
Julian Hyde commented on CALCITE-6912:
--------------------------------------
This issue relates to {{{}ReflectiveSchema{}}}. You should make that explicit
in the summary/description.
Do we have any documentation about how {{ReflectiveSchema}} is supposed to
behave, in particular, what Java datatypes map are allowed, and how they map to
SQL data types. Absent such documentation, people make assumptions about what
should work, hence confusion.
The solution to confusion is documentation.
> Confusion around typing of byte[] versus ByteString in Enumerable code
> ----------------------------------------------------------------------
>
> Key: CALCITE-6912
> URL: https://issues.apache.org/jira/browse/CALCITE-6912
> Project: Calcite
> Issue Type: Bug
> Components: avatica, core
> Affects Versions: 1.35.0, 1.40.0
> Reporter: Chris Dennis
> Priority: Major
> Labels: pull-request-available
>
> The Enumerable convention code generation seems to be at odds with both
> Avatica and at other times with itself when trying to handle {{byte[]}} field
> types. This leads to a variety of failure either at during code generation,
> or at query execution time. I will push an example of a failing query in PR
> shortly after filing this... but I suspect most any query that attempts to
> project a byte[] typed column has a good chance of tripping over itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
