Bug 540646 - Make ETL Trace an Model
Summary: Make ETL Trace an Model
Status: NEW
Alias: None
Product: Epsilon
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Horacio Hoyos CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-31 05:47 EDT by Horacio Hoyos CLA
Modified: 2018-10-31 05:47 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Horacio Hoyos CLA 2018-10-31 05:47:16 EDT 
Expected behaviour: Use the ETL trace as a model for further processing (i.e. store, print, etc.) via modelling scripts.

Seen behaviour: Currently, the ETL trace model is a POJO with a trace cache and a list of generated artefacts per rule.

Proposal: Do something similar to EPL in which the Match model implements IModel and provides a set of script based types: one type per match rule (rule XXX -> PatternXXX) and one type per rule role (role YYY -> PatternXXXYYY).

For ETL I would suggest only one type per rule (rule XXX -> TxXXX), and then have the "transform" and "to" elements as properties. Perhaps a type for "transform" roles would be interesting too (TxXXXYYY), so we could provide an equivalent/equivalents operation (via the model).