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

Posted to issues@flink.apache.org by "Xuefu Zhang (JIRA)" <ji...@apache.org> on 2019/07/01 22:23:00 UTC

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

Xuefu Zhang created FLINK-13047:
-----------------------------------

             Summary: 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


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)