Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.0
    • Component/s: SQL
    • Labels:
      None
    • Target Version/s:
    • Sprint:
      Spark 1.5 doc/QA sprint

      Description

      Right now our support and internal implementation of many functions has a few issues. Specifically:

      • UDFS don't know their input types and thus don't do type coercion.
      • We hard code a bunch of built in functions into the parser. This is bad because in SQL it creates new reserved words for things that aren't actually keywords. Also it means that for each function we need to add support to both SQLContext and HiveContext separately.

      For this JIRA I propose we do the following:

      • Change the interfaces for registerFunction and ScalaUdf to include types for the input arguments as well as the output type.
      • Add a rule to analysis that does type coercion for UDFs.
      • Add a parse rule for functions to SQLParser.
      • Rewrite all the UDFs that are currently hacked into the various parsers using this new functionality.

      Depending on how big this refactoring becomes we could split parts 1&2 from part 3 above.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rxin Reynold Xin
                Reporter:
                marmbrus Michael Armbrust
              • Votes:
                1 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: