[jira] [Commented] (PHOENIX-6003) Metadata operations via Avatica turn empty string args to null

["Istvan Toth (Jira)" <ji...@apache.org>]

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

Istvan Toth commented on PHOENIX-6003:
--------------------------------------

While this is an Avatica issue, I'm going to leave this open, to remind us, that we

A) Need to update to the future Avatica version where this is fixed.

B) Need to update PhoenixDB as well to fix this (regenerate with new protobuf, and set new fields)

> Metadata operations via Avatica turn empty string args to null
> --------------------------------------------------------------
>
>                 Key: PHOENIX-6003
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6003
>             Project: Phoenix
>          Issue Type: Bug
>          Components: queryserver
>    Affects Versions: queryserver-6.0.0
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> PhoenixDatabaseMetaData.getTables(), and some other functions have parameters (catalog, schemaPattern), where null and empty String have different semantics.
> The corresponding protobuf fields in Avatica are not nullable, and PQS seems to interpret empty string as Null, making it impossible to get the default catalog/schema only.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)