atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Jones (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1016) Support for composite unique attributes for a type.
Date Mon, 10 Oct 2016 14:02:21 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562396#comment-15562396
] 

Nigel Jones commented on ATLAS-1016:
------------------------------------

I'm not a titan expert, but an index can include multiple properties. An index can be unique.
(not checked tinkerpop abstraction). I assume therefore that the underlying graph can do this...
though I think in attribute it's single property only?

> 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)

Mime
View raw message