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

Posted to issues@flink.apache.org by "Bowen Li (JIRA)" <ji...@apache.org> on 2019/07/02 18:18:00 UTC

[jira] [Closed] (FLINK-13047) Fix the Optional.orElse() usage issue in DatabaseCalciteSchema

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

Bowen Li closed FLINK-13047.
----------------------------
    Resolution: Fixed

merged in 1.9.0: 3358cd3b6d6ffebb313b6c02f2a53e6dbd6ec1ed

> Fix the Optional.orElse() usage issue in DatabaseCalciteSchema 
> ---------------------------------------------------------------
>
>                 Key: FLINK-13047
>                 URL: https://issues.apache.org/jira/browse/FLINK-13047
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>    Affects Versions: 1.9.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> It's found that Optional.orElse() will evaluate the argument first before returning Optional.get(). If the evaluation throws an exception then the call fails even if the Optional object is nonempty. This the case In {{DatabaseCalciteSchema.convertCatalogTable()}}.



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