[
https://issues.apache.org/jira/browse/ATLAS-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561749#comment-15561749
]
David Radley commented on ATLAS-1016:
-------------------------------------
I read this as introducing something that would mean that the combination of
more than one fields would need to be unique; even though the individual fields
may not be unique. This can be used to define a more meaningful business key
and can be used in master data management.
Can we do this with the current support for structures? [~zhangqiangzte]
> Support for composite unique attributes for a type.
> ---------------------------------------------------
>
> Key: ATLAS-1016
> URL: https://issues.apache.org/jira/browse/ATLAS-1016
> Project: Atlas
> Issue Type: Improvement
> Affects Versions: 0.8-incubating
> Reporter: Satish Duggana
> Fix For: 0.8-incubating
>
>
> Currently atlas types support attributes containing unique attributes.
> Enhance this to support composite unique attributes.
> For example,
> DeviceInfo has attributes like name, model, version and timestamp. Any of
> these attributes can be configured unique constraint. There should be a way
> to set composite unique constraint on both model and version fields so that
> it should not allow storing entities having same set of values for both model
> and version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
