In LAE, many common tasks required you to use script to configure a node. In Data360 Analyze, a number of these tasks can now be completed by using one of the script-free nodes, for example the Aggregate, Sort, Split andFilter nodes.
Take the following example of BRAINscript in an LAE Filter node:
emit *where 'type' == "primary" and 'color' != "Red"
i.e. output all records where the value of the type field is "primary" and the value of the color field is not "Red".
In the Data360 Analyze Filter node, this can be configured using the UI grid, for example:
For advanced use cases, you can use Python script to further tailor nodes. It is worth noting the following differences between BRAINscript and Python:
One general difference between BRAINscript and Python is the handling of NULL values ("null" in BRAINscript, and "Null" in Data360 Analyze):
null + 10 returns a value of
10. In Python, this type of expression would cause an error, so you would need to state explicitly what to do with the Null value, for example:
if inputs['inputField'] is Null: outputs['outputField'] = 10 else: outputs['outputField'] = 10 + inputs['inputField']
When using BRAINscript in nodes such as the Filter node, the metadata for output fields was implicitly defined when the node was compiled in BRE for execution. In Data360 Analyze, output metadata must be explicitly defined in the ConfigureFields property of the Transform node (and similar nodes). The ConfigureFields script is executed before any input records are processed. The ConfigureFields script can also be used to import Python modules into the execution environment, retrieve node property values and to set / initialize variable values prior to execution of records. The ProcessRecords script is executed once for each input record.
Input and output field references
In the Python-based nodes, you can use the following input and output field references:
out1 += in1
outputs += inputs
outputs += inputs format uses the output / input pin index rather than the pin's name, so the script will still operate if the output pin name is subsequently changed.
For examples of how to configure the Python-based nodes, see:
If you are still using some superseded nodes in your graphs while you begin to transition to use the new Python-based nodes, it is important to be aware of a number of BRAINscript changes in Data360 Analyze compared to LAE, see BRAINscript changes.