Events are the base unit of data in Alooma and the Mapper. An event in Alooma can be an application action sent to Alooma via our SDK, a row in MySQL, a line in a CSV file, a row in a Salesforce object and so on — each piece of information that is streamed into Alooma is treated as an individual event. Alooma automatically converts each event into a JSON structure as part of the input process. Alooma also adds metadata to every event.
The Alooma Code Engine lets you define how the events from each input are handled, meaning how they are transformed, enriched, merged and so on.
The Alooma Mapper lets you define which event fields are taken and replicated into the tables and columns of your target data warehouse.
An event type is an internal data construct automatically created by Alooma to represent the data structure of events of a certain type. Alooma automatically creates one or more event types for each input (depending on the type of input), and you can define additional event types. An event type contains a superset of all the fields ever received in events of that type.
When an event of a certain event type contains a new field, then this field is automatically added to the corresponding event type.
If a field of an event is changed, then its event type includes both the old field and the new field.
Fields are not deleted from an event type. If you want to remove fields that are no longer relevant, you can do so from the Mapper page.