Scribd
Upload
57 views1 page

Bruno Oliveira and Orlando Belo: Porto Polytechnic

The document discusses validating ETL patterns using the Alloy modeling language. It introduces ETL processes as a critical data warehouse component that are influenced by business requirements and can change and evolve over time. It then describes using Alloy to define an ETL meta model for patterns, where each pattern encapsulates core components, error handling, and event logging. The Alloy specification includes facts to enforce pattern consistency and the Analyzer can generate valid pattern instances or check instances for correctness.

Uploaded by

Bruno Oliveira
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
57 views1 page

Bruno Oliveira and Orlando Belo: Porto Polytechnic

The document discusses validating ETL patterns using the Alloy modeling language. It introduces ETL processes as a critical data warehouse component that are influenced by business requirements and can change and evolve over time. It then describes using Alloy to define an ETL meta model for patterns, where each pattern encapsulates core components, error handling, and event logging. The Alloy specification includes facts to enforce pattern consistency and the Analyzer can generate valid pattern instances or check instances for correctness.

Uploaded by

Bruno Oliveira
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Validating ETL Patterns

Feasibility Using Alloy Porto Polytechnic

Bruno Oliveira and Orlando Belo


[email protected]
University of Minho
[email protected]

Introduction
Independent Encapsulates the logic
Critical Data Warehouse component Influence data schemas used from each other for its physical mapping

Strongly influenced by Managed by

ETL Processes Business Requirements Patterns approach

Designed to map Supports both


Error-prone Complex Can change Can evolve standard ETL conceptual and logical
procedures ETL representation

Pattern components specification


throwable component represents pattern error strategies

Data Quality Exception


Pattern
Data Integration
Throwable
Error
Pattern Core Slowly Changing
Dimension
{EXCEPTION,
() Pattern Log Log Level FATAL, INFO,
(...)}
core component represents pattern strategy for problem solution log component represents pattern event tracking

Each component encapsulates all pattern rules to support operational requirements and the logic behind
it;

ETL meta model for patterns definition using Alloy


Pattern instance generated by the Alloy Engine
(...)
abstract sig Pattern{
coreComponent:one PatternCore,
throwableComponent: set Throwable,
logComponent: set Log}
fact consistentPattern {(...)}
abstract sig Extract, Transform, Load extends PatternCore{}(...)
sig DCI extends Transform{(...)}
(...)

The Alloy facts enforces several constraints to guarantee the patterns consistency;
The predicates embody the notion of consistent patterns;
the Alloy Analyser is used to simulate instances that conform to the specification or to check for the
correctness of concrete instances.

You might also like