[jira] [Updated] (ATLAS-1927) UI - changing the look and feel of attribute in details page.

[Kalyani Kashikar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kalyani Kashikar updated ATLAS-1927:

Attachment: ATLAS-1927.3.patch

> UI - changing the look and feel of attribute in details page.
> -
>
> Key: ATLAS-1927
> URL: https://issues.apache.org/jira/browse/ATLAS-1927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1927.1.patch, ATLAS-1927.2.patch, 
> ATLAS-1927.3.patch, ATLAS-1927.patch
>
>
> Show the attributes of entities in tag format instead of showing comma(,) 
> separator.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 60705: ATLAS-1927 : UI - changing the look and feel of attribute in details page.

[Kalyani Kashikar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60705/
---

(Updated July 17, 2017, 11:16 a.m.)


Review request for atlas, keval bhatt, Madhan Neethiraj, and Nixon Rodrigues.


Changes
---

border added for attribute table.


Bugs: ATLAS-1927
https://issues.apache.org/jira/browse/ATLAS-1927


Repository: atlas


Description
---

Show the attributes of entities in tag format instead of showing comma(,) 
separator.


Diffs (updated)
-

  dashboardv2/public/css/scss/tag.scss fc0652b 
  dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js c45755f 
  dashboardv2/public/js/views/tag/TagDetailTableLayoutView.js 45cdd6b 
  dashboardv2/public/js/views/tag/addTagModalView.js 97d80bd 


Diff: https://reviews.apache.org/r/60705/diff/4/

Changes: https://reviews.apache.org/r/60705/diff/3-4/


Testing
---

verified the attributes of entities is showing in tag format instead of showing 
comma(,) separator.


Thanks,

Kalyani Kashikar

Re: Review Request 60681: ATLAS-1698 Glossary OMAS API - early Swagger draft

[David Radley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60681/
---

(Updated July 17, 2017, 1:11 p.m.)


Review request for atlas and Madhan Neethiraj.


Repository: atlas


Description
---

This is stub code to generate some Glossary OMAS REST interfaces. 

It does not include : 
- search
- finding all assets
- lineage

This patch is not to be committed at this time- it is for review purposes only.


Diffs (updated)
-

  glossary-omas/pom.xml PRE-CREATION 
  glossary-omas/src/main/java/org/apache/atlas/model/GlossaryOMASCategory.java 
PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/GlossaryOMASGraphEdgeDirection.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/GlossaryOMASPermission.java 
PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/GlossaryGraph.java 
PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/GlossaryGraphEdge.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/GlossaryGraphNode.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/GlossaryTreeElement.java
 PRE-CREATION 
  glossary-omas/src/main/java/org/apache/atlas/model/instance/Relatable.java 
PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/category/GlossaryCategory.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/glossary/Anchor.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/glossary/Glossary.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/ExternalGlossaryLink.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/GlossaryTerm.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/Antonym.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/ISA.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/PreferedTerm.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/RelatedTerm.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/RelatedTerms.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/ReplacementTerm.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/Synonym.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/Translation.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/RelatedTerms/ValidValue.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/SemanticAssignment/SemanticAssignment.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/TermRelationshipStatus.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/contexts/Context.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/SpineObjects.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/TermHASARelationship.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/TermISATYPEOFRelationship.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/TermSpineRelationship.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/spineObjects/TermTYPEDBYRelationship.java
 PRE-CREATION 
  
glossary-omas/src/main/java/org/apache/atlas/model/instance/term/termCategorization/TermCategorization.java
 PRE-CREATION 
  omas/pom.xml PRE-CREATION 
  omas/src/main/java/org/apache/atlas/exception/OMASBaseException.java 
PRE-CREATION 
  omas/src/main/java/org/apache/atlas/exception/OMASErrorCode.java PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/EmbeddedMedia.java PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/MediaUsage.java PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/PList.java PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/SearchFilter.java PRE-CREATION 
  omas/src/main/java/org/apache/atlas/model/instance/OMASEntity.java 
PRE-CREATION 
  pom.xml ebc07e21d2d721910f1aae7069305845284a8c21 
  webapp/pom.xml 465d2a5498376a2517dc1b01f970734c452c504d 
  
webapp/src/main/java/org/apache/atlas/examples/CreateTypesFromJsonFileUtil.java 
PRE-CREATION 
  
webapp/src/main/java/org/apache/atlas/examples/UpdateTypesFromJsonFileUtil.java 
PRE-CREATION 
  webapp/src/main/java/org/apache/atlas/web/rest/GlossaryOMASREST.java 
PRE-CREATION 


Diff: https://

[jira] [Commented] (ATLAS-1839) Area 2 of the open metadata model

[Israel Varea (JIRA)]

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

Israel Varea commented on ATLAS-1839:
-

Hi all,

I have been looking at how open metadata model is being defined and I think 
this iniciative is awesome.

In particular, I would like to model some domain using this Area 2 definitions, 
but I can't find a proper way to do so, may be you can have some insights of 
how to do it.

I want to model a Person, so I would include Person as a Term that inherits 
from Catalog. Now I want to add some attributes (concepts) related to a Person, 
such as Person_Name, Person_Surname, Date_of_Birth, Email, so I add them as 
Terms too.
How should I relate these Terms as "attribute_of" Person? I see there is a 0250 
Related Terms section, however there is no relation to specify "attribute_of" 
or similar.

In this model, I would like to specify some features for Terms, such as 
validation/normalization, max and min values, etc. For example, I would like to 
specify that only a specific regex is valid for Emails, or Card_Numbers. 
How could I add these features for the Terms?

Thanks




> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: 0210Glossary.json, 0220CategoryHierarchy.json, 
> 0230Terms.json, 0240Dictionary.json, 0250RelatedTerms.json
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

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

David Radley commented on ATLAS-1839:
-

Hi [~ivarea],
Thank you for your interest. I am in the process of putting together json files 
that will define the types that are required for the glossary. I am also 
putting up am OMAS API for the Glossary for review - this is an 
API that is optimized for glossary user interfaces. I would appreciate your 
feedback on ATLAS-1698. 
To go through what you are looking to do:
- yes you can create terms for Person, such as Person_Name, Person_Surname, 
Date_of_Birth etc
- the way we are looking to represent attributes is using the spine objects. 
See https://cwiki.apache.org/confluence/display/ATLAS/Area+2+-+Glossary for 
more details.  
- regarding validation of string attributes. I am not aware of this 
functionality in Atlas - though you might be able to do this in Ranger. I think 
this would be good enhancement to the Atlas entity model - I suggest that you 
raise a Jira for this. 



> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: 0210Glossary.json, 0220CategoryHierarchy.json, 
> 0230Terms.json, 0240Dictionary.json, 0250RelatedTerms.json
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1698) Create Glossary OMAS API

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1698:

Attachment: (was: apidocs-3.zip)

> Create Glossary OMAS API
> 
>
> Key: ATLAS-1698
> URL: https://issues.apache.org/jira/browse/ATLAS-1698
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: apidocs-4.zip, Atlas Glossary OMAS API proposal v1.0 
> .pdf, Atlas Glossary OMAS API proposal v1.1.pdf
>
>
> The Glossary OMAS provides a specialized API for glossary applications to 
> retrieve and store their glossary metadata and link assets of different types 
> to these glossary entries.
> The Glossary OMAS makes heavy use of the Area 2 open metadata model.  See 
> https://cwiki.apache.org/confluence/display/ATLAS/Area+2+-+Glossary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1698) Create Glossary OMAS API

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1698:

Attachment: apidocs-4.zip

Addressed review comments and changed to allow Atlas to start with this code. 
amended the object names to not include Atlas

> Create Glossary OMAS API
> 
>
> Key: ATLAS-1698
> URL: https://issues.apache.org/jira/browse/ATLAS-1698
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: apidocs-4.zip, Atlas Glossary OMAS API proposal v1.0 
> .pdf, Atlas Glossary OMAS API proposal v1.1.pdf
>
>
> The Glossary OMAS provides a specialized API for glossary applications to 
> retrieve and store their glossary metadata and link assets of different types 
> to these glossary entries.
> The Glossary OMAS makes heavy use of the Area 2 open metadata model.  See 
> https://cwiki.apache.org/confluence/display/ATLAS/Area+2+-+Glossary



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-1768) Create common types for Open Metadata

[David Radley (JIRA)]

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

David Radley commented on ATLAS-1768:
-

[~mandy_chessell] I am looking at the glossary model and I notice that in model 
210-Glossary, the ExternalGlossaryLink has an atribute called source of type 
ExternalReference. Now that ExternalReference is an entity and not a structure, 
I suggest we change ExternalGlossaryLink  to subclass  ExternalReference and 
add the extra organization attribute.  

> Create common types for Open Metadata
> -
>
> Key: ATLAS-1768
> URL: https://issues.apache.org/jira/browse/ATLAS-1768
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata
>
> This JIRA describes a proposal for standard types for open metadata entities 
> and relationships.  For example, glossaries, database definitions, rules, 
> policies, ...
> The value of having standard definitions for metadata is to enable type safe 
> APIs and business level UIs plus be able to exchange metadata between 
> different instances of metadata repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and 
> using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and 
> collaboration around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see 
> https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common 
> definitions must be extensible - and we still need to support the ad hoc 
> definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new 
> types.  These are currently enumeration, struct, classification and entity.  
> JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to 
> this list.  The open metadata models make use of all of these meta-types.  
> These are represented by sterotypes on the classes of the open metadata 
> definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the 
> easiest way to view the models.
> Start here: 
> https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (ATLAS-1768) Create common types for Open Metadata

[David Radley (JIRA)]

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

David Radley edited comment on ATLAS-1768 at 7/17/17 3:19 PM:
--

[~mandy_chessell] I am looking at the glossary model and I notice that in model 
210-Glossary, the ExternalGlossaryLink has an atribute called source of type 
ExternalReference. Now that ExternalReference is an entity and not a structure, 
I suggest we change ExternalGlossaryLink  to subclass  ExternalReference and 
add the extra organization attribute.  

In model 220 LibraryCategoryReference is a relationship with an attribute 
called source of type  ExternalReference. We need to change this as 
relationshipDefs cannot have relationships. I suggest we explicitly add the 
attributes we need into this relationship. I notice the term version of this 
relationship is not consistent with this category one.   



was (Author: davidrad):
[~mandy_chessell] I am looking at the glossary model and I notice that in model 
210-Glossary, the ExternalGlossaryLink has an atribute called source of type 
ExternalReference. Now that ExternalReference is an entity and not a structure, 
I suggest we change ExternalGlossaryLink  to subclass  ExternalReference and 
add the extra organization attribute.  

> Create common types for Open Metadata
> -
>
> Key: ATLAS-1768
> URL: https://issues.apache.org/jira/browse/ATLAS-1768
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata
>
> This JIRA describes a proposal for standard types for open metadata entities 
> and relationships.  For example, glossaries, database definitions, rules, 
> policies, ...
> The value of having standard definitions for metadata is to enable type safe 
> APIs and business level UIs plus be able to exchange metadata between 
> different instances of metadata repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and 
> using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and 
> collaboration around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see 
> https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common 
> definitions must be extensible - and we still need to support the ad hoc 
> definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new 
> types.  These are currently enumeration, struct, classification and entity.  
> JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to 
> this list.  The open metadata models make use of all of these meta-types.  
> These are represented by sterotypes on the classes of the open metadata 
> definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the 
> easiest way to view the models.
> Start here: 
> https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (ATLAS-1768) Create common types for Open Metadata

[David Radley (JIRA)]

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

David Radley edited comment on ATLAS-1768 at 7/17/17 4:32 PM:
--

[~mandy_chessell] I am looking at the glossary model and I notice that in model 
210-Glossary, the ExternalGlossaryLink has an atribute called source of type 
ExternalReference. Now that ExternalReference is an entity and not a structure, 
I suggest we change ExternalGlossaryLink  to subclass  ExternalReference and 
add the extra organization attribute.  

In model 220 LibraryCategoryReference is a relationship with an attribute 
called source of type  ExternalReference. We need to change this as 
relationshipDefs cannot have relationships. I suggest we explicitly add the 
attributes we need into this relationship. I notice the term version of this 
relationship is not consistent with this category one.   

I model 280 spine objects, there are 2 endpoints called attribute. I suggest we 
use plural names for all "SET" endpoints and have attributes and 
typedAttributes. 


was (Author: davidrad):
[~mandy_chessell] I am looking at the glossary model and I notice that in model 
210-Glossary, the ExternalGlossaryLink has an atribute called source of type 
ExternalReference. Now that ExternalReference is an entity and not a structure, 
I suggest we change ExternalGlossaryLink  to subclass  ExternalReference and 
add the extra organization attribute.  

In model 220 LibraryCategoryReference is a relationship with an attribute 
called source of type  ExternalReference. We need to change this as 
relationshipDefs cannot have relationships. I suggest we explicitly add the 
attributes we need into this relationship. I notice the term version of this 
relationship is not consistent with this category one.   


> Create common types for Open Metadata
> -
>
> Key: ATLAS-1768
> URL: https://issues.apache.org/jira/browse/ATLAS-1768
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata
>
> This JIRA describes a proposal for standard types for open metadata entities 
> and relationships.  For example, glossaries, database definitions, rules, 
> policies, ...
> The value of having standard definitions for metadata is to enable type safe 
> APIs and business level UIs plus be able to exchange metadata between 
> different instances of metadata repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and 
> using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and 
> collaboration around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see 
> https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common 
> definitions must be extensible - and we still need to support the ad hoc 
> definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new 
> types.  These are currently enumeration, struct, classification and entity.  
> JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to 
> this list.  The open metadata models make use of all of these meta-types.  
> These are represented by sterotypes on the classes of the open metadata 
> definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the 
> easiest way to view the models.
> Start here: 
> https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1836) Area 0 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1836:

Attachment: (was: 0005LinkedMediaTypes.json)

> Area 0 of the open metadata model
> -
>
> Key: ATLAS-1836
> URL: https://issues.apache.org/jira/browse/ATLAS-1836
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 0 in the open metadata model.  This area covers base types.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1836) Area 0 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1836:

Attachment: 0005LinkedMediaTypes.json

> Area 0 of the open metadata model
> -
>
> Key: ATLAS-1836
> URL: https://issues.apache.org/jira/browse/ATLAS-1836
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: 0005LinkedMediaTypes.json
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 0 in the open metadata model.  This area covers base types.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1839:

Attachment: (was: 0220CategoryHierarchy.json)

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1839:

Attachment: (was: 0230Terms.json)

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1839:

Attachment: (was: 0210Glossary.json)

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1839:

Attachment: (was: 0240Dictionary.json)

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1839:

Attachment: (was: 0250RelatedTerms.json)

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley reassigned ATLAS-1839:
---

Assignee: David Radley  (was: Mandy Chessell)

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: 0210Glossary.json, 0220CategoryHierarchy.json, 
> 0230Terms.json, 0250RelatedTerms.json, 0260Contexts.json, 
> 0270SemanticAssignment.json, 0280SpineObjects.json
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1839:

Attachment: 0210Glossary.json
0220CategoryHierarchy.json
0230Terms.json
0250RelatedTerms.json
0260Contexts.json
0270SemanticAssignment.json
0280SpineObjects.json

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: 0210Glossary.json, 0220CategoryHierarchy.json, 
> 0230Terms.json, 0250RelatedTerms.json, 0260Contexts.json, 
> 0270SemanticAssignment.json, 0280SpineObjects.json
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-1939) Export/Import Regression : NPE during import

