[jira] [Created] (ATLAS-2930) UI changes to handle error message based on softReference attribute.

2018-10-21 Thread Abhishek Kadam (JIRA) 
Abhishek Kadam created ATLAS-2930:
-

 Summary: UI changes to handle error message based on softReference 
attribute.
 Key: ATLAS-2930
 URL: https://issues.apache.org/jira/browse/ATLAS-2930
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.8.2
Reporter: Abhishek Kadam
Assignee: Abhishek Kadam
 Fix For: 0.8.3, 2.0.0, 1.2.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Atlas v 0.8.3 - RC0

2018-10-21 Thread Nixon Rodrigues 
+1 for the release of release-0.8.3-rc0


1) Tested with the rc0 bits with berkeley-elasticsearch profile.
2) UI loads fine.
3) Quickstart data loads correctly.
4) Verified signature & SHA512 hash.

Thanks, Ashutosh for putting for Apache Atlas
0.8.3 for release.

Thanks
Nixon


On Mon, Oct 22, 2018 at 11:01 AM Sharmadha Sainath 
wrote:

> +1 for the release
>
>
> 1.Verified the existing export & import functionality, incremental export,
> new options in the import , AtlasServer datatype and audits.
> 2.Verified Basic Search , DSL Search.
> 3.Verified the Basic UI functionalities such as search , navigate to
> entities , tag creation/association/disassociation.
>
> Thanks,
> Sharmadha S.
>
>
>
>
> On 10/21/18, 8:26 AM, "Apoorv Naik"  wrote:
>
> >+1 for the release Ashutosh.
> >
> >1. Verified signature
> >2. Built with embedded hbase and solr profile
> >3. Basic search and DSL works as expected
> >
> >Thanks for putting in the effort towards this release.
> >
> >*Apoorv Naik*
> >
> >
> >On Sat, Oct 20, 2018 at 11:35 AM Sarath Subramanian 
> >wrote:
> >
> >> Thanks Ashutosh for putting together release candidate #0 for Apache
> Atlas
> >> 0.8.3
> >>
> >> Verified the following:
> >>
> >>- Verified PGP Signature and hash
> >>- Build the source using embedded HBase and Solr profile, build was
> >>successful
> >>- Ran quick start and validated basic functionality - basic search,
> >>import-export, advanced search.
> >>
> >> +1 for release of Apache Atlas 0.8.3 rc0
> >>
> >> Thanks,
> >> Sarath
> >>
> >> On Wed, Oct 17, 2018 at 4:14 PM Ashutosh Mestry <
> ames...@hortonworks.com>
> >> wrote:
> >>
> >> > Apache Atlas 0.8.3 Release Candidate #0 is now available for a vote
> >> within
> >> > dev community.
> >> >
> >> > Links to the release artifacts are given below. Please review and
> vote.
> >> >
> >> > The vote will be open for at least 72 hours or until necessary votes
> are
> >> > reached.
> >> >   [ ] +1 approve
> >> >   [ ] +0 no opinion
> >> >   [ ] -1 disapprove (and reason why)
> >> >
> >> > Ashutosh Mestry
> >> >
> >> > List of issues addressed in this release:
> >> >
> >>
> https://issues.apache.org/jira/browse/ATLAS-2924?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.3%20ORDER%20BY%20key%20DESC
> >> >
> >> > Git tag for the release:
> >> > https://github.com/apache/atlas/tree/release-0.8.3-rc0
> >> >
> >> > Sources for the release:
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz
> >> >
> >> > Source release verification:
> >> > PGP Signature:
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.asc
> >> > SHA512
> >> > <
> >>
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.ascSHA512
> >> >
> >> > Hash:
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.sha512
> >> >
> >> > Keys to verify the signature of the release artifacts are available
> at:
> >> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> >> >
> >> >
> >> >
> >>
>

Re: [VOTE] Release Apache Atlas v 0.8.3 - RC0

2018-10-21 Thread Sharmadha Sainath 
+1 for the release


1.Verified the existing export & import functionality, incremental export, new 
options in the import , AtlasServer datatype and audits.
2.Verified Basic Search , DSL Search.
3.Verified the Basic UI functionalities such as search , navigate to entities , 
tag creation/association/disassociation.

Thanks,
Sharmadha S.




On 10/21/18, 8:26 AM, "Apoorv Naik"  wrote:

>+1 for the release Ashutosh.
>
>1. Verified signature
>2. Built with embedded hbase and solr profile
>3. Basic search and DSL works as expected
>
>Thanks for putting in the effort towards this release.
>
>*Apoorv Naik*
>
>
>On Sat, Oct 20, 2018 at 11:35 AM Sarath Subramanian 
>wrote:
>
>> Thanks Ashutosh for putting together release candidate #0 for Apache Atlas
>> 0.8.3
>>
>> Verified the following:
>>
>>- Verified PGP Signature and hash
>>- Build the source using embedded HBase and Solr profile, build was
>>successful
>>- Ran quick start and validated basic functionality - basic search,
>>import-export, advanced search.
>>
>> +1 for release of Apache Atlas 0.8.3 rc0
>>
>> Thanks,
>> Sarath
>>
>> On Wed, Oct 17, 2018 at 4:14 PM Ashutosh Mestry 
>> wrote:
>>
>> > Apache Atlas 0.8.3 Release Candidate #0 is now available for a vote
>> within
>> > dev community.
>> >
>> > Links to the release artifacts are given below. Please review and vote.
>> >
>> > The vote will be open for at least 72 hours or until necessary votes are
>> > reached.
>> >   [ ] +1 approve
>> >   [ ] +0 no opinion
>> >   [ ] -1 disapprove (and reason why)
>> >
>> > Ashutosh Mestry
>> >
>> > List of issues addressed in this release:
>> >
>> https://issues.apache.org/jira/browse/ATLAS-2924?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.3%20ORDER%20BY%20key%20DESC
>> >
>> > Git tag for the release:
>> > https://github.com/apache/atlas/tree/release-0.8.3-rc0
>> >
>> > Sources for the release:
>> >
>> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz
>> >
>> > Source release verification:
>> > PGP Signature:
>> >
>> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.asc
>> > SHA512
>> > <
>> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.ascSHA512
>> >
>> > Hash:
>> >
>> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.sha512
>> >
>> > Keys to verify the signature of the release artifacts are available at:
>> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
>> >
>> >
>> >
>>

[jira] [Commented] (ATLAS-2927) Update lineage query for Process entities

2018-10-21 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2927:


Commit 9653cc5d544ce07ffe236462ee09a32d58f75011 in atlas's branch 
refs/heads/branch-1.0 from [~sarath.ku...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=9653cc5 ]

ATLAS-2927: Update lineage query for Process entities

(cherry picked from commit 46b9b7c85835b1c4285eddce6c9773024a1b2114)


> Update lineage query for Process entities
> -
>
> Key: ATLAS-2927
> URL: https://issues.apache.org/jira/browse/ATLAS-2927
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.1.0
>
>
> Currently lineage query for process entities generates lineage based on the 
> number of hops on process entities. Lineage should be generated based on the 
> hops on DataSet entities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2927) Update lineage query for Process entities

2018-10-21 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2927:


Commit 46b9b7c85835b1c4285eddce6c9773024a1b2114 in atlas's branch 
refs/heads/master from [~sarath.ku...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=46b9b7c ]

ATLAS-2927: Update lineage query for Process entities


> Update lineage query for Process entities
> -
>
> Key: ATLAS-2927
> URL: https://issues.apache.org/jira/browse/ATLAS-2927
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.1.0
>
>
> Currently lineage query for process entities generates lineage based on the 
> number of hops on process entities. Lineage should be generated based on the 
> hops on DataSet entities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 69106: ATLAS-2927: Update lineage query for Process entities

