Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-11275 Unified Catalog APIs
  3. FLINK-13047

Fix the Optional.orElse() usage issue in DatabaseCalciteSchema

    XMLWordPrintableJSON

    Details

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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                xuefuz Xuefu Zhang
                Reporter:
                xuefuz Xuefu Zhang
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m