[Madhan Neethiraj (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj resolved ATLAS-1939.
-
   Resolution: Fixed
 Assignee: Sharmadha Sainath
Fix Version/s: 0.8.1-incubating
   0.9-incubating

Fix committed to following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/eddab3b1
 - 0.8-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/e4565a5f

> Export/Import Regression : NPE during import
> 
>
> Key: ATLAS-1939
> URL: https://issues.apache.org/jira/browse/ATLAS-1939
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Sharmadha Sainath
>Priority: Blocker
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1939.patch, Import_error_NPE2.txt, Import_NPE.txt
>
>
> Exported a hive_table and created zip file t5.zip and tried to import in into 
> another cluster using
> {code}
> curl -v -X POST -u admin:admin -H "Content-Type: multipart/form-data" -H 
> "Cache-Control: no-cache" --data-binary @t5.zip 
> "http://host2:21000/api/atlas/admin/import";
> {code}
> Import Request failed with 500 internal server error with NPE in application 
> logs.
> Attached the exception stack trace.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-1947) AtlasSearchResult to include referredEntity headers

[Madhan Neethiraj (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj resolved ATLAS-1947.
-
   Resolution: Fixed
Fix Version/s: (was: trunk)
   0.8.1-incubating
   0.9-incubating

Committed to the following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/bcec42e3
 - 0.8-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c1f0f496

> AtlasSearchResult to include referredEntity headers
> ---
>
> Key: ATLAS-1947
> URL: https://issues.apache.org/jira/browse/ATLAS-1947
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.1-incubating
>
>
> With the upcoming search feature the UI becomes more chatty with Atlas web 
> server in order to render the dynamic columns. This change adds more 
> information in the search result so that the UI can render with relatively 
> less calls.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-1944) NotificationHookConsumer throws exception while shutting down the consumer thread

[Madhan Neethiraj (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj resolved ATLAS-1944.
-
   Resolution: Fixed
Fix Version/s: 0.8.1-incubating

Committed to the following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/18745cf4
 - 0.8-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/9b63509d

> NotificationHookConsumer throws exception while shutting down the consumer 
> thread
> -
>
> Key: ATLAS-1944
> URL: https://issues.apache.org/jira/browse/ATLAS-1944
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Ashutosh Mestry
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1944.patch
>
>
> NotificationHookConsumer throws below exception while shutting down the 
> consumer thread, this issue is possibly after this commit.
> https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62
> CC [~nixonrodrigues]
> {noformat}
> 2017-07-12 01:26:09,743 WARN  - [pool-1-thread-1:] ~ Error stopping service 
> org.apache.atlas.notification.NotificationHookConsumer (Services:69)
> java.util.ConcurrentModificationException: KafkaConsumer is not safe for 
> multi-threaded access
> at 
> org.apache.kafka.clients.consumer.KafkaConsumer.acquire(KafkaConsumer.java:1557)
> at 
> org.apache.kafka.clients.consumer.KafkaConsumer.close(KafkaConsumer.java:1467)
> at 
> org.apache.atlas.kafka.AtlasKafkaConsumer.close(AtlasKafkaConsumer.java:88)
> at 
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.stop(NotificationHookConsumer.java:384)
> at 
> org.apache.atlas.notification.NotificationHookConsumer.stopConsumerThreads(NotificationHookConsumer.java:172)
> at 
> org.apache.atlas.notification.NotificationHookConsumer.stop(NotificationHookConsumer.java:155)
> at org.apache.atlas.service.Services.stop(Services.java:67)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:366)
> at 
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeDestroyMethods(InitDestroyAnnotationBeanPostProcessor.java:325)
> at 
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeDestruction(InitDestroyAnnotationBeanPostProcessor.java:154)
> at 
> org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:253)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:578)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:961)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:523)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingletons(DefaultListableBeanFactory.java:968)
> at 
> org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:1033)
> at 
> org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1009)
> at 
> org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:961)
> at 
> org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:583)
> at 
> org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:116)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:808)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:457)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:842)
> at 
> org.eclipse.jetty.servlet.ServletC

