[
https://issues.apache.org/jira/browse/PHOENIX-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364143#comment-17364143
]
Istvan Toth commented on PHOENIX-6003:
--------------------------------------
I turns out that metadata handling is broken in Phoenix, and applying the
Avatica fix would break PhoenixDB metadata handling.
For now, I'll leave PhoenixDB as is.
> 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)
