You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2020/08/03 04:27:00 UTC

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

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

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

The fix is in Avatica master, it will be available int the 1.18 release.

> 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)