[jira] [Updated] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1839:

Attachment: 0220CategoryHierarchy.json

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: 0210Glossary.json, 0220CategoryHierarchy.json, 
> 0230Terms.json, 0250RelatedTerms.json, 0260Contexts.json, 
> 0270SemanticAssignment.json, 0280SpineObjects.json
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1839) Area 2 of the open metadata model

[David Radley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1839:

Attachment: (was: 0220CategoryHierarchy.json)

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: 0210Glossary.json, 0220CategoryHierarchy.json, 
> 0230Terms.json, 0250RelatedTerms.json, 0260Contexts.json, 
> 0270SemanticAssignment.json, 0280SpineObjects.json
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 60722: Fix for: Export of hive_table with fetchType "connected" fails

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60722/#review180695
---


Ship it!




Ship It!

- Madhan Neethiraj


On July 10, 2017, 3:59 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60722/
> ---
> 
> (Updated July 10, 2017, 3:59 p.m.)
> 
> 
> Review request for atlas and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-1919
> https://issues.apache.org/jira/browse/ATLAS-1919
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Analysis**
> The connected _fetchType_ in Export API had a potential for attempting to 
> save same entity twice.
> 
> **Fix**
> The entities saved to the _ZipSink_ are now maintained in a separate set. 
> Before attempting to save to _ZipSink_ existence check is performed. If 
> passed, save is prevented, else entity is saved to _ZipSink_.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
>  3538cfd7 
>   repository/src/main/java/org/apache/atlas/repository/impexp/ZipSink.java 
> 4bb04da9 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ZipSinkTest.java 
> 635caf7f 
> 
> 
> Diff: https://reviews.apache.org/r/60722/diff/2/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> - Executed existing unit tests.
> 
> **Functional tests**
> - Executed standard set of tests.
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Created] (ATLAS-1955) Validation for Attributes

[Israel Varea (JIRA)]

