[jira] [Updated] (ATLAS-4068) Export/Import Service: Conditionally Support Multiple Operations

[Ashutosh Mestry (Jira)]

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

Ashutosh Mestry updated ATLAS-4068:
---
Attachment: ATLAS-4068-Support-simultaneous-export-and-import-op.patch

> Export/Import Service: Conditionally Support Multiple Operations
> 
>
> Key: ATLAS-4068
> URL: https://issues.apache.org/jira/browse/ATLAS-4068
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: 
> ATLAS-4068-Support-simultaneous-export-and-import-op.patch
>
>
> *Background*
> Existing implementation for Export & Import REST APIs disallows more than one 
> operation at a time.
> *Solution*
> Loosen the criteria based on request:
>  * Export: _AtlasExportRequest_: _skipLineage_ and _replicatedTo_ is selected.
>  * Import: _AtlasImportRequest_: _replicatedFrom_ is selected.
> Operations where these options are not specified, the existing behavior will 
> continue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-4068) Export/Import Service: Conditionally Support Multiple Operations

[Ashutosh Mestry (Jira)]

Ashutosh Mestry created ATLAS-4068:
--

 Summary: Export/Import Service: Conditionally Support Multiple 
Operations
 Key: ATLAS-4068
 URL: https://issues.apache.org/jira/browse/ATLAS-4068
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 2.1.0
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
 Fix For: trunk


*Background*

Existing implementation for Export & Import REST APIs disallows more than one 
operation at a time.

*Solution*

Loosen the criteria based on request:
 * Export: _AtlasExportRequest_: _skipLineage_ and _replicatedTo_ is selected.
 * Import: _AtlasImportRequest_: _replicatedFrom_ is selected.

Operations where these options are not specified, the existing behavior will 
continue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Atlas Eclipse setup

[Sarath Subramanian]

You can checkout Eclipse setup instructions for Atlas here -
http://atlas.apache.org/#/EclipseSetup


Thanks,
Sarath

On Tue, Dec 8, 2020 at 6:16 AM Chinmaya Padhi 
wrote:

> Hello developers,
>
> Has anyone tried recently to do the Eclipse setup of the Atlas project ?
> Is it straightforward ?
>
> Thanks and regards,
> Chinmaya kumar
>

Re: Review Request 73064: ATLAS-4059 - Rename Configuration flag for importing internal Kafka topics

[Ashutosh Mestry via Review Board]

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


Ship it!




Ship It!

- Ashutosh Mestry


On Dec. 7, 2020, 3:44 p.m., Deep Singh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73064/
> ---
> 
> (Updated Dec. 7, 2020, 3:44 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Sarath Subramanian, and Sidharth 
> Mishra.
> 
> 
> Bugs: ATLAS-4059
> https://issues.apache.org/jira/browse/ATLAS-4059
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 'atlas.hook.kafka.import.internal.topics' flag was introduced through 
> ATLAS-4043 to enable import of Kafka internal topics. 
> Rename it to better flag 'atlas.kafka.bridge.enable.internal.topics.import'
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/utils/KafkaUtils.java 7e9f7897d 
> 
> 
> Diff: https://reviews.apache.org/r/73064/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Deep Singh
> 
>

[jira] [Updated] (ATLAS-4067) In Entity Audits tab, show action as "user-defined properties added/updated/deleted" instead of plain 'Entity Updated'

[Umesh Padashetty (Jira)]

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

Umesh Padashetty updated ATLAS-4067:

Description: 
Currently in the entity audits tab, we show actions as below:
 * Business Attribute(s) Updated
 * Classification Added
 * Label(s) Added

!Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440!

But for user-defined properties alone, we show "Entity Updated" for all the udp 
actions. 

!Screenshot 2020-12-09 at 12.57.59 AM.png|width=1028,height=292!

This makes it very difficult to find out from the audits tab in which "Entity 
Update" action the udp was updated for an entity.

Though the user can expand the operation and find out what happened with udp, 
this is not very intuitive

  was:
Currently in the entity audits tab, we show actions as below:
 * Business Attribute(s) Updated
 * Classification Added
 * Label(s) Added

!Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440!

But for user-defined properties alone, we show "Entity Updated" for all the udp 
actions. 

!Screenshot 2020-12-09 at 12.57.59 AM.png|width=1239,height=352!

This makes it very difficult to find out from the audits tab in which "Entity 
Update" action the udp was updated for an entity.

Though the user can expand the operation and find out what happened with udp, 
this is not very intuitive


> In Entity Audits tab, show action as "user-defined properties 
> added/updated/deleted" instead of plain 'Entity Updated'
> --
>
> Key: ATLAS-4067
> URL: https://issues.apache.org/jira/browse/ATLAS-4067
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-12-09 at 1.03.44 AM.png, Screenshot 
> 2020-12-09 at 12.57.59 AM.png
>
>
> Currently in the entity audits tab, we show actions as below:
>  * Business Attribute(s) Updated
>  * Classification Added
>  * Label(s) Added
> !Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440!
> But for user-defined properties alone, we show "Entity Updated" for all the 
> udp actions. 
> !Screenshot 2020-12-09 at 12.57.59 AM.png|width=1028,height=292!
> This makes it very difficult to find out from the audits tab in which "Entity 
> Update" action the udp was updated for an entity.
> Though the user can expand the operation and find out what happened with udp, 
> this is not very intuitive



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-4067) In Entity Audits tab, show action as "user-defined properties added/updated/deleted" instead of plain 'Entity Updated'

[Umesh Padashetty (Jira)]

Umesh Padashetty created ATLAS-4067:
---

 Summary: In Entity Audits tab, show action as "user-defined 
properties added/updated/deleted" instead of plain 'Entity Updated'
 Key: ATLAS-4067
 URL: https://issues.apache.org/jira/browse/ATLAS-4067
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 2.1.0
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-12-09 at 1.03.44 AM.png, Screenshot 
2020-12-09 at 12.57.59 AM.png

Currently in the entity audits tab, we show actions as below:
 * Business Attribute(s) Updated
 * Classification Added
 * Label(s) Added

!Screenshot 2020-12-09 at 1.03.44 AM.png!

But for user-defined properties alone, we show "Entity Updated" for all the udp 
actions. 

!Screenshot 2020-12-09 at 12.57.59 AM.png!

This makes it very difficult to find out from the audits tab in which "Entity 
Update" action the udp was updated for an entity.

Though the user can expand the operation and find out what happened with udp, 
this is not very intuitive



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4067) In Entity Audits tab, show action as "user-defined properties added/updated/deleted" instead of plain 'Entity Updated'

[Umesh Padashetty (Jira)]

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

Umesh Padashetty updated ATLAS-4067:

Description: 
Currently in the entity audits tab, we show actions as below:
 * Business Attribute(s) Updated
 * Classification Added
 * Label(s) Added

!Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440!

But for user-defined properties alone, we show "Entity Updated" for all the udp 
actions. 

!Screenshot 2020-12-09 at 12.57.59 AM.png|width=1239,height=352!

This makes it very difficult to find out from the audits tab in which "Entity 
Update" action the udp was updated for an entity.

Though the user can expand the operation and find out what happened with udp, 
this is not very intuitive

  was:
Currently in the entity audits tab, we show actions as below:
 * Business Attribute(s) Updated
 * Classification Added
 * Label(s) Added

!Screenshot 2020-12-09 at 1.03.44 AM.png!

But for user-defined properties alone, we show "Entity Updated" for all the udp 
actions. 

!Screenshot 2020-12-09 at 12.57.59 AM.png!

This makes it very difficult to find out from the audits tab in which "Entity 
Update" action the udp was updated for an entity.

Though the user can expand the operation and find out what happened with udp, 
this is not very intuitive


> In Entity Audits tab, show action as "user-defined properties 
> added/updated/deleted" instead of plain 'Entity Updated'
> --
>
> Key: ATLAS-4067
> URL: https://issues.apache.org/jira/browse/ATLAS-4067
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-12-09 at 1.03.44 AM.png, Screenshot 
> 2020-12-09 at 12.57.59 AM.png
>
>
> Currently in the entity audits tab, we show actions as below:
>  * Business Attribute(s) Updated
>  * Classification Added
>  * Label(s) Added
> !Screenshot 2020-12-09 at 1.03.44 AM.png|width=1017,height=440!
> But for user-defined properties alone, we show "Entity Updated" for all the 
> udp actions. 
> !Screenshot 2020-12-09 at 12.57.59 AM.png|width=1239,height=352!
> This makes it very difficult to find out from the audits tab in which "Entity 
> Update" action the udp was updated for an entity.
> Though the user can expand the operation and find out what happened with udp, 
> this is not very intuitive



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties

[Umesh Padashetty (Jira)]

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

Umesh Padashetty updated ATLAS-4066:

Component/s: atlas-webui

> [UI] Attribute Filter: 'is null' and 'is not null' does not work for 
> user-defined properties 
> -
>
> Key: ATLAS-4066
> URL: https://issues.apache.org/jira/browse/ATLAS-4066
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-12-08 at 11.56.36 PM.png, Screenshot 
> 2020-12-08 at 11.56.45 PM.png, Screenshot 2020-12-08 at 11.56.54 PM.png
>
>
> For user-defined properties, currently only 'contains' filter is working. 
> !Screenshot 2020-12-08 at 11.56.54 PM.png!
> When I select either 'is null' or 'is not null', nothing happens (both when i 
> click on apply or search)
> !Screenshot 2020-12-08 at 11.56.45 PM.png!
> !Screenshot 2020-12-08 at 11.56.36 PM.png!
> 'is null' or 'is not null' works fine for all other System attributes 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties

[Umesh Padashetty (Jira)]

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

Umesh Padashetty updated ATLAS-4066:

Affects Version/s: 2.1.0

> [UI] Attribute Filter: 'is null' and 'is not null' does not work for 
> user-defined properties 
> -
>
> Key: ATLAS-4066
> URL: https://issues.apache.org/jira/browse/ATLAS-4066
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-12-08 at 11.56.36 PM.png, Screenshot 
> 2020-12-08 at 11.56.45 PM.png, Screenshot 2020-12-08 at 11.56.54 PM.png
>
>
> For user-defined properties, currently only 'contains' filter is working. 
> !Screenshot 2020-12-08 at 11.56.54 PM.png!
> When I select either 'is null' or 'is not null', nothing happens (both when i 
> click on apply or search)
> !Screenshot 2020-12-08 at 11.56.45 PM.png!
> !Screenshot 2020-12-08 at 11.56.36 PM.png!
> 'is null' or 'is not null' works fine for all other System attributes 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties

[Umesh Padashetty (Jira)]

Umesh Padashetty created ATLAS-4066:
---

 Summary: [UI] Attribute Filter: 'is null' and 'is not null' does 
not work for user-defined properties 
 Key: ATLAS-4066
 URL: https://issues.apache.org/jira/browse/ATLAS-4066
 Project: Atlas
  Issue Type: Bug
Reporter: Umesh Padashetty
 Attachments: Screenshot 2020-12-08 at 11.56.36 PM.png, Screenshot 
2020-12-08 at 11.56.45 PM.png, Screenshot 2020-12-08 at 11.56.54 PM.png

For user-defined properties, currently only 'contains' filter is working. 

!Screenshot 2020-12-08 at 11.56.54 PM.png!

When I select either 'is null' or 'is not null', nothing happens (both when i 
click on apply or search)

!Screenshot 2020-12-08 at 11.56.45 PM.png!

!Screenshot 2020-12-08 at 11.56.36 PM.png!

'is null' or 'is not null' works fine for all other System attributes 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DRAFT] Board report for Apache Atlas: December 2020

[Ashutosh Mestry]

Thanks for putting this together.

Looks good to me. No additional comments.

~ ashutosh
Ashutosh Mestry . Software Engineer
...
No hurry, no pause. – Tim Ferriss, Life Hacker, Author


From: Madhan Neethiraj 
Date: Sunday, December 6, 2020 at 11:44 PM
To: dev@atlas.apache.org 
Subject: [DRAFT] Board report for Apache Atlas: December 2020
Atlas team,

Please review the draft board report below and send your feedback/comments.

Thanks,
Madhan


## Description:
Apache Atlas is a scalable and extensible set of core foundational governance
services that enables enterprises to effectively and efficiently meet their
compliance requirements within Hadoop and allows integration with the complete
enterprise data ecosystem.

## Issues:
There are no issues requiring board attention at this time.

## Membership Data:
Apache Atlas was founded 2017-06-20 (3 years ago)
There are currently 43 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- No new PMC members. Last addition was Ashutosh Mestry on 2019-04-16.
- Pinal Shah was added as committer on 2020-11-02

## Project Activity:
 - the community is working on enhancements and fixes for next release
 - Atlas hooks enhancements to improve resiliency
 - updated admin audits to capture import/export, server start/activation events
 - performance improvements
 - updated version for a number of dependent libraries, like: Spring
   Framework, JQuery, Jetty, JanusGraph
 - enable easier reindexing using Java Patch framework
 - introduced Python client APIs for Atlas
 - added support for additional keystore and truststore types besides JKS

## Community Health:
 - dev@atlas.apache.org had a 7% decrease in traffic in the past quarter (1153
   emails compared to 1236)
 - u...@atlas.apache.org had a 34% decrease in traffic in the past quarter (20
   emails compared to 30)
 - 122 issues opened in JIRA, past quarter (14% increase)
 -  87 issues closed in JIRA, past quarter (27% increase)
 - 181 commits in the past quarter (39% increase)
 -  17 code contributors in the past quarter (-5% decrease)
 -   5 PRs opened on GitHub, past quarter (-50% decrease)
 -   2 PRs closed on GitHub, past quarter (-60% decrease)

## Releases:
  2.1.0was released on 07/16/2020
  0.8.4was released on 06/21/2019
  1.2.0was released on 06/12/2019
  2.0.0was released on 05/14/2019
  0.8.3was released on 10/31/2018
  1.1.0was released on 09/17/2018
  1.0.0was released on 06/02/2018
  0.8.2was released on 02/05/2018
  1.0.0-alpha  was released on 01/25/2018
  0.8.1was released on 08/29/2017
  0.8-incubating   was released on 03/16/2017
  0.7.1-incubating was released on 01/26/2017
  0.7-incubating   was released on 07/09/2016
  0.6-incubating   was released on 12/31/2015
  0.5-incubating   was released on 07/11/2015

Apache Atlas Eclipse setup

[Chinmaya Padhi]

Hello developers,

Has anyone tried recently to do the Eclipse setup of the Atlas project ?
Is it straightforward ?

Thanks and regards,
Chinmaya kumar

[jira] [Updated] (ATLAS-4065) TYPE_DEF_UPDATE audit does not reflect the right values

[Mandar Ambawane (Jira)]

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

Mandar Ambawane updated ATLAS-4065:
---
Attachment: ATLAS-4065.patch

> TYPE_DEF_UPDATE audit does not reflect the right values
> ---
>
> Key: ATLAS-4065
> URL: https://issues.apache.org/jira/browse/ATLAS-4065
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4065.patch
>
>
> 1) Create a type as user_1 and update it as user_2
> The update audit should reflects user_2 in the update audit
> userName field reflects the right value but the result field displays the 
> incorrect value
> 2) There is a mismatch in the Version



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Review Request 73072: ATLAS-4065 TYPE_DEF_UPDATE audit does not reflect the right values

[Mandar Ambawane]

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

Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, 
and Sarath Subramanian.


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


Repository: atlas


Description
---

This issue is coming from the Atlas Framework itself.

For every TypeDef Create operation there is subsequent Update call.

Similarly for every TypeDef Update operation there is subsequent Update call.

Some attributes are not getting set in the first Create / Update call of the 
TypeDef. Instead, they are getting set in the subsequent Update call.

This patch handles all these scenarios.


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/audit/TypeDefAuditListener.java
 4fe9f59 


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


Testing
---


Thanks,

Mandar Ambawane