Data360 DQ+

 View Only

  • 1.  Reason for removing RUNTIME function from DQ+ version 5 and onwards

    Employee
    Posted 09-30-2020 08:01

    Hi Team,

    Can you please let us know the reason why the function "RUNTIME" is getting removed from the version 5 on wards in DQ+.

    Currently, the implementation of Nordea uses RUNTIME function inside all of its Process Models. The function is defined inside the process model variable as an expression.

    Nordea is currently using the version 3.3 and they are planning to have an upgrade in October to the version 5. Since this function is getting removed, we would have to make changes in our code and would need to communicate accordingly mentioning the reasons.

    Please let us know whether any other function is replacing RUNTIME and would serve its purpose so that the same can be suggested to the client.

    Regards,
    Abhijith 



  • 2.  RE: Reason for removing RUNTIME function from DQ+ version 5 and onwards

    Employee
    Posted 09-30-2020 11:36

    Hi Abhijith,

       The RUNTIME function is still available within analyses in 5.x.  The function was removed from Process Model because it did not serve a purpose other than returning null no matter value you provide it.  If you have one, can you tell me what your use case within Process Model?

    Thanks,

    Jeff



  • 3.  RE: Reason for removing RUNTIME function from DQ+ version 5 and onwards

    Employee
    Posted 09-30-2020 12:23

    Hi Jeff,

     

    I am defining RUNTIME function inside Process model variable to call an environment variable and I am successful in achieving this in version 3.3 of DQ+

     

    Please find below example for your reference:

     

    Environment Variable name: root

    Value of Environment variable (or) root: /home/shared
    Process Model Variable Name: CURRENT_PATH
    Expression defined in Process Model Variable: CONCATENATE(RUNTIME('root'),'/<HDFS_directory>/<HDFS_subdirectory>'

     

    On triggering the process model, the above expression gets transformed and the file from below HDFS directory is processed:

    /home/shared/<HDFS_directory>/<HDFS_subdirectory

     

    However, as you mentioned, it was returning a null value when I tried to display value of environment variable through email using the node “Notify Task”.

     

    Script used in Message Details of node "Notify Task":
    Path = ${CURRENT_PATH}
    Expected Result: /home/shared/<HDFS_directory>/<HDFS_subdirectory
    Actual Result: /<HDFS_directory>/<HDFS_subdirectory

     

    From what I have observed, I believe that internally functionality of RUNTIME is working, however it is returning a null while trying to display the value.

     

    Regards