Israel Varea created ATLAS-1955:
---

 Summary: Validation for Attributes
 Key: ATLAS-1955
 URL: https://issues.apache.org/jira/browse/ATLAS-1955
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Israel Varea
 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 having:

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: org.apache.atlas.validators.creditcard 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: 

where  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|https://cwiki.apache.org/confluence/display/ATLAS/Area+5+-+Standards].

A similar approach is followed in software 
[Kylo|https://github.com/Teradata/kylo/tree/master/integrations/spark/spark-validate-cleanse]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-1839) Area 2 of the open metadata model

[Israel Varea (JIRA)]

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

Israel Varea commented on ATLAS-1839:
-

Thank you for your quick response.

* I have reviewed [ATLAS-1698|https://issues.apache.org/jira/browse/ATLAS-1698] 
and it covers all of the use cases we were looking for.
* Using spine objects seems to be a good solution for the relation of Term 
Objects and Term Attributtes. Thanks!
* I have created a new issue on attribute validation here: 
[ATLAS-1955|https://issues.apache.org/jira/browse/ATLAS-1955].

Cheers

> Area 2 of the open metadata model
> -
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: 0210Glossary.json, 0220CategoryHierarchy.json, 
> 0230Terms.json, 0250RelatedTerms.json, 0260Contexts.json, 
> 0270SemanticAssignment.json, 0280SpineObjects.json
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 2 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Testing API...

[Jean Georges Perrin]

Hi,

I installed and run Atlas on my Mac. Everything seems to be working fine in the 
UI, but I cannot get the API to work... I am sure it is really a small thing, 
but...

curl --user admin:admin -v http://localhost:21000/api/v2/search/basic 


returns:

*   Trying ::1...
* TCP_NODELAY set
* Connection failed
* connect to ::1 port 21000 failed: Connection refused
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 21000 (#0)
* Server auth using Basic with user 'admin'
> GET /api/v2/search/basic HTTP/1.1
> Host: localhost:21000
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.54.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Mon, 17 Jul 2017 18:42:49 GMT
< Set-Cookie: ATLASSESSIONID=14z2v5j9416lcibimeswa5it;Path=/;HttpOnly
< X-Frame-Options: DENY
< Content-Type: text/html; charset=ISO-8859-1
< Cache-Control: must-revalidate,no-cache,no-store
< Content-Length: 303
< Server: Jetty(9.2.12.v20150709)
<



Error 404 Not Found

HTTP ERROR 404
Problem accessing /api/v2/search/basic. Reason:
Not FoundPowered by Jetty://



* Connection #0 to host localhost left intact

Thanks!

jg

Re: Testing API...

[Madhan Neethiraj]

“/api/v2/search” is not the correct URI. Can you try  with 
“api/atlas/v2/search”?

Madhan



On 7/17/17, 11:51 AM, "Jean Georges Perrin"  wrote:

Hi,

I installed and run Atlas on my Mac. Everything seems to be working fine in 
the UI, but I cannot get the API to work... I am sure it is really a small 
thing, but...

curl --user admin:admin -v http://localhost:21000/api/v2/search/basic 


returns:

*   Trying ::1...
* TCP_NODELAY set
* Connection failed
* connect to ::1 port 21000 failed: Connection refused
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 21000 (#0)
* Server auth using Basic with user 'admin'
> GET /api/v2/search/basic HTTP/1.1
> Host: localhost:21000
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.54.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Mon, 17 Jul 2017 18:42:49 GMT
< Set-Cookie: ATLASSESSIONID=14z2v5j9416lcibimeswa5it;Path=/;HttpOnly
< X-Frame-Options: DENY
< Content-Type: text/html; charset=ISO-8859-1
< Cache-Control: must-revalidate,no-cache,no-store
< Content-Length: 303
< Server: Jetty(9.2.12.v20150709)
<



Error 404 Not Found

HTTP ERROR 404
Problem accessing /api/v2/search/basic. Reason:
Not FoundPowered by 
Jetty://



* Connection #0 to host localhost left intact

Thanks!

jg

Re: Testing API...

[Jean Georges Perrin]

Thanks Madhan! I knew it was something silly like that!

jg
 
> On Jul 17, 2017, at 2:56 PM, Madhan Neethiraj  wrote:
> 
> “/api/v2/search” is not the correct URI. Can you try  with 
> “api/atlas/v2/search”?
> 
> Madhan
> 
> 
> 
> On 7/17/17, 11:51 AM, "Jean Georges Perrin"  wrote:
> 
>Hi,
> 
>I installed and run Atlas on my Mac. Everything seems to be working fine 
> in the UI, but I cannot get the API to work... I am sure it is really a small 
> thing, but...
> 
>curl --user admin:admin -v http://localhost:21000/api/v2/search/basic 
> 
> 
>returns:
> 
>*   Trying ::1...
>* TCP_NODELAY set
>* Connection failed
>* connect to ::1 port 21000 failed: Connection refused
>*   Trying 127.0.0.1...
>* TCP_NODELAY set
>* Connected to localhost (127.0.0.1) port 21000 (#0)
>* Server auth using Basic with user 'admin'
>> GET /api/v2/search/basic HTTP/1.1
>> Host: localhost:21000
>> Authorization: Basic YWRtaW46YWRtaW4=
>> User-Agent: curl/7.54.1
>> Accept: */*
>> 
>< HTTP/1.1 404 Not Found
>< Date: Mon, 17 Jul 2017 18:42:49 GMT
>< Set-Cookie: ATLASSESSIONID=14z2v5j9416lcibimeswa5it;Path=/;HttpOnly
>< X-Frame-Options: DENY
>< Content-Type: text/html; charset=ISO-8859-1
>< Cache-Control: must-revalidate,no-cache,no-store
>< Content-Length: 303
>< Server: Jetty(9.2.12.v20150709)
><
>
>
>
>Error 404 Not Found
>
>HTTP ERROR 404
>Problem accessing /api/v2/search/basic. Reason:
>Not FoundPowered by 
> Jetty://
> 
>
>
>* Connection #0 to host localhost left intact
> 
>Thanks!
> 
>jg
> 
> 
> 
> 
> 

[jira] [Created] (ATLAS-1956) AtlasSearchResult to include filter attributes by default

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-1956:
--

 Summary: AtlasSearchResult to include filter attributes by default
 Key: ATLAS-1956
 URL: https://issues.apache.org/jira/browse/ATLAS-1956
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: trunk
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: trunk


If no attributes are specified in the SearchParameters then by default 
AtlasSearchResult should include the attributes present in the filter criteria



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Review Request 60923: ATLAS-1956: Search results should include the filter criteria attributes

[Apoorv Naik]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60923/
---

Review request for atlas, Madhan Neethiraj and Sarath Subramanian.


Bugs: ATLAS-1956
https://issues.apache.org/jira/browse/ATLAS-1956


Repository: atlas


Description
---

If no attributes are specified in the SearchParameters then by default 
AtlasSearchResult should include the attributes present in the filter criteria


Diffs
-

  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
a4538bda 
  repository/src/main/java/org/apache/atlas/discovery/SearchContext.java 
2125d610 
  repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
1a2d997b 


Diff: https://reviews.apache.org/r/60923/diff/1/


Testing
---

Tested using curl calls, response contains the attributes present in the filter 
criteria

mvn clean package executes successfully


Thanks,

Apoorv Naik

Review Request 60922: ATLAS-1925: Misc bugfixes for ATLAS-1880

[Apoorv Naik]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60922/
---

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
Subramanian.


Bugs: ATLAS-1925
https://issues.apache.org/jira/browse/ATLAS-1925


Repository: atlas


Description
---

Resolves ATLAS-1917, 1922, 1926


Diffs
-

  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
a4538bda 
  repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
1a2d997b 


Diff: https://reviews.apache.org/r/60922/diff/1/


Testing
---

mvn clean package executes successfully


Thanks,

Apoorv Naik

[jira] [Created] (ATLAS-1957) MultiVertex graph query

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-1957:
--

 Summary: MultiVertex graph query
 Key: ATLAS-1957
 URL: https://issues.apache.org/jira/browse/ATLAS-1957
 Project: Atlas
  Issue Type: Improvement
Affects Versions: trunk
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: trunk


There are lot of use cases where the graph query needs to be executed against a 
given set of vertices, right now the only way to do it to first determine a 
unique indexed attribute for those and then use that as the very first has 
condition filter.

e.g. graph.query().has("__guid", IN, Set guids)

This makes it difficult to perform hops in the graph traversal using the query 
API alone.

Titan0 and Titan1 has the ability to perform queries on multiple vertices in 
one go, which would benefit us in the future.

This enhancement will track the implementation of the MultiVertexQuery feature 
across Titan0 and Titan1



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1956) AtlasSearchResult to include filter attributes by default

[Apoorv Naik (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apoorv Naik updated ATLAS-1956:
---
Issue Type: Improvement  (was: Bug)

> AtlasSearchResult to include filter attributes by default
> -
>
> Key: ATLAS-1956
> URL: https://issues.apache.org/jira/browse/ATLAS-1956
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: trunk
>
>
> If no attributes are specified in the SearchParameters then by default 
> AtlasSearchResult should include the attributes present in the filter criteria



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-1958) Better graph traversal APIs

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-1958:
--

 Summary: Better graph traversal APIs 
 Key: ATLAS-1958
 URL: https://issues.apache.org/jira/browse/ATLAS-1958
 Project: Atlas
  Issue Type: Improvement
Reporter: Apoorv Naik
Assignee: Apoorv Naik


Right now the only way to perform deep/complex graph traversals is through the 
Gremlin API.
Currently atlas has an ExpressionFactory abstraction which internally generates 
groovy expression as per the compatible TinkerPop version. It requires solid 
understanding of the TypeSystem, gremlin query structure, required 
optimizations etc.

Instead, TinkerPop itself supports a Gremlin pipeline (TP2) and a 
GraphTraversal (TP3), which are good abstractions over the gremlin query 
language. We should have a Querying abstraction in Atlas which is agnostic to 
the underlying Graph implementation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Review Request 60927: ATLAS-1957: Multi-vertex atlas graph query

[Apoorv Naik]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60927/
---

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Sarath 
Subramanian, and Suma Shivaprasad.


Repository: atlas


Description
---

Initial draft for multi-vertex graph query in atlas


Diffs
-

  graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java 
dded76f8 
  
graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasMultiVertexQuery.java
 PRE-CREATION 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/NativeTitanMultiVertexQuery.java
 PRE-CREATION 
  
graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/NativeTitanQueryFactory.java
 ac7ff9e8 
  graphdb/titan0/pom.xml ceda1bb2 
  
graphdb/titan0/src/main/java/org/apache/atlas/repository/graphdb/titan0/Titan0Graph.java
 2408287b 
  
graphdb/titan0/src/main/java/org/apache/atlas/repository/graphdb/titan0/query/Titan0AtlasMultiVertexQuery.java
 PRE-CREATION 
  
graphdb/titan1/src/main/java/org/apache/atlas/repository/graphdb/titan1/Titan1Graph.java
 ffb6b37f 
  
graphdb/titan1/src/main/java/org/apache/atlas/repository/graphdb/titan1/query/Titan1AtlasMultiVertexQuery.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
 77b2c7c2 


Diff: https://reviews.apache.org/r/60927/diff/1/


Testing
---


Thanks,

Apoorv Naik

Re: Review Request 60927: ATLAS-1957: Multi-vertex atlas graph query

[Apoorv Naik]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60927/#review180754
---




repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
Lines 184 (patched)


TODO: The multi-vertex query will be used here


- Apoorv Naik


On July 17, 2017, 10:31 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60927/
> ---
> 
> (Updated July 17, 2017, 10:31 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Sarath 
> Subramanian, and Suma Shivaprasad.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Initial draft for multi-vertex graph query in atlas
> 
> 
> Diffs
> -
> 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java 
> dded76f8 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasMultiVertexQuery.java
>  PRE-CREATION 
>   
> graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/NativeTitanMultiVertexQuery.java
>  PRE-CREATION 
>   
> graphdb/common/src/main/java/org/apache/atlas/repository/graphdb/titan/query/NativeTitanQueryFactory.java
>  ac7ff9e8 
>   graphdb/titan0/pom.xml ceda1bb2 
>   
> graphdb/titan0/src/main/java/org/apache/atlas/repository/graphdb/titan0/Titan0Graph.java
>  2408287b 
>   
> graphdb/titan0/src/main/java/org/apache/atlas/repository/graphdb/titan0/query/Titan0AtlasMultiVertexQuery.java
>  PRE-CREATION 
>   
> graphdb/titan1/src/main/java/org/apache/atlas/repository/graphdb/titan1/Titan1Graph.java
>  ffb6b37f 
>   
> graphdb/titan1/src/main/java/org/apache/atlas/repository/graphdb/titan1/query/Titan1AtlasMultiVertexQuery.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
>  77b2c7c2 
> 
> 
> Diff: https://reviews.apache.org/r/60927/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

Re: Review Request 60922: ATLAS-1925: Misc bugfixes for ATLAS-1880

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60922/#review180763
---


Fix it, then Ship it!




Ship It!


repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java
Lines 479 (patched)


keep this inside a finally {} block, to ensure that search-context gets 
removed when search method exits.


- Madhan Neethiraj


On July 17, 2017, 9:37 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60922/
> ---
> 
> (Updated July 17, 2017, 9:37 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-1925
> https://issues.apache.org/jira/browse/ATLAS-1925
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Resolves ATLAS-1917, 1922, 1926
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java
>  a4538bda 
>   repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
> 1a2d997b 
> 
> 
> Diff: https://reviews.apache.org/r/60922/diff/1/
> 
> 
> Testing
> ---
> 
> mvn clean package executes successfully
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

Re: Review Request 60923: ATLAS-1956: Search results should include the filter criteria attributes

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60923/#review180780
---


Ship it!




Ship It!

- Madhan Neethiraj


On July 17, 2017, 9:36 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60923/
> ---
> 
> (Updated July 17, 2017, 9:36 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-1956
> https://issues.apache.org/jira/browse/ATLAS-1956
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> If no attributes are specified in the SearchParameters then by default 
> AtlasSearchResult should include the attributes present in the filter criteria
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java
>  a4538bda 
>   repository/src/main/java/org/apache/atlas/discovery/SearchContext.java 
> 2125d610 
>   repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
> 1a2d997b 
> 
> 
> Diff: https://reviews.apache.org/r/60923/diff/1/
> 
> 
> Testing
> ---
> 
> Tested using curl calls, response contains the attributes present in the 
> filter criteria
> 
> mvn clean package executes successfully
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

[jira] [Created] (ATLAS-1959) Enhance relationship attributes to support different cardinality mappings

[Sarath Subramanian (JIRA)]

Sarath Subramanian created ATLAS-1959:
-

 Summary: Enhance relationship attributes to support different 
cardinality mappings
 Key: ATLAS-1959
 URL: https://issues.apache.org/jira/browse/ATLAS-1959
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Affects Versions: trunk, 0.9-incubating
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian


Improve relationship model to support create/update operations and the 
following cardinalities (previously supported using inverseReference):

* 1 to 1
* 1 to many
* many to 1
* many to many

Add unit tests for the above cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Review Request 60938: [ATLAS-1959]: Enhance relationship attributes to support different cardinality mappings

[Sarath Subramanian]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60938/
---

Review request for atlas and Madhan Neethiraj.


Bugs: ATLAS-1959
https://issues.apache.org/jira/browse/ATLAS-1959


Repository: atlas


Description
---

* Improve relationship model to support create/update operations and the 
following cardinalities (previously supported using inverseReference):
1 to 1
1 to many
many to 1
many to many


* Change legacyLabel flag in AtlasRelationshipEndDef to boolean flag.
* Add unit tests for the above cases.


Diffs
-

  addons/models/0010-base_model.json 303f3796 
  addons/models/0030-hive_model.json a795f0f3 
  addons/models/0050-falcon_model.json 7755fa86 
  addons/models/0060-hbase_model.json 1d264df4 
  addons/models/0080-storm_model.json 25360ff0 
  intg/src/main/java/org/apache/atlas/model/instance/AtlasEntity.java 68da6af1 
  intg/src/main/java/org/apache/atlas/model/instance/AtlasRelationship.java 
2de9bdf0 
  intg/src/main/java/org/apache/atlas/model/typedef/AtlasRelationshipDef.java 
fc820d49 
  
intg/src/main/java/org/apache/atlas/model/typedef/AtlasRelationshipEndDef.java 
f80ea895 
  intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java e94dd190 
  intg/src/main/java/org/apache/atlas/type/AtlasRelationshipType.java 841b66f7 
  intg/src/main/java/org/apache/atlas/type/AtlasStructType.java f97d7674 
  intg/src/test/java/org/apache/atlas/TestRelationshipUtilsV2.java PRE-CREATION 
  intg/src/test/java/org/apache/atlas/TestUtilsV2.java 9774583d 
  repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
6f6d74bc 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityGraphDiscoveryV1.java
 12e8bb1f 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasGraphUtilsV1.java
 cd9a47ad 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1.java
 3ff6fbef 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
 d4fdc257 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
 157f8cd2 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphRetriever.java
 f4257be7 
  
repository/src/test/java/org/apache/atlas/repository/impexp/ImportServiceTest.java
 de8e7ef3 
  
repository/src/test/java/org/apache/atlas/repository/impexp/ZipFileResourceTestUtils.java
 d9017319 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreHardDeleteV1Test.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreSoftDeleteV1Test.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipStoreV1Test.java
 67702231 
  
repository/src/test/resources/logging-v1-full/2c8c2622-c7aa-43be-8956-f47dd5f6bac4.json
 PRE-CREATION 
  
repository/src/test/resources/logging-v1-full/63a4b6f5-d0a4-484c-8cab-61c0c14b6c69.json
 PRE-CREATION 
  
repository/src/test/resources/logging-v1-full/974cbc3a-c9c9-4776-ae0e-357df2ea055f.json
 PRE-CREATION 
  repository/src/test/resources/logging-v1-full/atlas-export-info.json 
PRE-CREATION 
  repository/src/test/resources/logging-v1-full/atlas-export-order.json 
PRE-CREATION 
  repository/src/test/resources/logging-v1-full/atlas-typesdef.json 
PRE-CREATION 
  
repository/src/test/resources/logging-v1-full/ec2ed3d2-b603-4948-bf2d-dde49411000a.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/221de408-7246-4988-82f7-fe889dad032e.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/42f82e22-ebb9-4f2e-b93a-6d436b239fad.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/7178713e-fc15-4406-86dd-da5a4f077257.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/84d079fc-6177-4937-a232-944aa35e568d.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/aa0bb6cf-f3db-4fb7-9c69-c67447b3b6ad.json
 PRE-CREATION 
  repository/src/test/resources/sales-v1-full/atlas-export-info.json 
PRE-CREATION 
  repository/src/test/resources/sales-v1-full/atlas-export-order.json 
PRE-CREATION 
  repository/src/test/resources/sales-v1-full/atlas-typesdef.json PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/bfe88eb8-7556-403c-8210-647013f44a44.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/ee35e6b3-8d6f-4815-9acd-3ef24c78ac49.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/ef3354e4-38c5-48fa-879f-552b1942034e.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/efdfafa5-d74b-4733-8f36-fdb05bc4adcf.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/f2dd85a6-3bc6-414e-b6bb-ca385592da28.json
 PRE-CREATION 
  
repository/src/test/resources/sales-v1-full/f69046b1-7518-45e

[jira] [Updated] (ATLAS-1959) Enhance relationship attributes to support different cardinality mappings

[Sarath Subramanian (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sarath Subramanian updated ATLAS-1959:
--
Attachment: ATLAS-1959.1.patch

> Enhance relationship attributes to support different cardinality mappings
> -
>
> Key: ATLAS-1959
> URL: https://issues.apache.org/jira/browse/ATLAS-1959
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Attachments: ATLAS-1959.1.patch
>
>
> Improve relationship model to support create/update operations and the 
> following cardinalities (previously supported using inverseReference):
> * 1 to 1
> * 1 to many
> * many to 1
> * many to many
> Add unit tests for the above cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1959) Enhance relationship attributes to support different cardinality mappings

[Sarath Subramanian (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sarath Subramanian updated ATLAS-1959:
--
Description: 
1. Improve relationship model to support create/update operations and the 
following cardinalities (previously supported using inverseReference):
* 1 to 1
* 1 to many
* many to 1
* many to many

2. Change legacyLabel flag in AtlasRelationshipEndDef to boolean flag.
3. Add unit tests for the above cases.

  was:
Improve relationship model to support create/update operations and the 
following cardinalities (previously supported using inverseReference):

* 1 to 1
* 1 to many
* many to 1
* many to many

Add unit tests for the above cases.


> Enhance relationship attributes to support different cardinality mappings
> -
>
> Key: ATLAS-1959
> URL: https://issues.apache.org/jira/browse/ATLAS-1959
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Attachments: ATLAS-1959.1.patch
>
>
> 1. Improve relationship model to support create/update operations and the 
> following cardinalities (previously supported using inverseReference):
> * 1 to 1
> * 1 to many
> * many to 1
> * many to many
> 2. Change legacyLabel flag in AtlasRelationshipEndDef to boolean flag.
> 3. Add unit tests for the above cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)