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

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Component/s: Table SQL / API
• Labels: pull-request-available
• Assignee: Xuefu Zhang
• Reporter: Xuefu Zhang
• Created: 01/Jul/19 22:22
• Updated: 02/Jul/19 18:17
• Resolved: 02/Jul/19 18:17

Description

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().

Issue Links

• links to: GitHub Pull Request #8940