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

Posted to issues@calcite.apache.org by "Volodymyr Vysotskyi (JIRA)" <ji...@apache.org> on 2018/07/05 11:39:00 UTC

[jira] [Resolved] (CALCITE-2342) use of assert with side-effect in Schemas

     [ https://issues.apache.org/jira/browse/CALCITE-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Volodymyr Vysotskyi resolved CALCITE-2342.
------------------------------------------
    Resolution: Fixed

Fixed in [a99f386|https://github.com/apache/calcite/commit/a99f386d5c36d560c832f9e70542f9d058ea22f5]

> use of assert with side-effect in Schemas
> -----------------------------------------
>
>                 Key: CALCITE-2342
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2342
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>            Reporter: Laurent Goujon
>            Assignee: Laurent Goujon
>            Priority: Major
>             Fix For: 1.17.0
>
>
> {{Schemas#path(CalciteSchema,Iterable<String>)}} method has the following code:
> {code:java}
> if (!rootSchema.name.isEmpty()) {
>   assert rootSchema.name.equals(iterator.next());
> }
> {code}
> Depending if assertions are enabled or not, iterator state might be different



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)