Details

    • Type: Sub-task Sub-task
    • Status: Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 7.0
    • Component/s: Query Engine
    • Labels:
      None
    • Affects:
      Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes
    • Estimated Difficulty:
      Medium
    • Similar Issues:
      Show 10 results 

      Description

      Customer feature request from Issue Tracker ticket# 228151:

      The current mechanism for UDF (user-defined functions) is limited to having one model (FunctionDefinitions.xmi) in which UDF are defined and related to their Java implementations. This results in a configuration management problem even on just one project. For multiple projects it becomes a nightmare, unless we abandon all hope of building a body of reusable UDFs. I would therefore suggest that designer and server need to support multiple UDF definition models, identified by the extensions already defined and used for FunctionDefinitions.xmi.

      Similar to JBEDSP-632

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            Ramesh Reddy added a comment -

            This is a big issue which has been bought up before and will be worked upon in Westport, too late for 5.5.3 in my opinion

            Show
            Ramesh Reddy added a comment - This is a big issue which has been bought up before and will be worked upon in Westport, too late for 5.5.3 in my opinion
            Hide
            Ramesh Reddy added a comment -

            By allowing the user to have a "FunctionDefinition.xml" per VDB this can be solved. However this removes support for the global "FunctionDefinitions.xmi". Also this aids to deploy the UDF module in single VDB artifact. User who are using the this UDF in global nature can get same features by adding this file to every VDB they are used in. Any supporting JAR file needs to be in the "lib" directory of the Container.

            Show
            Ramesh Reddy added a comment - By allowing the user to have a "FunctionDefinition.xml" per VDB this can be solved. However this removes support for the global "FunctionDefinitions.xmi". Also this aids to deploy the UDF module in single VDB artifact. User who are using the this UDF in global nature can get same features by adding this file to every VDB they are used in. Any supporting JAR file needs to be in the "lib" directory of the Container.
            Hide
            Ramesh Reddy added a comment -

            In "vdb.xml" file inside the VDB, user can define any number of FUNCTION models (UDF) that need to be loaded along with metadata for the VDB. There is no notion of global UDF file any more.

            Show
            Ramesh Reddy added a comment - In "vdb.xml" file inside the VDB, user can define any number of FUNCTION models (UDF) that need to be loaded along with metadata for the VDB. There is no notion of global UDF file any more.

              People

              • Assignee:
                Ramesh Reddy
                Reporter:
                Debbie Steigner
              • Votes:
                1 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development