[jira] [Commented] (CALCITE-4891) Avatica can't handle uuid fields saying 'Cannot handle class java.util.UUID as bytes'

["Josh Elser (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445325#comment-17445325 ] 

Josh Elser commented on CALCITE-4891:
-------------------------------------

Yeah, I am inclined to agree with you, Jamie. We coerce the UUID to bytes (or a utf-8 string) when sending that over the wire, so this error sounds like we messed up the wrapping/unwrapping across the wire. Do you have any aspirations to try to fix this? Seeing if we can write a simple unit test would be a good start –  I would look at adding a test method to [RemoteMetaTest|https://github.com/apache/calcite-avatica/blob/master/server/src/test/java/org/apache/calcite/avatica/remote/RemoteMetaTest.java]

> Avatica can't handle uuid fields saying 'Cannot handle class java.util.UUID as bytes'
> -------------------------------------------------------------------------------------
>
>                 Key: CALCITE-4891
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4891
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>    Affects Versions: avatica-1.19.0
>            Reporter: Jamie Taylor
>            Priority: Major
>
> When I try and fetch a value of type UUID through an avatica proxy I get an error saying 'Cannot handle class java.util.UUID as bytes'
> If I change the serilisation from json to protobuf I still get the exact same error.
> Other types that aren't supported such as blob give messages saying they aren't supported, which makes this look like a bug.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)