[
https://issues.apache.org/jira/browse/CALCITE-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164877#comment-17164877
]
Istvan Toth commented on CALCITE-4138:
--------------------------------------
[~elserj] This is the Avatica bug that I'd had to work around in the PhoenixDB
SqlAclhemy driver.
> Metadata operations via Avatica turn empty string args to null
> --------------------------------------------------------------
>
> Key: CALCITE-4138
> URL: https://issues.apache.org/jira/browse/CALCITE-4138
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Affects Versions: 1.17.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DatabaseMetaData.getTables(), and some other functions have parameters
> (catalog, schemaPattern), where null and empty String have different
> semantics.
> The corresponding protobuf fields in Avatica are Strings, and the Avatica
> logic turns those args to null.
> This makes it impossible to filter on actual empty string values.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
