You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2019/08/09 20:48:00 UTC
[jira] [Resolved] (CALCITE-3234) For boolean properties, empty
string should mean "true"
[ https://issues.apache.org/jira/browse/CALCITE-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde resolved CALCITE-3234.
----------------------------------
Resolution: Fixed
Fixed in [a042b61|https://github.com/apache/calcite/commit/a042b6115120cb48079266444a264e16a9ca611b].
[~zabetak], I didn't use your PR, but can you please close it now the issue is fixed.
> For boolean properties, empty string should mean "true"
> -------------------------------------------------------
>
> Key: CALCITE-3234
> URL: https://issues.apache.org/jira/browse/CALCITE-3234
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.21.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> For boolean properties, empty string should mean "true". For example, if I add -Dcalcite.test.slow to the JVM args, CalciteSystemProperty.TEST_SLOW should have value "true".
> This was broken by CALCITE-2859 (Util.getBooleanProperty, which was removed, had the desired behavior).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)