2018-10-21 Thread Madhan Neethiraj 

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


Ship it!




Ship It!

- Madhan Neethiraj


On Oct. 20, 2018, 6:52 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69106/
> ---
> 
> (Updated Oct. 20, 2018, 6:52 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2927
> https://issues.apache.org/jira/browse/ATLAS-2927
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently lineage query for process entities generates lineage based on the 
> number of hops on process entities. Lineage should be generated based on the 
> hops on DataSet entities.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityLineageService.java 
> 6f2f97b7b 
>   
> repository/src/main/java/org/apache/atlas/util/AtlasGremlin3QueryProvider.java
>  866e5af51 
> 
> 
> Diff: https://reviews.apache.org/r/69106/diff/2/
> 
> 
> Testing
> ---
> 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/768/console
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

[jira] [Commented] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

2018-10-21 Thread Nagaraj Janardhana (JIRA) 


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

Nagaraj Janardhana commented on ATLAS-2928:
---

[~madhan.neethiraj] There are couple of interesting scenarios where 
Relationship-attribute names overlaps with entity attribute names.
 # By setting the relationship attribute it is also available as an entity 
attribute (atleast for end1). Hence the value is available both as a property 
and relationship. Hence there is no need to set/maintain values 2 times, 
instead the system takes care of maintaining it.
 # In the underlying graph store there is only one relationship between the 2 
entites and things are simpler, instead of 2 if which would be the case if 
attribute names (relationship and entity) are different.

The one caveat i see is the behavior is different for end2, in case 
relationship attribute name and entity attribute name being same then entity 
attribute is always null. 

Not sure if the existing beahvior is intentional but it is interesting as it 
might be useful to have relationship attribute map to an entity attribute as 
well in cases.

> Namespace entity relationship-attribute names to avoid conflict with entity 
> attributes
> --
>
> Key: ATLAS-2928
> URL: https://issues.apache.org/jira/browse/ATLAS-2928
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0, 1.2.0
>
>
> Apache Atlas 1.0 introduced relationships as first-class types. A 
> relationship effectively 'injects' an attribute on the entities at each end. 
> For example, assignment of a glossary term to an entity is captured by 
> relationship AtlasGlossarySemanticAssignment (in 
> -Area0/0011-glossary_model.json). This relationship adds following 
> attributes:
> - Referceable.meanings: set
> - AtlasGlossaryTerm.assignedEntities: set
> This works fine as long as the entity-types involved in the relationship, or 
> their sub-types don't have an attribute with the same name as the attribute 
> injected by the relationships. Once such instance was reported by [~bolke], 
> about relationship attribute DataSet.schema introduced by 
> avro_schema_associatedEntities - which conflicts with spark_table.schema, 
> since spark_table type is a sub-type of DataSet.
> Such name conflicts can be avoided by prefixing relationship-attribute names 
> with a prefix like "r:".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-2929) Fix netty issues when running with embedded Cassandra

2018-10-21 Thread Apoorv Naik (JIRA) 


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

Apoorv Naik resolved ATLAS-2929.

Resolution: Fixed

> Fix netty issues when running with embedded Cassandra
> -
>
> Key: ATLAS-2929
> URL: https://issues.apache.org/jira/browse/ATLAS-2929
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
>
> This is resolved by pull request # 13 on Github



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2929) Fix netty issues when running with embedded Cassandra

2018-10-21 Thread Apoorv Naik (JIRA) 


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

Apoorv Naik commented on ATLAS-2929:


Fixes ATLAS-2919

> Fix netty issues when running with embedded Cassandra
> -
>
> Key: ATLAS-2929
> URL: https://issues.apache.org/jira/browse/ATLAS-2929
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
>
> This is resolved by pull request # 13 on Github



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2919) Install ATLAS into Azure Virtual Machine

