Documentation
Introduction to Aether
Try It For Yourself
- Prerequisites
- Install and Configure
- A Simple Aether-Based Solution
- A More Complex Aether-Based Solution
- Adding Aether Connect
Aether UI User Guide
Create a mapping
You connect the fields of your incoming data to your desired output by mapping them to the properties of your Entity Types.
In the previous two steps you have learned how to add your input fields and how to define the Entity Types.
So now let’s have a look at how to map them.
The MAPPING screen
So hop over to “MAPPING” and see your Input and your Entity Types next to a list of yet empty mapping Rules. What we want to do now, is to create a connection between fields of your input schema and properties of your Entity Types.
Add a mapping rule
Clicking on “ADD RULE” will show you a pair of text-boxes. One for the source, and one for the destination of the mapping you want to create.
Now check your schemas from your INPUT and your ENTITY TYPES on the left hand side. The first fields you might wanna map are first_name
from your survey to username
from your “Person” Entity :
To add the mapping, simply type the path of the fields into the related textboxes:
Aether is using JsonPaths. A correct path for Entity Types consists of EntityTypeName
.property
.
By hitting “APPLY MAPPING RULES TO PIPELINE” you can see the result of your action: The first mapping is created!
The mapped fields have a different background now.
Check the Output
Noticed the red dot next to “OUTPUT”?
Aether actually processes the pipeline now, since you have applied a mapping. But it is failing. Why?
Because a Person consists of id
, username
and age
. Our output would be a Person with username
only, which is not what the extracted record expects.
More mappings
So let’s go back to the MAPPING screen and add another rule for the property id
.
Remember as we’ve explained earlier, that each Entity Type must have an ID? This is mandatory for every Mapping.
Since we haven’t got an ID that comes with the input source, we can create one by using #!uuid
. This will generate a Universally unique identifier.
We can continue now adding all the mappings we need for our Entity Types:
See how all the the mappings are marked now:
The Output
If you click to open the OUTPUT panel, you can see the data, that was generated from your mappings.
Great job!
The output has switched to display a green light: This pipeline now produces two Entities from your Input.