Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-3323

Handle arbitrary/unknown functions that have ordinary syntax

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.22.0
    • None

    Description

      Add a strategy where if a function has ordinary function syntax and we don't recognize it we assume that it can take any argument types and returns a result of unknown type.

      We will still need to change the parser to handle functions with non-standard syntax (e.g. DATEADD). And it's a good idea to explicitly add commonly used non-standard functions (e.g. MD5, CONCAT).”

      [19/Sept/2019] Functions have to have ordinary function syntax [e.g. foo(arg0, ...)]. Current implementation idea is to:

      • Create a known/unknown flag for use within the validator
      • Create a more permissive SqlUnresolvedFunction to be passed through validator
        • Allow OperandTypes to be variadic

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              fib-seq Ryan Fu
              Votes:
              0 Vote for this issue
              Watchers:
              5 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 - 1h 40m
                  1h 40m