2018-10-21 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2919:


Commit 23e61364f8ce2a56a859c98affbbd3bcaf6170c0 in atlas's branch 
refs/heads/branch-1.0 from [~zdmytriv]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=23e6136 ]

ATLAS-2919: Fixed issue with Cassandra and Netty

Signed-off-by: apoorvnaik 

(cherry picked from commit 3b8a34c51eeadb54adeed78bea1e1ec3b03e279f)


> Install ATLAS into Azure Virtual Machine
> 
>
> Key: ATLAS-2919
> URL: https://issues.apache.org/jira/browse/ATLAS-2919
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mahender Shankesi
>Priority: Major
> Attachments: application.log
>
>
> I'm trying to install Atlas into my Azure Virtual Machine. I have followed 
> the steps from the below location.
> [https://atlas.apache.org/InstallationSteps.html]
> I'm able to start atlas_start but when I execute curl command I got the below 
> error
> $ curl -u admin:admin 
> [http://myip:21000/api/atlas/admin/version|http://10.41.64.19:21000/api/atlas/admin/version]
> curl: (7) Failed to connect to myip port 21000: Connection refused
> $ curl -u admin:admin 
> [https://myip/api/atlas/admin/version|https://10.41.64.19:21443/api/atlas/admin/version]
> curl: (7) Failed to connect to myip port 21443: Connection refused
> I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my ip. 
> None of them seems to be working.
>  
> $ netstat -a | grep 21000
> netstat -a | grep 21443
> Didn't return anything
>  
> Debug further and found that Cassandra is an issue. I reached out to dev team 
> and I got below response
> {color:#22}"This looks like an issue with the packaging, a wrong version 
> of netty is getting pulled in. ll try to find the source and update the 
> thread" {color}
>  
> {color:#22}I'm attaching the application log for this ticket. {color}
>  
> {color:#22}For better transparency and visibility I'm creating a Jira 
> ticket so that if anyone else has the same issue they can also look into 
> it.{color}
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2919) Install ATLAS into Azure Virtual Machine

2018-10-21 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2919:


Commit 3b8a34c51eeadb54adeed78bea1e1ec3b03e279f in atlas's branch 
refs/heads/master from [~zdmytriv]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=3b8a34c ]

ATLAS-2919: Fixed issue with Cassandra and Netty

Signed-off-by: apoorvnaik 


> Install ATLAS into Azure Virtual Machine
> 
>
> Key: ATLAS-2919
> URL: https://issues.apache.org/jira/browse/ATLAS-2919
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mahender Shankesi
>Priority: Major
> Attachments: application.log
>
>
> I'm trying to install Atlas into my Azure Virtual Machine. I have followed 
> the steps from the below location.
> [https://atlas.apache.org/InstallationSteps.html]
> I'm able to start atlas_start but when I execute curl command I got the below 
> error
> $ curl -u admin:admin 
> [http://myip:21000/api/atlas/admin/version|http://10.41.64.19:21000/api/atlas/admin/version]
> curl: (7) Failed to connect to myip port 21000: Connection refused
> $ curl -u admin:admin 
> [https://myip/api/atlas/admin/version|https://10.41.64.19:21443/api/atlas/admin/version]
> curl: (7) Failed to connect to myip port 21443: Connection refused
> I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my ip. 
> None of them seems to be working.
>  
> $ netstat -a | grep 21000
> netstat -a | grep 21443
> Didn't return anything
>  
> Debug further and found that Cassandra is an issue. I reached out to dev team 
> and I got below response
> {color:#22}"This looks like an issue with the packaging, a wrong version 
> of netty is getting pulled in. ll try to find the source and update the 
> thread" {color}
>  
> {color:#22}I'm attaching the application log for this ticket. {color}
>  
> {color:#22}For better transparency and visibility I'm creating a Jira 
> ticket so that if anyone else has the same issue they can also look into 
> it.{color}
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2929) Fix netty issues when running with embedded Cassandra

2018-10-21 Thread Apoorv Naik (JIRA) 
Apoorv Naik created ATLAS-2929:
--

 Summary: Fix netty issues when running with embedded Cassandra
 Key: ATLAS-2929
 URL: https://issues.apache.org/jira/browse/ATLAS-2929
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.1.0, 2.0.0


This is resolved by pull request # 13 on Github



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

2018-10-21 Thread Madhan Neethiraj (JIRA) 


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

Madhan Neethiraj updated ATLAS-2928:

Description: 
Apache Atlas 1.0 introduced relationships as first-class types. A relationship 
effectively 'injects' an attribute on the entities at each end. For example, 
assignment of a glossary term to an entity is captured by relationship 
AtlasGlossarySemanticAssignment (in -Area0/0011-glossary_model.json). This 
relationship adds following attributes:
- Referceable.meanings: set
- AtlasGlossaryTerm.assignedEntities: set

This works fine as long as the entity-types involved in the relationship, or 
their sub-types don't have an attribute with the same name as the attribute 
injected by the relationships. Once such instance was reported by [~bolke], 
about relationship attribute DataSet.schema introduced by 
avro_schema_associatedEntities - which conflicts with spark_table.schema, since 
spark_table type is a sub-type of DataSet.

Such name conflicts can be avoided by prefixing relationship-attribute names 
with a prefix like "r:".

> Namespace entity relationship-attribute names to avoid conflict with entity 
> attributes
> --
>
> Key: ATLAS-2928
> URL: https://issues.apache.org/jira/browse/ATLAS-2928
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0, 1.2.0
>
>
> Apache Atlas 1.0 introduced relationships as first-class types. A 
> relationship effectively 'injects' an attribute on the entities at each end. 
> For example, assignment of a glossary term to an entity is captured by 
> relationship AtlasGlossarySemanticAssignment (in 
> -Area0/0011-glossary_model.json). This relationship adds following 
> attributes:
> - Referceable.meanings: set
> - AtlasGlossaryTerm.assignedEntities: set
> This works fine as long as the entity-types involved in the relationship, or 
> their sub-types don't have an attribute with the same name as the attribute 
> injected by the relationships. Once such instance was reported by [~bolke], 
> about relationship attribute DataSet.schema introduced by 
> avro_schema_associatedEntities - which conflicts with spark_table.schema, 
> since spark_table type is a sub-type of DataSet.
> Such name conflicts can be avoided by prefixing relationship-attribute names 
> with a prefix like "r:".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

2018-10-21 Thread Madhan Neethiraj (JIRA) 


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

Madhan Neethiraj updated ATLAS-2928:

Component/s:  atlas-core

> Namespace entity relationship-attribute names to avoid conflict with entity 
> attributes
> --
>
> Key: ATLAS-2928
> URL: https://issues.apache.org/jira/browse/ATLAS-2928
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0, 1.2.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

2018-10-21 Thread Madhan Neethiraj (JIRA) 


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

Madhan Neethiraj updated ATLAS-2928:

Fix Version/s: 1.2.0
   2.0.0

> Namespace entity relationship-attribute names to avoid conflict with entity 
> attributes
> --
>
> Key: ATLAS-2928
> URL: https://issues.apache.org/jira/browse/ATLAS-2928
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0, 1.2.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

2018-10-21 Thread Madhan Neethiraj (JIRA) 


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

Madhan Neethiraj updated ATLAS-2928:

Affects Version/s: 1.1.0
   1.0.0

> Namespace entity relationship-attribute names to avoid conflict with entity 
> attributes
> --
>
> Key: ATLAS-2928
> URL: https://issues.apache.org/jira/browse/ATLAS-2928
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

2018-10-21 Thread Madhan Neethiraj (JIRA) 


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

Madhan Neethiraj updated ATLAS-2928:

Summary: Namespace entity relationship-attribute names to avoid conflict 
with entity attributes  (was: Scope entity attributes from relationships, to 
avoid confl)

> Namespace entity relationship-attribute names to avoid conflict with entity 
> attributes
> --
>
> Key: ATLAS-2928
> URL: https://issues.apache.org/jira/browse/ATLAS-2928
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2928) Scope entity attributes from relationships, to avoid confl

2018-10-21 Thread Madhan Neethiraj (JIRA) 
Madhan Neethiraj created ATLAS-2928:
---

 Summary: Scope entity attributes from relationships, to avoid confl
 Key: ATLAS-2928
 URL: https://issues.apache.org/jira/browse/ATLAS-2928
 Project: Atlas
  Issue Type: Bug
Reporter: Madhan Neethiraj






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-2925) Better logging for graph database initialization error

2018-10-21 Thread Madhan Neethiraj (JIRA) 


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

Madhan Neethiraj resolved ATLAS-2925.
-
   Resolution: Fixed
Fix Version/s: (was: trunk)
   1.2.0
   2.0.0

[~gm_coringa] - thanks for the patch.

> Better logging for graph database initialization error
> --
>
> Key: ATLAS-2925
> URL: https://issues.apache.org/jira/browse/ATLAS-2925
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Fabiano V. Santos
>Priority: Minor
> Fix For: 2.0.0, 1.2.0
>
>
> Any exception thrown during the graph database initialization only logs its 
> message, without the stack trace, so the real reason of a failure is not 
> logged.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2925) Better logging for graph database initialization error

2018-10-21 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2925:


Commit 95ac4f489ec0cef979a1968ad163a52721b50a71 in atlas's branch 
refs/heads/branch-1.0 from [~gm_coringa]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=95ac4f4 ]

ATLAS-2925: Better logging for graph database initialization error

Signed-off-by: Madhan Neethiraj 
(cherry picked from commit f5fd57475d8aec1a41d694f9f8bd6337ab9a8560)


> Better logging for graph database initialization error
> --
>
> Key: ATLAS-2925
> URL: https://issues.apache.org/jira/browse/ATLAS-2925
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Fabiano V. Santos
>Priority: Minor
> Fix For: trunk
>
>
> Any exception thrown during the graph database initialization only logs its 
> message, without the stack trace, so the real reason of a failure is not 
> logged.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2925) Better logging for graph database initialization error

2018-10-21 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2925:


Commit f5fd57475d8aec1a41d694f9f8bd6337ab9a8560 in atlas's branch 
refs/heads/master from [~gm_coringa]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=f5fd574 ]

ATLAS-2925: Better logging for graph database initialization error

Signed-off-by: Madhan Neethiraj 


> Better logging for graph database initialization error
> --
>
> Key: ATLAS-2925
> URL: https://issues.apache.org/jira/browse/ATLAS-2925
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Fabiano V. Santos
>Priority: Minor
> Fix For: trunk
>
>
> Any exception thrown during the graph database initialization only logs its 
> message, without the stack trace, so the real reason of a failure is not 
> logged.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 69106: ATLAS-2927: Update lineage query for Process entities

2018-10-21 Thread Madhan Neethiraj 

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


Ship it!




Ship It!

- Madhan Neethiraj


On Oct. 20, 2018, 6:52 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69106/
> ---
> 
> (Updated Oct. 20, 2018, 6:52 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2927
> https://issues.apache.org/jira/browse/ATLAS-2927
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently lineage query for process entities generates lineage based on the 
> number of hops on process entities. Lineage should be generated based on the 
> hops on DataSet entities.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityLineageService.java 
> 6f2f97b7b 
>   
> repository/src/main/java/org/apache/atlas/util/AtlasGremlin3QueryProvider.java
>  866e5af51 
> 
> 
> Diff: https://reviews.apache.org/r/69106/diff/1/
> 
> 
> Testing
> ---
> 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/768/console
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>