atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Radley (JIRA)" <>
Subject [jira] [Commented] (ATLAS-1955) Validation for Attributes
Date Thu, 17 Aug 2017 11:24:00 GMT


David Radley commented on ATLAS-1955:

[~ivarea]. I think we want reusable validation one email type all can use. Atlas will then
ship some of these types that can be used by the shipped models - I am thinking of url and
image being very useful. We could have new attribute types to police valid names for hive
tables and the like. I think option 2 or a variant will be very powerful. 

> Validation for Attributes
> -------------------------
>                 Key: ATLAS-1955
>                 URL:
>             Project: Atlas
>          Issue Type: New Feature
>          Components:  atlas-core
>    Affects Versions: 0.9-incubating
>            Reporter: Israel Varea
>            Assignee: Richard Ding
>             Fix For: 0.9-incubating
> It would be very nice that Atlas model could contain a way to represent attribute validation.

> A simple example is that we would like to model a Person, with attributes Name, Email
and Country. Now we would like to specify that Email has to follow a specific regular expression,
so it would be nice if we could set Email -> hasValidation -> EmailRegex, with EmailRegex
> Name: Email Regular Expresion
> Expression: /[0-9a-z]+@[0-9a-z]+.[0-9a-z]+/
> For more complex types of validation, e.g. checking card number validity, it could be
added some external validator function/service.
> Name: Credit Card Number Validator
> Validator: or https://host:port/creditCardValidator
> For validations from a reference table, for example a country name, it could be:
> Name: Country Name Ref Validator
> Reference Column: <country_name_column>
> where <country_name_column> would be an instance of type Hive_Column or HBase_Column.
> Since this is a kind of Standarization, it could be placed in [Area 5|].
> A similar approach is followed in software [Kylo|]

This message was sent by Atlassian JIRA

View raw message