[
https://issues.apache.org/jira/browse/CALCITE-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved CALCITE-4138.
---------------------------------
Fix Version/s: avatica-1.18.0
Resolution: Fixed
Thanks for the nice fix, Istvan!
I had to go back into the mental archives to remember how Calcite/Avatica does
the website :). I modified your commit to calcite-avatica.git to include the
markdown which generates the content (which is copied) into
calcite-site.git/avatica. It was easy enough to adapt – just mentioning it for
the next time!
> 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
> Labels: pull-request-available
> Fix For: avatica-1.18.0
>
> Time Spent: 40m
> 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)
