Request to join Apache Atlas

[Radhika Kundam]

Hi Atlas Team,

I am interested in contributing to the Apache Atlas project, please add me
as a contributor.
My Apache Jira id is *radhikak*

Thank you,
Radhika

Review Request 72994: ATLAS-4010: Sort properties lexicographically in pom.xml for readability

[Radhika Kundam]

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

Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.


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


Repository: atlas


Description
---

Properties are in random order under  section in pom.xml

For better readability, need to sort properties in lexicographic order.


Diffs
-

  distro/pom.xml db1f23acd 
  docs/pom.xml f22f9e2ff 
  pom.xml aca36aaee 
  webapp/pom.xml 5a8cfe616 


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


Testing
---

Build is successful.


Thanks,

Radhika Kundam

Re: Review Request 72994: ATLAS-4010: Sort properties lexicographically in pom.xml for readability

[Radhika Kundam]

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

(Updated Oct. 30, 2020, 5:46 p.m.)


Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.


Changes
---

Removed the extra tabs as mentioned in comments.


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


Repository: atlas


Description
---

Properties are in random order under  section in pom.xml

For better readability, need to sort properties in lexicographic order.


Diffs
-

  distro/pom.xml db1f23acd 
  docs/pom.xml f22f9e2ff 
  pom.xml aca36aaee 
  webapp/pom.xml 5a8cfe616 


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


Testing
---

Build is successful.


File Attachments (updated)


Removing extra spaces
  
https://reviews.apache.org/media/uploaded/files/2020/10/30/40e165c6-985c-48e0-a61a-558ef4d9b2a3__0002-ATLAS-4010-Sort-properties-in-pom-removing-extra-spa.patch


Thanks,

Radhika Kundam

Re: Review Request 72994: ATLAS-4010: Sort properties lexicographically in pom.xml for readability

[Radhika Kundam]

> On Oct. 30, 2020, 5:43 a.m., Ashutosh Mestry wrote:
> > distro/pom.xml
> > Line 51 (original), 39 (patched)
> > <https://reviews.apache.org/r/72994/diff/1/?file=2241742#file2241742line51>
> >
> > nit: Remove extraneous tabs.

Fixed, attached the patach with updates.


- Radhika


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


On Oct. 30, 2020, 5:46 p.m., Radhika Kundam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72994/
> ---
> 
> (Updated Oct. 30, 2020, 5:46 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-4010
> https://issues.apache.org/jira/browse/ATLAS-4010
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Properties are in random order under  section in pom.xml
> 
> For better readability, need to sort properties in lexicographic order.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml db1f23acd 
>   docs/pom.xml f22f9e2ff 
>   pom.xml aca36aaee 
>   webapp/pom.xml 5a8cfe616 
> 
> 
> Diff: https://reviews.apache.org/r/72994/diff/1/
> 
> 
> Testing
> ---
> 
> Build is successful.
> 
> 
> File Attachments
> 
> 
> Removing extra spaces
>   
> https://reviews.apache.org/media/uploaded/files/2020/10/30/40e165c6-985c-48e0-a61a-558ef4d9b2a3__0002-ATLAS-4010-Sort-properties-in-pom-removing-extra-spa.patch
> 
> 
> Thanks,
> 
> Radhika Kundam
> 
>

Re: Review Request 72994: ATLAS-4010: Sort properties lexicographically in pom.xml for readability

[Radhika Kundam]

> On Oct. 30, 2020, 2:57 p.m., Madhan Neethiraj wrote:
> > distro/pom.xml
> > Line 51 (original), 39 (patched)
> > <https://reviews.apache.org/r/72994/diff/1/?file=2241742#file2241742line51>
> >
> > The value of property graph.index.properties is written to 
> > configuration file, refer to distro/src/conf/atlas-application.properties. 
> > Hence leading spaces should be avoided.

Fixed, attached the patach with updates.


- Radhika


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


On Oct. 30, 2020, 5:46 p.m., Radhika Kundam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72994/
> ---
> 
> (Updated Oct. 30, 2020, 5:46 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-4010
> https://issues.apache.org/jira/browse/ATLAS-4010
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Properties are in random order under  section in pom.xml
> 
> For better readability, need to sort properties in lexicographic order.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml db1f23acd 
>   docs/pom.xml f22f9e2ff 
>   pom.xml aca36aaee 
>   webapp/pom.xml 5a8cfe616 
> 
> 
> Diff: https://reviews.apache.org/r/72994/diff/1/
> 
> 
> Testing
> ---
> 
> Build is successful.
> 
> 
> File Attachments
> 
> 
> Removing extra spaces
>   
> https://reviews.apache.org/media/uploaded/files/2020/10/30/40e165c6-985c-48e0-a61a-558ef4d9b2a3__0002-ATLAS-4010-Sort-properties-in-pom-removing-extra-spa.patch
> 
> 
> Thanks,
> 
> Radhika Kundam
> 
>

Re: Review Request 72994: ATLAS-4010: Sort properties lexicographically in pom.xml for readability

[Radhika Kundam]

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

(Updated Nov. 2, 2020, 12:08 p.m.)


Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.


Changes
---

Removed the extra tab spaces for conf properties


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


Repository: atlas


Description
---

Properties are in random order under  section in pom.xml

For better readability, need to sort properties in lexicographic order.


Diffs (updated)
-

  distro/pom.xml db1f23acd 
  docs/pom.xml f22f9e2ff 
  pom.xml aca36aaee 
  webapp/pom.xml 5a8cfe616 


Diff: https://reviews.apache.org/r/72994/diff/2/

Changes: https://reviews.apache.org/r/72994/diff/1-2/


Testing
---

Build is successful.


File Attachments


Removing extra spaces
  
https://reviews.apache.org/media/uploaded/files/2020/10/30/40e165c6-985c-48e0-a61a-558ef4d9b2a3__0002-ATLAS-4010-Sort-properties-in-pom-removing-extra-spa.patch


Thanks,

Radhika Kundam

Re: Review Request 72994: ATLAS-4010: Sort properties lexicographically in pom.xml for readability

[Radhika Kundam]

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

(Updated Nov. 9, 2020, 2:17 p.m.)


Review request for atlas, Ashutosh Mestry and Madhan Neethiraj.


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


Repository: atlas


Description
---

Properties are in random order under  section in pom.xml

For better readability, need to sort properties in lexicographic order.


Diffs
-

  distro/pom.xml db1f23acd 
  docs/pom.xml f22f9e2ff 
  pom.xml aca36aaee 
  webapp/pom.xml 5a8cfe616 


Diff: https://reviews.apache.org/r/72994/diff/2/


Testing (updated)
---

Build is successful.
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/178/


File Attachments


Removing extra spaces
  
https://reviews.apache.org/media/uploaded/files/2020/10/30/40e165c6-985c-48e0-a61a-558ef4d9b2a3__0002-ATLAS-4010-Sort-properties-in-pom-removing-extra-spa.patch


Thanks,

Radhika Kundam

Review Request 73016: ATLAS-4026: Update Atlas with latest version of JanusGraph - 0.5.2

[Radhika Kundam]

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

Review request for atlas, Ashutosh Mestry and Sarath Subramanian.


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


Repository: atlas


Description
---

Atlas is using JanusGraph 0.5.1, update JanusGraph to latest version 0.5.2


Diffs
-

  pom.xml 13ff29967 


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


Testing
---


Thanks,

Radhika Kundam

Re: Review Request 73016: ATLAS-4026: Update Atlas with latest version of JanusGraph - 0.5.2

[Radhika Kundam]

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

(Updated Nov. 13, 2020, 2:56 p.m.)


Review request for atlas, Ashutosh Mestry and Sarath Subramanian.


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


Repository: atlas


Description
---

Atlas is using JanusGraph 0.5.1, update JanusGraph to latest version 0.5.2


Diffs
-

  pom.xml 13ff29967 


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


Testing (updated)
---

https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/189


Thanks,

Radhika Kundam

Re: Review Request 73016: ATLAS-4026: Update Atlas with latest version of JanusGraph - 0.5.2

[Radhika Kundam]

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

(Updated Nov. 16, 2020, 10:16 a.m.)


Review request for atlas, Ashutosh Mestry and Sarath Subramanian.


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


Repository: atlas


Description
---

Atlas is using JanusGraph 0.5.1, update JanusGraph to latest version 0.5.2


Diffs
-

  pom.xml 13ff29967 


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


Testing (updated)
---

https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/190


Thanks,

Radhika Kundam

Review Request 73017: ATLAS-4027: Update Atlas with latest version of slf4j - 1.7.30

[Radhika Kundam]

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

Review request for atlas, Ashutosh Mestry and Sarath Subramanian.


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


Repository: atlas


Description
---

Update Atlas with latest version of slf4j 1.7.30

In Atlas, latest slf4j version will be used for below jars.

slf4j-api

slf4j-log4j12 

jul-to-slf4j


Diffs
-

  pom.xml c5aafba95 


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


Testing
---


Thanks,

Radhika Kundam

Review Request 73018: ATLAS-4028: Update Atlas with latest version of httpclient and httpcore

[Radhika Kundam]

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

Review request for atlas, Ashutosh Mestry and Sarath Subramanian.


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


Repository: atlas


Description
---

Update Atlas with httpclient 4.5.13 & httpcore 4.4.13


Diffs
-

  addons/hbase-bridge/pom.xml 0907f47ee 
  addons/kafka-bridge/pom.xml 2b6a319ee 
  pom.xml c5aafba95 


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


Testing
---


Thanks,

Radhika Kundam

Re: Review Request 73018: ATLAS-4028: Update Atlas with latest version of httpclient and httpcore

[Radhika Kundam]

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

(Updated Nov. 17, 2020, 8:21 p.m.)


Review request for atlas, Ashutosh Mestry and Sarath Subramanian.


Changes
---

Updated httpclient to 4.5.13 and httpcore to 4.4.13


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


Repository: atlas


Description
---

Update Atlas with httpclient 4.5.13 & httpcore 4.4.13


Diffs
-

  addons/hbase-bridge/pom.xml 0907f47ee 
  addons/kafka-bridge/pom.xml 2b6a319ee 
  pom.xml c5aafba95 


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


Testing (updated)
---

https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/199/


Thanks,

Radhika Kundam

Review Request 73019: ATLAS-4013: JanusGraph 0.5.1 is not compatible with elasticsearch 5.*

[Radhika Kundam]

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

Review request for atlas, Ashutosh Mestry and Sarath Subramanian.


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


Repository: atlas


Description
---

Atlas failed to initialize RestElasticSearchClient, due to 
org.elasticsearch.client.Request is not compatible with the current 
elasticsearch version.
Updated ElasticSearch version to 6.6.0.


Diffs
-

  pom.xml c5aafba95 


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


Testing
---


Thanks,

Radhika Kundam

Re: Adding mandatory attribute to an existing entity type

[Radhika Kundam]

Hi,


   1. ATLAS-4181  is
   created to provide option for adding mandatory attributes to existing
   entity definitions and it is available in atlas versions 3.0.0 & 2.2.0


On a high level, this feature is supported by the Typedef patch with action
"ADD_MANDATORY_ATTRIBUTE", more details can be found in Jira ATLAS-4181


Thanks,
Radhika


On Wed, Jan 20, 2021 at 5:13 PM Jiaxin Ye  wrote:

> Hey Sreeni,
>
>
>
> Have you found the solution yet? We are facing the same issue when deleted
> an entity def and then recreated it with mandatory field.
>
>
>
> Thanks,
>
> Jiaxin
>
>
>
> *From: *Nallapati, Sreenivasulu 
> *Date: *Thursday, October 1, 2020 at 5:27 AM
> *To: *dev@atlas.apache.org , u...@atlas.apache.org <
> u...@atlas.apache.org>
> *Subject: *Adding mandatory attribute to an existing entity type
>
> Hi,
>
>
>
> We have an entity type (schema) with name, environment, schema_format as
> attributes and we have created few entities for this type.
>
> We want to add new mandatory attribute data_format to *schema* type. As
> atlas is not allowing to add a mandatory attribute, we followed the below
> steps to add the mandatory attribute
>
>
>
>1. Delete all the entities of this type from atlas.
>2. Delete the existing type using *curl -negotiate -u user:pwd -X
>DELETE -H 'Content-Type: application/json' -H 'Accept: application/json'
>"http://localhost:21000/api/atlas/v2/types/typedef/name/schema
>"*  API.
>   1. 
> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphManagement.deletePropertyKey(String)
>   method renamed all the three properties to schema.name_deleted_0,
>   schema.environment_deleted_0 and schema.schema_format_deleted_0
>3. After deleting the model, we posted the updated model with new
>mandatory attribute using *curl -negotiate -u user:pwd -X POST -H
>'Content-Type: application/json' -H 'Accept: application/json'
>"http://localhost:21000/api/atlas/v2/types/typedefs
>"  -d "@./schema.json"*
>4. Now graph management has new properties *name, environment,
>schema_format, data_format* and previously renamed properties 
> *name_deleted_0,
> environment_deleted_0, schema_format_deleted_0*
>5. When we try to create a new entity with the new model, the entity
>got created successfully in the backend store and failing to create the
>entity in the search store with the below error (because of mapped-type)
>
>
>
> Multiple entries with same key: schema.name
> =org.janusgraph.diskstorage.indexing.StandardKeyInformation@55e7c2b4 and
> schema.name
> =org.janusgraph.diskstorage.indexing.StandardKeyInformation@b884972
>
> at
> com.google.common.collect.ImmutableMap.conflictException(ImmutableMap.java:215)
>
> at
> com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:209)
>
> at
> com.google.common.collect.RegularImmutableMap.checkNoConflictInKeyBucket(RegularImmutableMap.java:147)
>
> at
> com.google.common.collect.RegularImmutableMap.fromEntryArray(RegularImmutableMap.java:110)
>
> at
> com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:393)
>
> at
> org.janusgraph.graphdb.database.IndexSerializer$IndexInfoRetriever$1.get(IndexSerializer.java:162)
>
>
>
>1. The renamed attributes (schema.name_deleted_0) has a property
>“mapped-name” to the schema.type attribute. While building the
>ImmutableMap, “mapped-name” of schema.name_deleted_0 is colliding with the
>schema.name
>
>
>
>
>
> Have few queries about this functionality.
>
>1. Is there any reason why properties are getting renamed instead of
>delete when we delete the model?
>2. Is there any configuration setting to tweak this functionality or
>How to add a mandatory attribute to the existing model type?
>3. Is it ok if we delete the renamed
>(m.getPropertyKey('schema.name_deleted_0').remove())properties from graph
>management using gremlin console?
>
>
>
> Please guide us in the proper direction if we are not doing the right
> thing.
>
>
>
>
>
>
>
> ---
>
> Regards,
>
> Sreeni
>

Re: Review Request 73172: ATLAS-4124 Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

[Radhika Kundam]

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




repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasBusinessMetadataDefStoreV2.java
Lines 413 (patched)
<https://reviews.apache.org/r/73172/#comment311978>

isBusinessAttrubitePresent can be formatted for easy understanding.

SearchParameters.FilterCriteria criteria = new 
SearchParameters.FilterCriteria();
criteria.setAttributeName(attrName);
criteria.setOperator(SearchParameters.Operator.NOT_EMPTY);

SearchParameters.FilterCriteria entityFilters = new 
SearchParameters.FilterCriteria();

entityFilters.setCondition(SearchParameters.FilterCriteria.Condition.OR);
entityFilters.setCriterion(Arrays.asList(criteria));

SearchParameters searchParameters = new SearchParameters();

searchParameters.setTypeName(String.join(SearchContext.TYPENAME_DELIMITER, 
applicableTypes));
searchParameters.setExcludeDeletedEntities(true);
searchParameters.setIncludeSubClassifications(false);
searchParameters.setEntityFilters(entityFilters);
searchParameters.setAttributes(Collections.singleton(attrName));
searchParameters.setOffset(0);
searchParameters.setLimit(1);

AtlasSearchResult atlasSearchResult = 
entityDiscoveryService.searchWithParameters(searchParameters);



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasBusinessMetadataDefStoreV2.java
Lines 435 (patched)
<https://reviews.apache.org/r/73172/#comment311980>

No need to check for getEntities() size again as it's  already validated by 
CollectionUtils.


- Radhika Kundam


On April 9, 2021, 12:38 a.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73172/
> ---
> 
> (Updated April 9, 2021, 12:38 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Nixon Rodrigues, 
> Pinal Shah, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4124
> https://issues.apache.org/jira/browse/ATLAS-4124
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> We can delete the entire BusinessMetadata TypeDef using the curl command.
> 
> But that will affect the entities which already have Business Attributes from 
> this Deleted Business Metadata.
> Those Business Attributes will be removed from the Entity.
> 
> This patch will restrict user from deleting Business Metadata, if Business 
> Metadata is already associated with an entity.
> 
> This patch adds support for Multi-Valued Attribute NOT NULL search in Basic 
> Serch.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/model/discovery/SearchParameters.java 
> 367c5b8 
>   intg/src/test/java/org/apache/atlas/TestUtilsV2.java 80ab6b4 
>   repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
> 275fc78 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasBusinessMetadataDefStoreV2.java
>  d0d54af 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasTypeDefGraphStoreV2.java
>  96fb3b4 
>   webapp/src/test/java/org/apache/atlas/web/adapters/TypeDefsRESTTest.java 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/73172/diff/6/
> 
> 
> Testing
> ---
> 
> Test cases added
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

Re: Review Request 73172: ATLAS-4124 Restrict user from deleting Business Metadata, if Business Metadata is already associated with an entity

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On April 12, 2021, 9 a.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73172/
> ---
> 
> (Updated April 12, 2021, 9 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Nixon Rodrigues, 
> Pinal Shah, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4124
> https://issues.apache.org/jira/browse/ATLAS-4124
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> We can delete the entire BusinessMetadata TypeDef using the curl command.
> 
> But that will affect the entities which already have Business Attributes from 
> this Deleted Business Metadata.
> Those Business Attributes will be removed from the Entity.
> 
> This patch will restrict user from deleting Business Metadata, if Business 
> Metadata is already associated with an entity.
> 
> This patch adds support for Multi-Valued Attribute NOT NULL search in Basic 
> Serch.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/model/discovery/SearchParameters.java 
> 367c5b8 
>   intg/src/test/java/org/apache/atlas/TestUtilsV2.java 80ab6b4 
>   repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
> 275fc78 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasBusinessMetadataDefStoreV2.java
>  d0d54af 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasTypeDefGraphStoreV2.java
>  96fb3b4 
>   webapp/src/test/java/org/apache/atlas/web/adapters/TypeDefsRESTTest.java 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/73172/diff/8/
> 
> 
> Testing
> ---
> 
> Test cases added
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

Re: Review Request 73404: ATLAS-4324: FS entity created for load data inpath is created as shell entity - Part 2

[Radhika Kundam]

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




addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/HiveDDLEntityFilter.java
Line 200 (original), 194 (patched)
<https://reviews.apache.org/r/73404/#comment312237>

This will keep negative guid not only to Path entity types but for all 
typesToRetain.IdBasedResolver will not be able to find the entities like 
hive_table with -ve guid which are already created. We need to keep negative 
guid only for Path entity types.


- Radhika Kundam


On June 4, 2021, 1:43 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73404/
> ---
> 
> (Updated June 4, 2021, 1:43 p.m.)
> 
> 
> Review request for atlas, Mandar Ambawane, Radhika Kundam, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-4324
> https://issues.apache.org/jira/browse/ATLAS-4324
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> Updates:
> - Simplified approach.
> - Maintained abstraction.
> - Updated unit tests.
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> 94ef22577 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/ActiveEntityFilter.java
>  737c637bf 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/HiveDDLEntityFilter.java
>  9163c4709 
>   
> addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/utils/ActiveEntityFilterTest.java
>  4dde1dc2f 
>   addons/hive-bridge/src/test/resources/json/hs2-create-db-v2.json 881ee105e 
>   
> addons/hive-bridge/src/test/resources/json/hs2-create-db-with-no-pathentities-to-retain-v2.json
>  42553b5cf 
>   
> addons/hive-bridge/src/test/resources/json/hs2-create-db-with-no-pathentities-to-retain.json
>  a5b810f72 
>   addons/hive-bridge/src/test/resources/json/hs2-create-process-v2.json 
> 8e55b7282 
>   addons/hive-bridge/src/test/resources/json/hs2-create-table-v2.json 
> 801918e04 
>   addons/hive-bridge/src/test/resources/json/hs2-load-inpath-v2.json 
> dd31aa073 
>   
> addons/hive-bridge/src/test/resources/json/hs2-load-inpath-with-no-pathentities-to-retain-v2.json
>  7f90d1986 
>   
> addons/hive-bridge/src/test/resources/json/hs2-load-inpath-with-no-pathentities-to-retain.json
>  dd31aa073 
>   addons/hive-bridge/src/test/resources/json/hs2-load-inpath.json dd31aa073 
>   addons/hive-bridge/src/test/resources/json/hs2-table-rename-v2.json 
> f2b2bf7a8 
> 
> 
> Diff: https://reviews.apache.org/r/73404/diff/2/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> - Additional unit test.
> 
> **PC Build**
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/617/
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 73404: ATLAS-4324: FS entity created for load data inpath is created as shell entity - Part 2

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On June 8, 2021, 4:07 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73404/
> ---
> 
> (Updated June 8, 2021, 4:07 p.m.)
> 
> 
> Review request for atlas, Mandar Ambawane, Radhika Kundam, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-4324
> https://issues.apache.org/jira/browse/ATLAS-4324
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> Updates:
> - Simplified approach.
> - Maintained abstraction.
> - Updated unit tests.
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> 94ef22577 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/ActiveEntityFilter.java
>  737c637bf 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/HiveDDLEntityFilter.java
>  9163c4709 
>   
> addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/utils/ActiveEntityFilterTest.java
>  4dde1dc2f 
>   addons/hive-bridge/src/test/resources/json/hs2-create-db-v2.json 881ee105e 
>   
> addons/hive-bridge/src/test/resources/json/hs2-create-db-with-no-pathentities-to-retain-v2.json
>  42553b5cf 
>   
> addons/hive-bridge/src/test/resources/json/hs2-create-db-with-no-pathentities-to-retain.json
>  a5b810f72 
>   addons/hive-bridge/src/test/resources/json/hs2-create-process-v2.json 
> 8e55b7282 
>   addons/hive-bridge/src/test/resources/json/hs2-create-table-v2.json 
> 801918e04 
>   addons/hive-bridge/src/test/resources/json/hs2-load-inpath-v2.json 
> dd31aa073 
>   
> addons/hive-bridge/src/test/resources/json/hs2-load-inpath-with-no-pathentities-to-retain-v2.json
>  7f90d1986 
>   
> addons/hive-bridge/src/test/resources/json/hs2-load-inpath-with-no-pathentities-to-retain.json
>  dd31aa073 
>   addons/hive-bridge/src/test/resources/json/hs2-load-inpath.json dd31aa073 
>   addons/hive-bridge/src/test/resources/json/hs2-table-rename-v2.json 
> f2b2bf7a8 
> 
> 
> Diff: https://reviews.apache.org/r/73404/diff/2/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> - Additional unit test.
> 
> **PC Build**
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/617/
> 
> 
> File Attachments
> 
> 
> Screen Shot 2021-06-08 at 4.05.26 PM.png
>   
> https://reviews.apache.org/media/uploaded/files/2021/06/08/b15b33fc-007d-4ee3-8862-64750af16432__Screen_Shot_2021-06-08_at_4.05.26_PM.png
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Planning for Apache Atlas 2.2.0 release

[Radhika Kundam]

Thanks for volunteering Sidharth.
+1 for Apache Atlas 2.2

Regards,
Radhika

On Tue, Jul 27, 2021 at 12:11 PM Sidharth Mishra 
wrote:

> Dear Atlas community,
>
> Since Apache Atlas 2.1 was released, there are many new features,
> improvements and fixes. Here are few features/enhancements since last
> release, Apache Atlas 2.1:
>
> - Introduced Deferred Action - Tag propagation will be handled as
> a background process (AtlasTask)
>
> - Added Re-indexing as JAVA_PATCH
>
> - Created JavaPatch to add new super types to existing entities
>
> - Supported for Business Metadata in Atlas Export API
>
> - Supported HA for admin/task API
>
> - Enhanced export service to export Terms
>
> - Added new models and addition attributes to Atlas for Apache
> Flink, GCP and ADLS Gen 2
>
> - Added support to Configure HiveServer2 Hook to send Lineage-only
> Messages
>
> - Improved and enhanced Bulk Glossary Import supporting import
> with relations
>
> - Dependency between Atlas and Kafka Zookeeper removed
>
> - Improved performance of GraphHelper's guid and status getter methods
>
> - Added new privilege - "admin-audits" for Atlas Admin Audits
> authorization
>
> - Basic search Improvements - search text with special characters,
> optimize pagination
>
> - Updated free-text search processor to support Elasticsearch
>
> - Refactored and enhanced Atlas Python Client supporting Python 2.7
>
> - DSL Search enhancements - Support glossary terms and
> relationship, can handle null attribute values, Java Tinkerpop
> Traversals instead of GremlinScriptEngine, support search by
> classification and its attribute, Caching mechanism for translated dsl
> queries
>
> - Enhanced Export/Import Service to conditionally Support
> Simultaneous Operations
>
> - Enhanced NotificationHookConsumer for Large Message Processing
>
> - Enhanced Atlas authorization for Add/Update/Remove
> classification on entities
>
> - Provided option to add mandatory attribute to existing entity
> definition
>
> - Fixed Atlas UI to load faster in case of large number of
> classifications & entities
>
> - Updated versions of dependent libraries/components: JanusGraph,
> elasticsearch, JQuery, Http core, Http Client, slf4j, log4j, ant,
> gremlin, Solr, groovy, netty, Kafka
>
> There are around 336 plus commits on branch 2.0 and 205 resolved
> issues with fix version 2.2.0 after 2.1.0 release.
> With these significant improvements in place, it is time for the next
> release of Apache Atlas!
>
> I propose to release Apache Atlas 2.2 by early next month. Please
> review and send your comments.
>
> Regards,
> Sidharth
>

Re: [VOTE] Release Apache Atlas version 2.2.0 - rc1

[Radhika Kundam]

Hi Sid,

+1 for Apache Atlas v2.2.0 rc1.

Verified the following

   - Clean Build and setup Atlas with embedded-hbase-solr
   - Created entities, classifications on Atlas UI
   - Verified Entity Audit data
   - Verified entity search with REST API
   - Verified Basic Search and Advanced Search
   - Verified Metrics


Thanks,
Radhika


On Wed, Aug 11, 2021 at 8:53 AM mayank jain <
mayank.j...@freestoneinfotech.com> wrote:

> Hi Sidharth
>
> +1 for Apache Atlas v2.2.0 rc1.
>
> Verified the following -
>  *  Clean build embedded-hbase-solr profile.
>  *  Bulk import of glossary amd Business metadata
>  *  Tested the metrics of atlas
>  *  Setup Atlas server in embedded HBase and Solr.
>  *  Verified md5, sha512, Signature
>  *  Verified Import zip with REST API
>  *  Ran quick start
>  *  Created entities, glossaries ,terms on Atlas UI
>
>
> Regards,
> Mayank Jain
>
> On Wed, Aug 11, 2021 at 6:21 PM Jayendra Parab 
> wrote:
>
> > Thanks Sidharth for putting this together for vote.
> >
> > +1 for 2.2.0 - rc1 release.
> >
> > Verified following:
> >   * MD5, SHA512, release signature
> >   * mvn build with embedded-hbase-solr
> >   * Setup Atlas server with embedded HBase and Solr.
> >   * Ran quick_start.py
> >   * Atlas UI loading cleanly.
> >   * Created entities using Atlas UI
> >   * Validated basic and DSL search
> >
> >
> > On Wed, Aug 11, 2021 at 1:14 PM Mandar Ambawane <
> > mandar.ambaw...@freestoneinfotech.com> wrote:
> >
> > > Hi Sidharth,
> > >
> > > +1 for Apache Atlas 2.2.0 rc1
> > >
> > > Verified following:
> > >
> > >- md5, sha512 signatures
> > >- mvn build with embedded-hbase-solr -DskipTests
> > >- Started Atlas server and did run quick start
> > >- Atlas UI loading cleanly
> > >- Created entities using Atlas UI
> > >- Validated basic search
> > >- Validated Admin audits
> > >
> > > Thanks,
> > > Mandar
> > >
> > > On Wed, Aug 11, 2021 at 12:06 PM Chaitali Borole <
> > > chaitali.bor...@freestoneinfotech.com> wrote:
> > >
> > > > Hello Sidharth,
> > > >
> > > > +1 for Apache Atlas 2.2.0 rc1
> > > >
> > > > Checked for below points:
> > > >   *  md5, sha512 signatures.
> > > >   *  Clean build with mvn clean package -Pdist,embedded-hbase-solr
> > > > -DskipTests -Drat.skip.
> > > >   *  Atlas server up and running.
> > > >   *  Re-indexing with JAVA_PATCH.
> > > >   *  Sanity checks :
> > > > quick_search,entities,relationship,tags,glossaries,metrics api.
> > > >   *  Quick start is successful.
> > > >
> > > > Thanks,
> > > > Chaitali.
> > > >
> > > > On Tue, Aug 10, 2021 at 4:25 AM Sidharth Mishra <
> sidmis...@apache.org>
> > > > wrote:
> > > >
> > > > > Atlas team,
> > > > >
> > > > > Apache Atlas 2.2.0 rc1, with the following fixes since rc0, is now
> > > > > available for vote within the dev community.
> > > > >
> > > > > ATLAS-4390 - Changed Atlas branch to release-2.2.0-rc1
> > > > > ATLAS-4391 - NoSuchFileException for
> > > > {atlas.log.dir}/atlas-metrics.out
> > > > > ATLAS-4343 - [Entity Audits] 'Propagated Classification Added'
> > > > > Timestamp is < 'Entity
> > > > > Created' Timestamp
> > > > > ATLAS-4387 - UI: Propagated Classifications shows wrong count
> for
> > > > > entity type on Entity
> >  detail
> > > > > page
> > > > > ATLAS-4386 - Relationship search: Sorting does not work when
> > > > > relationship label is passed
> > > > >
> > > > > 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)
> > > > >
> > > > > Thanks,
> > > > > Sid
> > > > >
> > > > > List of all issues addressed in this release:
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%3DATLAS%20AND%20status%3DResolved%20AND%20fixVersion%3D2.2.0%20ORDER%20BY%20key%20DESC
> > > > >
> > > > > Git tag for the release:
> > > > > https://github.com/apache/atlas/tree/release-2.2.0-rc1
> > > > >
> > > > > Sources for the release:
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.2.0-rc1/apache-atlas-2.2.0-sources.tar.gz
> > > > >
> > > > > Source release verification:
> > > > >
> > > > >   PGP Signature:
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.2.0-rc1/apache-atlas-2.2.0-sources.tar.gz.asc
> > > > >
> > > > >   SHA512 Hash:
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.2.0-rc1/apache-atlas-2.2.0-sources.tar.gz.sha512
> > > > >
> > > > >   MD5 Hash:
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.2.0-rc1/apache-atlas-2.2.0-sources.tar.gz.md5
> > > > >
> > > > >
> > > > > Keys to verify the signature of the release artifacts are available
> > > > > at: https://dist.apache.org/repos/dist/release/atlas/KE

Re: Review Request 73637: ATLAS-4370: Persist Metrics for user to retrieve Metrics info at a past timestamp

[Radhika Kundam]

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




intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMinInfo.java
Lines 44 (patched)
<https://reviews.apache.org/r/73637/#comment312719>

AtlasMetricsMinInfo logic looks complicated and it can be restructured 
along with AtlasMetricsStat to make it simple.



intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMinInfo.java
Lines 52 (patched)
<https://reviews.apache.org/r/73637/#comment312715>

AtlasMetricsMinInfo to handle single typeName is redundant as it can be 
handled using constructor at line#61 list of typenames. This constructor can be 
removed to avoid duplicated code.



intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMinInfo.java
Lines 74 (patched)
<https://reviews.apache.org/r/73637/#comment312716>

unused method



repository/src/main/java/org/apache/atlas/services/MetricsService.java
Lines 362 (patched)
<https://reviews.apache.org/r/73637/#comment312718>

Return type can be void



repository/src/main/java/org/apache/atlas/services/MetricsService.java
Lines 516 (patched)
<https://reviews.apache.org/r/73637/#comment312717>

Need null check for return value of getTypeData().


- Radhika Kundam


On Oct. 7, 2021, 4:50 p.m., Disha Talreja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73637/
> ---
> 
> (Updated Oct. 7, 2021, 4:50 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Sarath Subramanian, and Sidharth 
> Mishra.
> 
> 
> Bugs: ATLAS-4370
> https://issues.apache.org/jira/browse/ATLAS-4370
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Rebased patch #73483 (https://reviews.apache.org/r/73483/) against the newest 
> master branch.
> 
> 
> Diffs
> -
> 
>   addons/models/-Area0/0010-base_model.json 769d8859f 
>   intg/src/main/java/org/apache/atlas/AtlasConfiguration.java 20f8f7343 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 2febff469 
>   
> intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsBaseObject.java 
> PRE-CREATION 
>   
> intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMapToChart.java 
> PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMinInfo.java 
> PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsStat.java 
> PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/utils/AtlasEntityUtil.java 1e78e2550 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/metrics/AtlasMetricsStatDTO.java
>  PRE-CREATION 
>   repository/src/main/java/org/apache/atlas/services/MetricsService.java 
> ceb252822 
>   repository/src/main/java/org/apache/atlas/util/AtlasMetricsUtil.java 
> beb90e67b 
>   repository/src/test/java/org/apache/atlas/TestModules.java 8dda20825 
>   repository/src/test/java/org/apache/atlas/services/MetricsServiceTest.java 
> 040592184 
>   test-tools/src/main/resources/solr/core-template/solrconfig.xml e7956cb36 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> 135b94b36 
> 
> 
> Diff: https://reviews.apache.org/r/73637/diff/2/
> 
> 
> Testing
> ---
> 
> 1) Tested locally.
> 2) Patched a cluster.
> 
> PC build: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/880/
> 
> 
> Thanks,
> 
> Disha Talreja
> 
>

Re: Review Request 73637: ATLAS-4370: Persist Metrics for user to retrieve Metrics info at a past timestamp

[Radhika Kundam]

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




repository/src/main/java/org/apache/atlas/services/MetricsService.java
Line 42 (original), 51 (patched)
<https://reviews.apache.org/r/73637/#comment312805>

Please import only required util classes.



repository/src/main/java/org/apache/atlas/services/MetricsService.java
Lines 441 (patched)
<https://reviews.apache.org/r/73637/#comment312804>

Why do we need to map to AtlasMetricsStat as already allMetrics is List of 
AtlasMetricsStat



repository/src/main/java/org/apache/atlas/services/MetricsService.java
Lines 442 (patched)
<https://reviews.apache.org/r/73637/#comment312802>

Instead of getting entire metricstats and then setting metrics to null here 
you can send minInfo flas true at Line#436



webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java
Lines 471 (patched)
<https://reviews.apache.org/r/73637/#comment312806>

At multiple places AtlasMetricsStat taking only Metrics as input then 
AtlasMetricsStat(Metrics) constructor can be implemented instead of passing 
null for typeNames.



webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java
Lines 495 (patched)
<https://reviews.apache.org/r/73637/#comment312807>

getAllMetricsStats(minInfo) returns AtlasMetricsStat. Do we need to map 
again to cast each element.


- Radhika Kundam


On Oct. 26, 2021, 3:49 p.m., Disha Talreja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73637/
> ---
> 
> (Updated Oct. 26, 2021, 3:49 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Sarath Subramanian, and Sidharth 
> Mishra.
> 
> 
> Bugs: ATLAS-4370
> https://issues.apache.org/jira/browse/ATLAS-4370
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Rebased patch #73483 (https://reviews.apache.org/r/73483/) against the newest 
> master branch.
> 
> 
> Diffs
> -
> 
>   addons/models/-Area0/0010-base_model.json 769d8859f 
>   intg/src/main/java/org/apache/atlas/AtlasConfiguration.java b63fab7cf 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 2febff469 
>   
> intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMapToChart.java 
> PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsStat.java 
> PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/utils/AtlasEntityUtil.java 1e78e2550 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/metrics/AtlasMetricsStatDTO.java
>  PRE-CREATION 
>   repository/src/main/java/org/apache/atlas/services/MetricsService.java 
> ceb252822 
>   repository/src/test/java/org/apache/atlas/TestModules.java 8dda20825 
>   repository/src/test/java/org/apache/atlas/services/MetricsServiceTest.java 
> 040592184 
>   test-tools/src/main/resources/solr/core-template/solrconfig.xml 3341e7199 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> 135b94b36 
> 
> 
> Diff: https://reviews.apache.org/r/73637/diff/4/
> 
> 
> Testing
> ---
> 
> 1) Tested locally.
> 2) Patched a cluster.
> 
> PC build: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/880/
> 
> 
> Thanks,
> 
> Disha Talreja
> 
>

Re: Review Request 73637: ATLAS-4370: Persist Metrics for user to retrieve Metrics info at a past timestamp

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Nov. 9, 2021, 11:54 a.m., Disha Talreja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73637/
> ---
> 
> (Updated Nov. 9, 2021, 11:54 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Radhika Kundam, Sarath 
> Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4370
> https://issues.apache.org/jira/browse/ATLAS-4370
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Rebased patch #73483 (https://reviews.apache.org/r/73483/) against the newest 
> master branch.
> 
> 
> Diffs
> -
> 
>   addons/models/-Area0/0010-base_model.json 769d8859f 
>   intg/src/main/java/org/apache/atlas/AtlasConfiguration.java b63fab7cf 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 7d092616d 
>   
> intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsMapToChart.java 
> PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/model/metrics/AtlasMetricsStat.java 
> PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/utils/AtlasEntityUtil.java 1e78e2550 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/metrics/AtlasMetricsStatDTO.java
>  PRE-CREATION 
>   repository/src/main/java/org/apache/atlas/services/MetricsService.java 
> ceb252822 
>   repository/src/test/java/org/apache/atlas/TestModules.java 8dda20825 
>   repository/src/test/java/org/apache/atlas/services/MetricsServiceTest.java 
> 040592184 
>   test-tools/src/main/resources/solr/core-template/solrconfig.xml 3341e7199 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> 0580f7f33 
> 
> 
> Diff: https://reviews.apache.org/r/73637/diff/6/
> 
> 
> Testing
> ---
> 
> 1) Tested locally.
> 2) Patched a cluster.
> 
> PC build: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/880/
> 
> 
> Thanks,
> 
> Disha Talreja
> 
>

Re: Review Request 73704: ATLAS-4475: Import Hive V2 is throwing wrong log message when running with set of tables

[Radhika Kundam]

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




addons/hive-bridge/src/main/java/org/apache/atlas/hive/bridge/HiveMetaStoreBridgeV2.java
Line 437 (original), 438 (patched)
<https://reviews.apache.org/r/73704/#comment312825>

What is the need of totalTablesImported. In log message in finallly block 
we can use tableObjects size itself instead of totalTablesImported


- Radhika Kundam


On Nov. 10, 2021, 1:04 p.m., Sidharth Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73704/
> ---
> 
> (Updated Nov. 10, 2021, 1:04 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Disha Talreja, Radhika Kundam, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4475
> https://issues.apache.org/jira/browse/ATLAS-4475
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-4475: Fixed log messages for Import Hive V2 when running with set of 
> tables
> 
> 
> Diffs
> -
> 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/bridge/HiveMetaStoreBridgeV2.java
>  0627c0e09 
> 
> 
> Diff: https://reviews.apache.org/r/73704/diff/1/
> 
> 
> Testing
> ---
> 
> Manually tested. PreCommit run - 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/960/
> 
> 
> Thanks,
> 
> Sidharth Mishra
> 
>

Re: Review Request 73704: ATLAS-4475: Import Hive V2 is throwing wrong log message when running with set of tables

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Nov. 10, 2021, 1:04 p.m., Sidharth Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73704/
> ---
> 
> (Updated Nov. 10, 2021, 1:04 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Disha Talreja, Radhika Kundam, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4475
> https://issues.apache.org/jira/browse/ATLAS-4475
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-4475: Fixed log messages for Import Hive V2 when running with set of 
> tables
> 
> 
> Diffs
> -
> 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/bridge/HiveMetaStoreBridgeV2.java
>  0627c0e09 
> 
> 
> Diff: https://reviews.apache.org/r/73704/diff/1/
> 
> 
> Testing
> ---
> 
> Manually tested. PreCommit run - 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/960/
> 
> 
> Thanks,
> 
> Sidharth Mishra
> 
>

Re: Review Request 73826: ATLAS-4548: Set Empty attribute value for queryStr and queryId in case of null value when atlas.hook.hive.hive_process.populate.deprecated.attributes=true

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Feb. 2, 2022, 11:08 a.m., Sidharth Mishra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73826/
> ---
> 
> (Updated Feb. 2, 2022, 11:08 a.m.)
> 
> 
> Review request for atlas, Disha Talreja, Jayendra Parab, Pinal Shah, Radhika 
> Kundam, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4548
> https://issues.apache.org/jira/browse/ATLAS-4548
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-4548: Added Empty attribute value for queryStr and queryId in case of 
> null value
> 
> 
> Diffs
> -
> 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/events/BaseHiveEvent.java
>  3e966ae66 
> 
> 
> Diff: https://reviews.apache.org/r/73826/diff/1/
> 
> 
> Testing
> ---
> 
> Manually tested and PreCommit - 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1034/
> 
> 
> Thanks,
> 
> Sidharth Mishra
> 
>

Re: Review Request 73855: ATLAS-4556 Add Ozone "ofs" scheme support for external tables created through hive.

[Radhika Kundam]

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




common/src/main/java/org/apache/atlas/utils/AtlasPathExtractorUtil.java
Line 646 (original), 648 (patched)
<https://reviews.apache.org/r/73855/#comment313046>

Consider checking the array size to avoid ArrayIndexOutOfBoundsException 
while accessing strpath.split array


- Radhika Kundam


On Feb. 21, 2022, 4:39 a.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73855/
> ---
> 
> (Updated Feb. 21, 2022, 4:39 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Pinal Shah, Sarath 
> Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4556
> https://issues.apache.org/jira/browse/ATLAS-4556
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When we provide ozone key as a path for an external table in hive,
> corresponding Ozone entities of type "Ozone_Volume", "Ozone_Bucket", 
> "Ozone_Key" etc. get created.
> 
> Currently in Atlas, code supports the above in "o3fs" ozone scheme.
> Need to provide improved support in "ofs" scheme, same as that of "o3fs".
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/utils/AtlasPathExtractorUtil.java 
> cf8f262b9 
>   common/src/test/java/org/apache/atlas/utils/AtlasPathExtractorUtilTest.java 
> f35e9ae57 
> 
> 
> Diff: https://reviews.apache.org/r/73855/diff/2/
> 
> 
> Testing
> ---
> 
> PreCommit: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1046/consoleFull
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

Re: Review Request 73855: ATLAS-4556 Add Ozone "ofs" scheme support for external tables created through hive.

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Feb. 22, 2022, 9:50 p.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73855/
> ---
> 
> (Updated Feb. 22, 2022, 9:50 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Pinal Shah, Sarath 
> Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4556
> https://issues.apache.org/jira/browse/ATLAS-4556
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When we provide ozone key as a path for an external table in hive,
> corresponding Ozone entities of type "Ozone_Volume", "Ozone_Bucket", 
> "Ozone_Key" etc. get created.
> 
> Currently in Atlas, code supports the above in "o3fs" ozone scheme.
> Need to provide improved support in "ofs" scheme, same as that of "o3fs".
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/utils/AtlasPathExtractorUtil.java 
> cf8f262b9 
>   common/src/test/java/org/apache/atlas/utils/AtlasPathExtractorUtilTest.java 
> f35e9ae57 
> 
> 
> Diff: https://reviews.apache.org/r/73855/diff/3/
> 
> 
> Testing
> ---
> 
> PreCommit: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1046/consoleFull
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

Re: Review Request 73731: ATLAS-4495 Glossary section takes longer time to load when Glossaries have large number of Categories and Terms associated with them

[Radhika Kundam]

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




repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java
Line 128 (original), 133 (patched)
<https://reviews.apache.org/r/73731/#comment313057>

Can we use atlasGlossaryDTO.from(glossaryEntity) and update "from" method 
to set the displayText instead of implementing new methods to avaoid duplicate 
code.



repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java
Lines 1335 (patched)
<https://reviews.apache.org/r/73731/#comment313058>


categoryObjectId.getRelationshipAttributes().getAttribute("parentCategoryGuid") 
can be used instead of getting all attributes and null check.



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
Lines 1554 (patched)
<https://reviews.apache.org/r/73731/#comment313059>

ret.getRelationshipAttributes().setAttribute("parentCategoryGuid", 
parentCategoryGuid) can be used which will handle to create attributes map if 
none present.


- Radhika Kundam


On Feb. 9, 2022, 8:54 p.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73731/
> ---
> 
> (Updated Feb. 9, 2022, 8:54 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Radhika Kundam, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4495
> https://issues.apache.org/jira/browse/ATLAS-4495
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> It is observed that, due to existing framework Glossary GET api takes longer 
> time.
> 
> This patch avoids the unnecessary db calls and improve the performance when 
> there is large number of data associated with the Glossary (say 10K terms or 
> categories)
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 
> f81b53854 
>   repository/src/main/java/org/apache/atlas/repository/ogm/DataAccess.java 
> f902b2afb 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/glossary/AtlasGlossaryDTO.java
>  c525bdb99 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
>  794847555 
> 
> 
> Diff: https://reviews.apache.org/r/73731/diff/2/
> 
> 
> Testing
> ---
> 
> Manual testing is done.
> 
> PreCommit: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1009/consoleFull
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

Re: Review Request 73731: ATLAS-4495 Glossary section takes longer time to load when Glossaries have large number of Categories and Terms associated with them

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On March 3, 2022, 4:44 a.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73731/
> ---
> 
> (Updated March 3, 2022, 4:44 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Radhika Kundam, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4495
> https://issues.apache.org/jira/browse/ATLAS-4495
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> It is observed that, due to existing framework Glossary GET api takes longer 
> time.
> 
> This patch avoids the unnecessary db calls and improve the performance when 
> there is large number of data associated with the Glossary (say 10K terms or 
> categories)
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 
> f81b53854 
>   repository/src/main/java/org/apache/atlas/repository/ogm/DataAccess.java 
> f902b2afb 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/glossary/AbstractGlossaryDTO.java
>  bee88c61f 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
>  9671df994 
> 
> 
> Diff: https://reviews.apache.org/r/73731/diff/3/
> 
> 
> Testing
> ---
> 
> Manual testing is done.
> 
> PreCommit: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1009/consoleFull
> 
> PreCommit: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1049/consoleFull
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

Re: Review Request 73883: ATLAS-4560 : DSL Search : Error when keyword 'limit' is present in the search value

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On March 4, 2022, 2:35 a.m., Snehal Ambavkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73883/
> ---
> 
> (Updated March 4, 2022, 2:35 a.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Mandar Ambawane, and Pinal Shah.
> 
> 
> Bugs: ATLAS-4560
> https://issues.apache.org/jira/browse/ATLAS-4560
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Root cause :
> 
> There is a check in the code, if the query contains 'limit' keyword and does 
> not contain 'offset' then add 'offset 0' to the query.
> eg : where name="test_column" limit 6, the updated query would be, where 
> name="test_column" limit 6 offset 0
> 
> In the query, where name="test_limit"
> Since the query contains 'limit' word, offset 0 is added to the query without 
> the 'limit' keyword.
> As per the grammar, there has to be 'limit' before 'offset', hence the error.
> 
> 
> Solution:
> It is not required to have offset when limit is specified.so the check is not 
> required.
> Removed the above mentioned check, so no offset is added when there is 
> 'limit' word in the query.
> Search works as expected with just limit specified
> If the query does not contain 'limit', default limit value is used.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/query/executors/TraversalBasedExecutor.java
>  ecd82e3fd 
>   repository/src/test/java/org/apache/atlas/BasicTestSetup.java a1d7b62a5 
>   
> repository/src/test/java/org/apache/atlas/discovery/AtlasDiscoveryServiceTest.java
>  8c257d866 
>   repository/src/test/java/org/apache/atlas/query/BaseDSLComposer.java 
> 419050ec8 
>   repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 
> 74cc4e0a2 
>   repository/src/test/java/org/apache/atlas/query/TraversalComposerTest.java 
> 60645771d 
> 
> 
> Diff: https://reviews.apache.org/r/73883/diff/3/
> 
> 
> Testing
> ---
> 
> 1. created hive table with column test_limit and did basic search and 
> advanced search
> 2. created hive table with 'limit' in name and did basic search and advanced 
> search
> 3. used quick search entity types to create entities with limit in their name 
> and searched for them
> 4. Tested for 'limit' string in classifications and glossaries.
> 5. Small sanity in basic search and advanced search.
> 
> 
> Precommit : 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1052/console
> 
> 
> Thanks,
> 
> Snehal Ambavkar
> 
>

Re: [DRAFT] [REPORT] Apache Atlas - March 2022

[Radhika Kundam]

Thanks Madhan for the report, looks good.
+1

Regards,
Radhika

On Tue, Mar 8, 2022 at 2:38 PM Madhan Neethiraj  wrote:

> Atlas community,
>
>
>
> Please review the following draft report for this quarter.
>
>
>
> Thanks,
>
> Madhan
>
>
>
>
>
>
>
> ## Description:
>
> The mission of Apache Atlas is the creation and maintenance of software
>
> related to a scalable and extensible set of core foundational governance
>
> services - enabling enterprises to effectively and efficiently meet their
>
> compliance requirements
>
>
>
> ## Issues:
>
> There are no issues requiring board attention.
>
>
>
> ## Membership Data:
>
> Apache Atlas was founded 2017-06-20 (5 years ago). There are currently 45
>
> 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.
>
> - Radhika Kundam was added as committer on 2022-02-04
>
>
>
> ## Project Activity:
>
> - added build profile for Cassandra and Elastic Search stores
>
> - UI fixes to handle glossary with large number of terms
>
> - multiple fixes in search feature and UI
>
> - updated docker setup to use network name
>
> - updated monitoring to support Elastic Search index backend
>
> - updated Hive hook to support Ozone file scheme for external tables
>
> - fixed failure in Atlas startup in HA mode with index recovery enabled
>
> - dependent component version updates: JanusGraph 0.6.1, TinkerPop 3.5.2,
>
>   Spring framework 5.3.15, log4j 2.17.1, testng 7.0, underscore.js 1.12.1
>
>
>
> ## Community Health:
>
> - dev@atlas.apache.org had a 22% decrease in traffic in the past quarter
> (680
>
>   emails compared to 868)
>
> - u...@atlas.apache.org had a 37% decrease in traffic in the past quarter
> (12
>
>   emails compared to 19)
>
> - 61 issues opened in JIRA, past quarter (-27% change)
>
> - 29 issues closed in JIRA, past quarter (-51% change)
>
> - 56 commits in the past quarter (-53% change)
>
> - 13 code contributors in the past quarter (-27% change)
>
> - 9 PRs opened on GitHub, past quarter (12% increase)
>
> - 2 PRs closed on GitHub, past quarter (-50% change)
>
>
>
> ## Most Recent releases:
>
> 2.2.0 was released on 2021-08-17
>
> 2.1.0 was released on 2020-07-15
>
> 0.8.4 was released on 2019-06-21
>
>
>
>
>
>

Re: [DRAFT] [REPORT] Apache Atlas - July 2022

[Radhika Kundam]

+1, Thanks Madhan for preparing the draft and putting it for review.

On Sun, Jul 10, 2022 at 10:46 PM Madhan Neethiraj  wrote:

> Atlas community,
>
> Please review the following draft report for this quarter.
>
> Thanks,
> Madhan
>
> ## Description:
> The mission of Apache Atlas is the creation and maintenance of software
> related
> to a scalable and extensible set of core foundational governance services
> -
> enabling enterprises to effectively and efficiently meet their compliance
> requirements
>
> ## Issues:
> There are not issues requiring board attention.
>
> ## Membership Data:
> Apache Atlas was founded 2017-06-20 (5 years ago)
> There are currently 45 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.
> - No new committers. Last addition was Radhika Kundam on 2022-02-04.
>
> ## Project Activity:
> - resolved failures with Atlas HA with index-recovery enabled
> - notification message processing improvements to enable server and hooks
> to
>   be of different versions
> - Kafka importer utility improvements
> - Impala hook fix to handle large query string
> - Glossary module performance improvements to handle glossaries with large
>   number of categories and terms
> - import zip functionality improvements
> - several UI enhancements/fixes
> - dependent component version updates: Spring 5.3.20, jQuery-UI 1.13.0,
> netty
>   4.1.77, Spring security 5.7.1, gson 2.9.0
>
> ## Community Health:
> - dev@atlas.apache.org had a 22% decrease in traffic in the past quarter
> (680
>   emails compared to 868)
> - u...@atlas.apache.org had a 37% decrease in traffic in the past quarter
> (12
>   emails compared to 19)
> - 48 issues opened in JIRA, past quarter (-12% change)
> - 24 issues closed in JIRA, past quarter (-20% change)
> - 48 commits in the past quarter (-27% change)
> - 11 code contributors in the past quarter (-15% change)
> - 24 PRs opened on GitHub, past quarter (20% increase)
> - 11 PRs closed on GitHub, past quarter (450% increase)
>
> ## Most Recent releases:
> 2.2.0 was released on 2021-08-17
> 2.1.0 was released on 2020-07-15
> 0.8.4 was released on 2019-06-21
>
>
>
>

Re: Review Request 74130: ATLAS-4679 : Indexing of deleted relationship edges prolongs entity update time

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Sept. 22, 2022, 11:17 a.m., Sheetal Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74130/
> ---
> 
> (Updated Sept. 22, 2022, 11:17 a.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Mandar Ambawane, and Pinal Shah.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Problem statement : While working with a kafka dump which contained messages 
> from spark streaming applications, 
> it was observed that when an application is getting updated, it takes longest 
> time while
> re-indexing the edges and that "deleted" relationship edges were also being
> re-indexed every-time an application was getting updated for an incoming 
> process message.
> This takes a few minutes to process for 35k processes, average time was 135 
> seconds; this time would increase as new processes enter the system.
> 
> Changes have been made to consider only active edges to process the 
> relationship edges which always ends up
> considering only new additional edges for processing/indexing leading to a 
> significant difference in processing time when number of deleted edges are 
> too high for an updating entity
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
>  68d331dfd 
> 
> 
> Diff: https://reviews.apache.org/r/74130/diff/1/
> 
> 
> Testing
> ---
> 
> We tested the same kafka dump for the changes and the time taken to process 
> messages was significantly less. Running the dump with the fix showed a 
> drastic improvement in that it considered only non-deleted edges for 
> processing/re-indexing leading to a consistent processing time of around 1 to 
> 2 seconds.
> 
> 
> Thanks,
> 
> Sheetal Shah
> 
>

Re: Review Request 74201: ATLAS-4445: fix import-hive.sh failure due to NoClassDefFoundError: javax/ws/rs/core/Link$Builder

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Nov. 15, 2022, 12:08 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74201/
> ---
> 
> (Updated Nov. 15, 2022, 12:08 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, keval bhatt, 
> Nikhil Bonte, Nixon Rodrigues, Pinal Shah, Radhika Kundam, Ramesh Mani, 
> Sarath Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4445
> https://issues.apache.org/jira/browse/ATLAS-4445
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> - updated hive version from 3.1.0 to 3.1.2
> - removed packaging jsr311-api in Hive hook
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/pom.xml 856e5d95d 
>   addons/hive-bridge/src/bin/import-hive.sh ebe6976f0 
>   pom.xml ca221fe29 
> 
> 
> Diff: https://reviews.apache.org/r/74201/diff/1/
> 
> 
> Testing
> ---
> 
> - verified import-hive.sh in docker setup
> - all existing tests pass successfully
> - pre-commit tests run: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1288/
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74202: ATLAS-4713: docker setup updates to be in sync with component versions in project pom.xml

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Nov. 15, 2022, 5:41 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74202/
> ---
> 
> (Updated Nov. 15, 2022, 5:41 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Mandar Ambawane, 
> Nikhil Bonte, Nixon Rodrigues, Pinal Shah, Radhika Kundam, Sarath 
> Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4713
> https://issues.apache.org/jira/browse/ATLAS-4713
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> - updated version of Kafka, Hive-hadoop
> - fixed incorrect Atlas URL in hook configuration setup
> 
> 
> Diffs
> -
> 
>   dev-support/atlas-docker/.env 19175c2ed 
>   dev-support/atlas-docker/scripts/atlas-hbase-application.properties 
> 8c5b9e088 
>   dev-support/atlas-docker/scripts/atlas-hive-application.properties 
> 8c5b9e088 
> 
> 
> Diff: https://reviews.apache.org/r/74202/diff/1/
> 
> 
> Testing
> ---
> 
> - verified that Atlas docker setup builds successfully
> - performed sanity testing of Atlas, Hive hook, HBase hook
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74203: ATLAS-4241: fix import-hbase errors

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Nov. 15, 2022, 9:53 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74203/
> ---
> 
> (Updated Nov. 15, 2022, 9:53 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Nikhil Bonte, 
> Nixon Rodrigues, Pinal Shah, Radhika Kundam, Ramesh Mani, Sarath Subramanian, 
> and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4241
> https://issues.apache.org/jira/browse/ATLAS-4241
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> - fixed classpath for import-hbase to exclude couple of libraries present in 
> HBase lib directory
> - added following libraries in HBase plugin impl: commons-collections, 
> commons-logging, jackson-jaxrs-json-provider, jackson-jaxrs-base, 
> jersey-bundle
> 
> 
> Diffs
> -
> 
>   addons/hbase-bridge/pom.xml f51a7d6f1 
>   addons/hbase-bridge/src/bin/import-hbase.sh a343036fa 
> 
> 
> Diff: https://reviews.apache.org/r/74203/diff/1/
> 
> 
> Testing
> ---
> 
> verified the following using Docker setup
>  - HBase hook successfully reports changes to Atlas server
>  - import-hbase utility successfully imports namespaces and tables to Atlas 
> server
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74204: ATLAS-3820: fix import-kafka.sh failures

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Nov. 15, 2022, 10:06 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74204/
> ---
> 
> (Updated Nov. 15, 2022, 10:06 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Nikhil Bonte, 
> Nixon Rodrigues, Pinal Shah, Radhika Kundam, Ramesh Mani, Sarath Subramanian, 
> Sharmadha Sainath, Sidharth Mishra, and Umesh Padashetty.
> 
> 
> Bugs: ATLAS-3820
> https://issues.apache.org/jira/browse/ATLAS-3820
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> - added missing libraries to Kafka bridge package
> - updated docker setup to include Kafka bridge
> 
> 
> Diffs
> -
> 
>   addons/kafka-bridge/pom.xml 9ce22a757 
>   addons/kafka-bridge/src/bin/import-kafka.sh ada3b4ae2 
>   
> addons/kafka-bridge/src/main/java/org/apache/atlas/kafka/bridge/KafkaBridge.java
>  8be2fca3a 
>   dev-support/atlas-docker/.dockerignore d4a3db26b 
>   dev-support/atlas-docker/Dockerfile.atlas-kafka e06d62845 
>   dev-support/atlas-docker/scripts/atlas-build.sh e53ebbba9 
>   dev-support/atlas-docker/scripts/atlas-kafka-application.properties 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/74204/diff/1/
> 
> 
> Testing
> ---
> 
> - verified that import-kafka.sh sucessfully added Kafka topics to Atlas
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74240: ATLAS-4700: updated documentation for 2.3.0 release

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Dec. 7, 2022, 12:08 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74240/
> ---
> 
> (Updated Dec. 7, 2022, 12:08 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Mandar Ambawane, 
> Nikhil Bonte, Nixon Rodrigues, Pinal Shah, Prasad Pawar, Radhika Kundam, 
> Sarath Subramanian, Sharmadha Sainath, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4700
> https://issues.apache.org/jira/browse/ATLAS-4700
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> updated documentation for 2.3.0 release
> 
> 
> Diffs
> -
> 
>   docs/docz-lib/config/menu.js 37acf46d4 
>   docs/docz-lib/config/versions.js 3ef55f681 
>   docs/src/documents/Downloads/Downloads.md e486a1d0b 
>   docs/src/documents/Overview.md 8614106ab 
>   docs/src/documents/Whats-New/WhatsNew-2.3.md PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/74240/diff/1/
> 
> 
> Testing
> ---
> 
> verified the updated site with 'mvn site:run" in docs directory
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74664: ATLAS-4800: Atlas - Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Oct. 11, 2023, 4:40 p.m., Disha Talreja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74664/
> ---
> 
> (Updated Oct. 11, 2023, 4:40 p.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Mehul Parikh, and Radhika Kundam.
> 
> 
> Bugs: ATLAS-4800
> https://issues.apache.org/jira/browse/ATLAS-4800
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Upgrade Apache Ivy to 2.5.2 due to CVE-2022-46751
> 
> 
> Diffs
> -
> 
>   pom.xml f76d0ea04 
> 
> 
> Diff: https://reviews.apache.org/r/74664/diff/1/
> 
> 
> Testing
> ---
> 
> Verified locally
> PC Build: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1484/ 
> [One test failed which is not related to this change - 
> (EntityV2JerseyResourceIT.testSetLabelsByTypeName:986)]
> 
> 
> Thanks,
> 
> Disha Talreja
> 
>

Re: Review Request 74676: ATLAS-4801: Atlas - Upgrade Okio to 3.4.0 due to CVE-2023-3635

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Oct. 27, 2023, 10:50 a.m., Disha Talreja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74676/
> ---
> 
> (Updated Oct. 27, 2023, 10:50 a.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Radhika Kundam, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4801
> https://issues.apache.org/jira/browse/ATLAS-4801
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> GzipSource does not handle an exception that might be raised when parsing a 
> malformed gzip buffer. This may lead to denial of service of the Okio client 
> when handling a crafted GZIP archive, by using the GzipSource class.
> 
> CVSSv3 Score:- 7.5(High)
> 
> https://nvd.nist.gov/vuln/detail/CVE-2023-3635
> 
> 
> Diffs
> -
> 
>   pom.xml f76d0ea04 
> 
> 
> Diff: https://reviews.apache.org/r/74676/diff/1/
> 
> 
> Testing
> ---
> 
> Verified Manually
> PC Build: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1485/ 
> [One test failed which is not related to this change - 
> (EntityV2JerseyResourceIT.testSetLabelsByTypeName:986)]
> 
> 
> Thanks,
> 
> Disha Talreja
> 
>

Re: [DRAFT] [REPORT] Apache Atlas - December 2023

[Radhika Kundam]

+1, Report looks good.
Thank you Madhan for putting this together.

- Radhika

On Wed, Dec 13, 2023 at 9:25 AM Madhan Neethiraj  wrote:

> Atlas community,
>
>
>
> Please review the following draft report for this quarter.
>
>
>
> Thanks,
>
> Madhan
>
>
>
> ## Description:
>
> The mission of Apache Atlas is the creation and maintenance of software
> related
>
> to a scalable and extensible set of core foundational governance services
> -
>
> enabling enterprises to effectively and efficiently meet their compliance
>
> requirements
>
>
>
> ## Project Status:
>
> Current project status: Ongoing, with moderate activity
>
> Issues for the board: There are no issues requiring board attention.
>
>
>
> ## Membership Data:
>
> Apache Atlas was founded 2017-06-20 (6 years ago)
>
> There are currently 48 committers and 32 PMC members in this project.
>
> The Committer-to-PMC ratio is 3:2.
>
>
>
> Community changes, past quarter:
>
> - No new PMC members. Last addition was Ashutosh Mestry on 2019-04-16.
>
> - No new committers. Last addition was Umesh Padashetty on 2023-06-14.
>
>
>
> ## Project Activity:
>
> - enhancements to support aging of entity audits
>
> - added bridge for Couchbase
>
> - performance improvement in notification processing with optimization in
>
>   fetching relationships
>
> - removed references to Python2 with Python3
>
> - improvements in dynamic index recovery
>
> - fixes in Impala hook
>
> - published Atlas client Python library 0.0.15
>
> - updated versions of Okio, Apache Ivy
>
>
>
> ## Community Health:
>
> - dev@atlas.apache.org had a 41% increase in traffic in the past quarter
> (247
>
>   emails compared to 174)
>
> - 17 issues opened in JIRA, past quarter (-48% change)
>
> - 14 issues closed in JIRA, past quarter (-30% change)
>
> - 33 commits in the past quarter (3% increase)
>
> - 11 code contributors in the past quarter (22% increase)
>
> - 2 PRs opened on GitHub, past quarter (-71% change)
>
> - 4 PRs closed on GitHub, past quarter (no change)
>
>
>
> ## Recent releases:
>
> Apache Atlas 2.3.0 was released on 2022-12-06.
>
> Apache Atlas 2.2.0 was released on 2021-08-17.
>
> Apache Atlas 2.1.0 was released on 2020-07-15.
>
>
>
>
>
>

Re: Review Request 74707: ATLAS-4806: Upgrade netty to 4.1.100.Final due to CVE-2023-44487

[Radhika Kundam]

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


Ship it!




Ship It!

- Radhika Kundam


On Feb. 8, 2024, 9:32 a.m., Disha Talreja wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74707/
> ---
> 
> (Updated Feb. 8, 2024, 9:32 a.m.)
> 
> 
> Review request for atlas, Jayendra Parab and Radhika Kundam.
> 
> 
> Bugs: ATLAS-4806
> https://issues.apache.org/jira/browse/ATLAS-4806
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Upgraded netty version to 4.1.100.Final
> 
> 
> Diffs
> -
> 
>   pom.xml 0e21c7f31 
> 
> 
> Diff: https://reviews.apache.org/r/74707/diff/2/
> 
> 
> Testing
> ---
> 
> Verified Manually
> PC Build: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1547/
> 
> 
> Thanks,
> 
> Disha Talreja
> 
>

Re: [DRAFT] [REPORT] Apache Atlas - June 2024

[Radhika Kundam]

+1, Thanks Madhan for the draft report.

- Radhika

On Fri, Jun 14, 2024 at 5:52 AM Madhan Neethiraj  wrote:

> Atlas community,
>
> Please review the following draft report for this quarter.
>
> Thanks,
> Madhan
>
>
> ## Description:
> The mission of Apache Atlas is the creation and maintenance of software
> related
> to a scalable and extensible set of core foundational governance services -
> enabling enterprises to effectively and efficiently meet their compliance
> requirements
>
> ## Project Status:
> Current project status: Ongoing, with low activity
> Issues for the board: there are no issues requiring board attention
>
> ## Membership Data:
> Apache Atlas was founded 2017-06-20 (7 years ago)
> There are currently 48 committers and 32 PMC members in this project.
> The Committer-to-PMC ratio is 3:2.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Ashutosh Mestry on 2019-04-16.
> - No new committers. Last addition was Umesh Padashetty on 2023-06-14.
>
> ## Project Activity:
> - improvements in Export/Import functionality
> - updates to support ignore patterns in all Atlas hooks
> - added support for Chinese characters in Atlas entity attributes
> - Docker setup update to address HBase failures
> - updated versions of dependent libraries JanusGraph and Tinkerpop
>
> ## Community Health:
> - dev@atlas.apache.org had a 166% increase in traffic in the past quarter
> (312
>   emails compared to 117)
> - 23 commits in the past quarter (64% increase)
> - 7 code contributors in the past quarter (40% increase)
> - 4 PRs opened on GitHub, past quarter (100% increase)
> - 2 PRs closed on GitHub, past quarter (100% increase)
>
> ## Recent releases:
> - Apache Atlas 2.3.0 was released on 2022-12-06
> - Apache Atlas 2.2.0 was released on 2021-08-17
> - Apache Atlas 2.1.0 was released on 2020-07-15
>
>
>
>
>

[jira] [Created] (ATLAS-4010) Sort properties lexicographically in pom.xml for readability

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4010:
-

 Summary: Sort properties lexicographically in pom.xml for 
readability
 Key: ATLAS-4010
 URL: https://issues.apache.org/jira/browse/ATLAS-4010
 Project: Atlas
  Issue Type: Task
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Properties are in random order under  section in pom.xml

For better readability, need to sort properties in lexicographic order.



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

[jira] [Updated] (ATLAS-4010) Sort properties lexicographically in pom.xml for readability

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4010:
--
Affects Version/s: 2.1.0

> Sort properties lexicographically in pom.xml for readability
> 
>
> Key: ATLAS-4010
> URL: https://issues.apache.org/jira/browse/ATLAS-4010
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Trivial
>
> Properties are in random order under  section in pom.xml
> For better readability, need to sort properties in lexicographic order.



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

[jira] [Updated] (ATLAS-4010) Sort properties lexicographically in pom.xml for readability

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4010:
--
Component/s:  atlas-core

> Sort properties lexicographically in pom.xml for readability
> 
>
> Key: ATLAS-4010
> URL: https://issues.apache.org/jira/browse/ATLAS-4010
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>        Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Trivial
>
> Properties are in random order under  section in pom.xml
> For better readability, need to sort properties in lexicographic order.



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

[jira] [Updated] (ATLAS-4010) Sort properties lexicographically in pom.xml for readability

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4010:
--
Description: 
Properties are in random order under  section in all pom.xml files.

For better readability, need to sort properties in lexicographic order.

Below are the pom.xml files with  tag

atlas/pom.xml

atlas/distro/pom.xml

atlas/docs/pom.xml

atlas/webapp/pom.xml

Need to sort all the properties inside the each  tag in 
alphabetically ascending order.

  was:
Properties are in random order under  section in pom.xml

For better readability, need to sort properties in lexicographic order.


> Sort properties lexicographically in pom.xml for readability
> 
>
> Key: ATLAS-4010
> URL: https://issues.apache.org/jira/browse/ATLAS-4010
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Trivial
>
> Properties are in random order under  section in all pom.xml 
> files.
> For better readability, need to sort properties in lexicographic order.
> Below are the pom.xml files with  tag
> atlas/pom.xml
> atlas/distro/pom.xml
> atlas/docs/pom.xml
> atlas/webapp/pom.xml
> Need to sort all the properties inside the each  tag in 
> alphabetically ascending order.



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

[jira] [Commented] (ATLAS-4010) Sort properties lexicographically in pom.xml for readability

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4010:
---

PC build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/178/]

> Sort properties lexicographically in pom.xml for readability
> 
>
> Key: ATLAS-4010
> URL: https://issues.apache.org/jira/browse/ATLAS-4010
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Trivial
>
> Properties are in random order under  section in all pom.xml 
> files.
> For better readability, need to sort properties in lexicographic order.
> Below are the pom.xml files with  tag
> atlas/pom.xml
> atlas/distro/pom.xml
> atlas/docs/pom.xml
> atlas/webapp/pom.xml
> Need to sort all the properties inside the each  tag in 
> alphabetically ascending order.



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

[jira] [Updated] (ATLAS-4010) Sort properties lexicographically in pom.xml for readability

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4010:
--
Fix Version/s: 2.2.0
   3.0.0

> Sort properties lexicographically in pom.xml for readability
> 
>
> Key: ATLAS-4010
> URL: https://issues.apache.org/jira/browse/ATLAS-4010
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Trivial
> Fix For: 3.0.0, 2.2.0
>
>
> Properties are in random order under  section in all pom.xml 
> files.
> For better readability, need to sort properties in lexicographic order.
> Below are the pom.xml files with  tag
> atlas/pom.xml
> atlas/distro/pom.xml
> atlas/docs/pom.xml
> atlas/webapp/pom.xml
> Need to sort all the properties inside the each  tag in 
> alphabetically ascending order.



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

[jira] [Comment Edited] (ATLAS-4010) Sort properties lexicographically in pom.xml for readability

[Radhika Kundam (Jira)]

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

Radhika Kundam edited comment on ATLAS-4010 at 11/12/20, 10:18 PM:
---

Committed the patch in branch-2.0 & master


was (Author: radhikak):
Committed the patch in 2.2.0 & 3.0.0

> Sort properties lexicographically in pom.xml for readability
> 
>
> Key: ATLAS-4010
> URL: https://issues.apache.org/jira/browse/ATLAS-4010
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Trivial
> Fix For: 3.0.0, 2.2.0
>
>
> Properties are in random order under  section in all pom.xml 
> files.
> For better readability, need to sort properties in lexicographic order.
> Below are the pom.xml files with  tag
> atlas/pom.xml
> atlas/distro/pom.xml
> atlas/docs/pom.xml
> atlas/webapp/pom.xml
> Need to sort all the properties inside the each  tag in 
> alphabetically ascending order.



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

[jira] [Assigned] (ATLAS-4013) JanusGraph 0.5.1 is not compatible with elasticsearch 5.*

[Radhika Kundam (Jira)]

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

Radhika Kundam reassigned ATLAS-4013:
-

Assignee: Radhika Kundam

> JanusGraph 0.5.1 is not compatible with elasticsearch 5.*
> -
>
> Key: ATLAS-4013
> URL: https://issues.apache.org/jira/browse/ATLAS-4013
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: wforget
>    Assignee: Radhika Kundam
>Priority: Major
> Attachments: 1.png, 2.png
>
>
> Atlas failed to initialize RestElasticSearchClient, due to 
> org.elasticsearch.client.Request is not compatible with the current 
> elasticsearch version. 



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

[jira] [Assigned] (ATLAS-3899) Not able to add or update businessAttributes using "/guid/{guid}/businessmetadata/{bmName}" API in EntityRest

[Radhika Kundam (Jira)]

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

Radhika Kundam reassigned ATLAS-3899:
-

Assignee: Radhika Kundam  (was: Jyoti Singh)

> Not able to add or update businessAttributes using 
> "/guid/{guid}/businessmetadata/{bmName}" API in EntityRest
> -
>
> Key: ATLAS-3899
> URL: https://issues.apache.org/jira/browse/ATLAS-3899
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Jyoti Singh
>Assignee: Radhika Kundam
>Priority: Major
>  Labels: api
> Attachments: businessmetadata.png
>
>
> There is a bug in the following API.
> POST *api/atlas/v2/entity/guid/\{guid}/businessmetadata/\{bmName}*
> **This API is sending a multi-level map to the repository layer. Due to this, 
> it is not able to add or update given businessAttributes to the entity.



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

[jira] [Assigned] (ATLAS-3359) Relationships : Unique attribute in a relationship is not honored

[Radhika Kundam (Jira)]

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

Radhika Kundam reassigned ATLAS-3359:
-

Assignee: Radhika Kundam  (was: Mayank Jain)

> Relationships : Unique attribute in a relationship is not honored
> -
>
> Key: ATLAS-3359
> URL: https://issues.apache.org/jira/browse/ATLAS-3359
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Nixon Rodrigues
>    Assignee: Radhika Kundam
>Priority: Major
> Fix For: 2.2.0
>
>
> 1.Created a relationship typedef between type1 & type2 with attribute "attr1" 
> which is unique (set "IsUnique" to true).
> 2. Created entity1 (type1) and entity2(type2) and created a relationship 
> instance between them with "attr1" value , say "value1".
> 3. Created entity3 (type1) and entity4(type2) and created a relationship 
> instance between them with "attr1" value with the same value "value1".
> Expected the relationship creation between entity3 and entity4 would fail 
> because a relationship with "attr1 " with "value1" is already created between 
> entity1 and entity2. But request passed and the relationship is created 
> successfully.



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

[jira] [Created] (ATLAS-4026) Update Atlas with latest version of JanusGraph - 0.5.2

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4026:
-

 Summary: Update Atlas with latest version of JanusGraph - 0.5.2
 Key: ATLAS-4026
 URL: https://issues.apache.org/jira/browse/ATLAS-4026
 Project: Atlas
  Issue Type: Task
  Components:  atlas-core
Affects Versions: 2.1.0
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Atlas is using JanusGraph 0.5.1, update JanusGraph to latest version 0.5.2



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

[jira] [Commented] (ATLAS-4026) Update Atlas with latest version of JanusGraph - 0.5.2

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4026:
---

PC Build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/189]

> Update Atlas with latest version of JanusGraph - 0.5.2
> --
>
> Key: ATLAS-4026
> URL: https://issues.apache.org/jira/browse/ATLAS-4026
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Atlas is using JanusGraph 0.5.1, update JanusGraph to latest version 0.5.2



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

[jira] [Created] (ATLAS-4027) Update Atlas with latest version of slf4j - 1.7.30

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4027:
-

 Summary: Update Atlas with latest version of slf4j - 1.7.30
 Key: ATLAS-4027
 URL: https://issues.apache.org/jira/browse/ATLAS-4027
 Project: Atlas
  Issue Type: Task
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Update Atlas with latest version of slf4j 1.7.30

In Atlas, latest slf4j version will be used for below jars.

slf4j-api

slf4j-log4j12 

jul-to-slf4j



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

[jira] [Updated] (ATLAS-4027) Update Atlas with latest version of slf4j - 1.7.30

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4027:
--
Affects Version/s: 2.1.0

> Update Atlas with latest version of slf4j - 1.7.30
> --
>
> Key: ATLAS-4027
> URL: https://issues.apache.org/jira/browse/ATLAS-4027
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 2.1.0
>        Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
>
> Update Atlas with latest version of slf4j 1.7.30
> In Atlas, latest slf4j version will be used for below jars.
> slf4j-api
> slf4j-log4j12 
> jul-to-slf4j



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

[jira] [Updated] (ATLAS-4027) Update Atlas with latest version of slf4j - 1.7.30

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4027:
--
Component/s:  atlas-core

> Update Atlas with latest version of slf4j - 1.7.30
> --
>
> Key: ATLAS-4027
> URL: https://issues.apache.org/jira/browse/ATLAS-4027
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
>
> Update Atlas with latest version of slf4j 1.7.30
> In Atlas, latest slf4j version will be used for below jars.
> slf4j-api
> slf4j-log4j12 
> jul-to-slf4j



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

[jira] [Comment Edited] (ATLAS-4026) Update Atlas with latest version of JanusGraph - 0.5.2

[Radhika Kundam (Jira)]

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

Radhika Kundam edited comment on ATLAS-4026 at 11/16/20, 6:15 PM:
--

PC Build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/190|https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/189]


was (Author: radhikak):
PC Build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/189]

> Update Atlas with latest version of JanusGraph - 0.5.2
> --
>
> Key: ATLAS-4026
> URL: https://issues.apache.org/jira/browse/ATLAS-4026
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Atlas is using JanusGraph 0.5.1, update JanusGraph to latest version 0.5.2



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

[jira] [Updated] (ATLAS-4028) Update Atlas with latest version of httpclient and httpcore

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4028:
--
Affects Version/s: 2.1.0

> Update Atlas with latest version of httpclient and httpcore
> ---
>
> Key: ATLAS-4028
> URL: https://issues.apache.org/jira/browse/ATLAS-4028
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 2.1.0
>        Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
>
> Update Atlas with httpclient 4.5.13 & httpcore 4.4.13



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

[jira] [Created] (ATLAS-4028) Update Atlas with latest version of httpclient and httpcore

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4028:
-

 Summary: Update Atlas with latest version of httpclient and 
httpcore
 Key: ATLAS-4028
 URL: https://issues.apache.org/jira/browse/ATLAS-4028
 Project: Atlas
  Issue Type: Task
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Update Atlas with httpclient 4.5.13 & httpcore 4.4.13



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

[jira] [Updated] (ATLAS-4028) Update Atlas with latest version of httpclient and httpcore

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4028:
--
Component/s:  atlas-core

> Update Atlas with latest version of httpclient and httpcore
> ---
>
> Key: ATLAS-4028
> URL: https://issues.apache.org/jira/browse/ATLAS-4028
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
>
> Update Atlas with httpclient 4.5.13 & httpcore 4.4.13



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

[jira] [Created] (ATLAS-4029) Apache documentation for Atlas Lineage

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4029:
-

 Summary: Apache documentation for Atlas Lineage
 Key: ATLAS-4029
 URL: https://issues.apache.org/jira/browse/ATLAS-4029
 Project: Atlas
  Issue Type: Task
  Components:  atlas-core
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Apache documentation should be updated with Lineage formation for different 
scenarios and with more examples.



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

[jira] [Commented] (ATLAS-4027) Update Atlas with latest version of slf4j - 1.7.30

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4027:
---

PC Build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/191/]

> Update Atlas with latest version of slf4j - 1.7.30
> --
>
> Key: ATLAS-4027
> URL: https://issues.apache.org/jira/browse/ATLAS-4027
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Update Atlas with latest version of slf4j 1.7.30
> In Atlas, latest slf4j version will be used for below jars.
> slf4j-api
> slf4j-log4j12 
> jul-to-slf4j



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

[jira] [Commented] (ATLAS-4028) Update Atlas with latest version of httpclient and httpcore

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4028:
---

PC Build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/199/]

 

> Update Atlas with latest version of httpclient and httpcore
> ---
>
> Key: ATLAS-4028
> URL: https://issues.apache.org/jira/browse/ATLAS-4028
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Update Atlas with httpclient 4.5.13 & httpcore 4.4.13



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

[jira] [Commented] (ATLAS-4013) JanusGraph 0.5.1 is not compatible with elasticsearch 5.*

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4013:
---

PC Build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/200/]

 

> JanusGraph 0.5.1 is not compatible with elasticsearch 5.*
> -
>
> Key: ATLAS-4013
> URL: https://issues.apache.org/jira/browse/ATLAS-4013
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: wforget
>Assignee: Radhika Kundam
>Priority: Major
> Attachments: 1.png, 2.png
>
>
> Atlas failed to initialize RestElasticSearchClient, due to 
> org.elasticsearch.client.Request is not compatible with the current 
> elasticsearch version. 



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

[jira] [Created] (ATLAS-4050) Atlas - upgrade log4j 2.11.0 to 2.13.2

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4050:
-

 Summary: Atlas - upgrade log4j 2.11.0 to 2.13.2
 Key: ATLAS-4050
 URL: https://issues.apache.org/jira/browse/ATLAS-4050
 Project: Atlas
  Issue Type: Task
  Components:  atlas-core
Affects Versions: 2.1.0
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Atlas using log4j2 version 2.11.0

Update log4j2 to version 2.13.2



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

[jira] [Created] (ATLAS-4051) Atlas - Remove jetty-jsp dependency

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4051:
-

 Summary: Atlas - Remove jetty-jsp dependency
 Key: ATLAS-4051
 URL: https://issues.apache.org/jira/browse/ATLAS-4051
 Project: Atlas
  Issue Type: Task
  Components:  atlas-core
Affects Versions: 2.1.0
Reporter: Radhika Kundam
Assignee: Radhika Kundam


jetty-jsp is an older glassfish JSP implementation and there is a newer 
implementation that defaults to jasper and is versioned with Jetty 9.4.x.

So jetty-jsp dependency can be removed.



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

[jira] [Commented] (ATLAS-4051) Atlas - Remove jetty-jsp dependency

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4051:
---

PC Build: 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/219/

> Atlas - Remove jetty-jsp dependency
> ---
>
> Key: ATLAS-4051
> URL: https://issues.apache.org/jira/browse/ATLAS-4051
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Minor
>
> jetty-jsp is an older glassfish JSP implementation and there is a newer 
> implementation that defaults to jasper and is versioned with Jetty 9.4.x.
> So jetty-jsp dependency can be removed.



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

[jira] [Commented] (ATLAS-4050) Atlas - upgrade log4j 2.11.0 to 2.13.2

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4050:
---

PC Build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/220/]

 

> Atlas - upgrade log4j 2.11.0 to 2.13.2
> --
>
> Key: ATLAS-4050
> URL: https://issues.apache.org/jira/browse/ATLAS-4050
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Minor
>
> Atlas using log4j2 version 2.11.0
> Update log4j2 to version 2.13.2



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

[jira] [Created] (ATLAS-4060) Update models with hive_db managedLocation attribute

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4060:
-

 Summary: Update models with hive_db managedLocation attribute
 Key: ATLAS-4060
 URL: https://issues.apache.org/jira/browse/ATLAS-4060
 Project: Atlas
  Issue Type: Task
Reporter: Radhika Kundam
Assignee: Radhika Kundam


HIVE added support for location for managed tables on database and introduced 
new attribute managedLocation.

Atlas Hive-hook should have support for managedLocation in hive_db entity.



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

[jira] [Updated] (ATLAS-4060) Update models with hive_db managedLocation attribute

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4060:
--
Description: 
HIVE added support for location for managed tables on database and introduced 
new attribute managedLocation.

Atlas Hive-hook should have support for managedLocation in hive_db entity.

Updating hive models with managedLocation.

Need to do hive-hook changes once Apache Hive release managedLocation feature.

  was:
HIVE added support for location for managed tables on database and introduced 
new attribute managedLocation.

Atlas Hive-hook should have support for managedLocation in hive_db entity.


> Update models with hive_db managedLocation attribute
> 
>
> Key: ATLAS-4060
> URL: https://issues.apache.org/jira/browse/ATLAS-4060
> Project: Atlas
>  Issue Type: Task
>    Reporter: Radhika Kundam
>        Assignee: Radhika Kundam
>Priority: Major
>
> HIVE added support for location for managed tables on database and introduced 
> new attribute managedLocation.
> Atlas Hive-hook should have support for managedLocation in hive_db entity.
> Updating hive models with managedLocation.
> Need to do hive-hook changes once Apache Hive release managedLocation feature.



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

[jira] [Created] (ATLAS-4061) Update Hive-Hook with hive_db attribute managedLocation

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4061:
-

 Summary: Update Hive-Hook with hive_db attribute managedLocation
 Key: ATLAS-4061
 URL: https://issues.apache.org/jira/browse/ATLAS-4061
 Project: Atlas
  Issue Type: Task
Reporter: Radhika Kundam
Assignee: Radhika Kundam


HIVE added support for location for managed tables on database and introduced 
new attribute managedLocation.

Atlas Hive-hook should have support for managedLocation in hive_db entity.

Updating hive models with managedLocation is done in ATLAS-4060.

Need to do hive-hook changes once Apache Hive release managedLocation feature.



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

[jira] [Updated] (ATLAS-4060) Update models with hive_db managedLocation attribute

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4060:
--
Description: 
HIVE added support for location for managed tables on database and introduced 
new attribute managedLocation.

Atlas Hive-hook should have support for managedLocation in hive_db entity.

Updating hive models with managedLocation.

Need to do hive-hook changes once Apache Hive release managedLocation 
feature(ATLAS-4061).

 

  was:
HIVE added support for location for managed tables on database and introduced 
new attribute managedLocation.

Atlas Hive-hook should have support for managedLocation in hive_db entity.

Updating hive models with managedLocation.

Need to do hive-hook changes once Apache Hive release managedLocation feature.


> Update models with hive_db managedLocation attribute
> 
>
> Key: ATLAS-4060
> URL: https://issues.apache.org/jira/browse/ATLAS-4060
> Project: Atlas
>  Issue Type: Task
>    Reporter: Radhika Kundam
>        Assignee: Radhika Kundam
>Priority: Major
>
> HIVE added support for location for managed tables on database and introduced 
> new attribute managedLocation.
> Atlas Hive-hook should have support for managedLocation in hive_db entity.
> Updating hive models with managedLocation.
> Need to do hive-hook changes once Apache Hive release managedLocation 
> feature(ATLAS-4061).
>  



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

[jira] [Commented] (ATLAS-4060) Update models with hive_db managedLocation attribute

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4060:
---

PC Build: 
[https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/274/]

> Update models with hive_db managedLocation attribute
> 
>
> Key: ATLAS-4060
> URL: https://issues.apache.org/jira/browse/ATLAS-4060
> Project: Atlas
>  Issue Type: Task
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
>
> HIVE added support for location for managed tables on database and introduced 
> new attribute managedLocation.
> Atlas Hive-hook should have support for managedLocation in hive_db entity.
> Updating hive models with managedLocation.
> Need to do hive-hook changes once Apache Hive release managedLocation 
> feature(ATLAS-4061).
>  



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

[jira] [Created] (ATLAS-4098) Add location relationship attribute for hive_db

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4098:
-

 Summary: Add location relationship attribute for hive_db
 Key: ATLAS-4098
 URL: https://issues.apache.org/jira/browse/ATLAS-4098
 Project: Atlas
  Issue Type: Task
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Add new relationship attribute "location" for hive_db entity. This location 
attribute holds the path of the hive_db create script file.

This location relationship attribute should be created with endDef1 as 
"hive_db" and endDef2 as "Path".

"Path" is superType for path/location of any type of file storage like AWS s3 
directory path, Azure ADLS storage path, HDFS Path etc.



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

[jira] [Updated] (ATLAS-4098) Add location relationship attribute for hive_db

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4098:
--
Description: 
Add new relationship attribute "location" for hive_db entity. This location 
attribute holds the details about the path of the hive_db create script file. 

"Path" is superType of location entity which can be used for any type of file 
storage like AWS s3 directory, Azure ADLS storage, HDFS  etc.

This location relationship attribute should be created with endDef1 as 
"hive_db" and endDef2 as "Path".

  was:
Add new relationship attribute "location" for hive_db entity. This location 
attribute holds the path of the hive_db create script file.

This location relationship attribute should be created with endDef1 as 
"hive_db" and endDef2 as "Path".

"Path" is superType for path/location of any type of file storage like AWS s3 
directory path, Azure ADLS storage path, HDFS Path etc.


> Add location relationship attribute for hive_db
> ---
>
> Key: ATLAS-4098
> URL: https://issues.apache.org/jira/browse/ATLAS-4098
> Project: Atlas
>  Issue Type: Task
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Add new relationship attribute "location" for hive_db entity. This location 
> attribute holds the details about the path of the hive_db create script file. 
> "Path" is superType of location entity which can be used for any type of file 
> storage like AWS s3 directory, Azure ADLS storage, HDFS  etc.
> This location relationship attribute should be created with endDef1 as 
> "hive_db" and endDef2 as "Path".



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

[jira] [Updated] (ATLAS-4098) Add location relationship attribute for hive_db

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4098:
--
Description: 
Requirement is to add "location" as one of the relationships to hive_db. With 
this we can create a "location" entity based on the type of file storage and 
assign it to hive_db relationship attributes.

Since we are creating entities for location we can get more details about the 
path. To support location entity with all types of file storage, need to create 
a super type for all types of location entities.

For that purpose, introduce new layer between DataSet and other location 
entities which are derived from DataSet. Create "Path" entity which should be 
derived from "DataSet" entity and "Path" should be a super type of all other 
location entities. AWS s3 directory(aws_s3_v2_directory ), Azure ADLS 
storage(adls_gen2_directory), HDFS(hdfs_path ) are the few location entities 
which will be subtypes of "Path" entity.

This location relationship attribute should be created with endDef1 as 
"hive_db" and endDef2 as "Path".

  was:
Add new relationship attribute "location" for hive_db entity. This location 
attribute holds the details about the path of the hive_db create script file. 

"Path" is superType of location entity which can be used for any type of file 
storage like AWS s3 directory, Azure ADLS storage, HDFS  etc.

This location relationship attribute should be created with endDef1 as 
"hive_db" and endDef2 as "Path".


> Add location relationship attribute for hive_db
> ---
>
> Key: ATLAS-4098
> URL: https://issues.apache.org/jira/browse/ATLAS-4098
> Project: Atlas
>  Issue Type: Task
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Requirement is to add "location" as one of the relationships to hive_db. With 
> this we can create a "location" entity based on the type of file storage and 
> assign it to hive_db relationship attributes.
> Since we are creating entities for location we can get more details about the 
> path. To support location entity with all types of file storage, need to 
> create a super type for all types of location entities.
> For that purpose, introduce new layer between DataSet and other location 
> entities which are derived from DataSet. Create "Path" entity which should be 
> derived from "DataSet" entity and "Path" should be a super type of all other 
> location entities. AWS s3 directory(aws_s3_v2_directory ), Azure ADLS 
> storage(adls_gen2_directory), HDFS(hdfs_path ) are the few location entities 
> which will be subtypes of "Path" entity.
> This location relationship attribute should be created with endDef1 as 
> "hive_db" and endDef2 as "Path".



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

[jira] [Updated] (ATLAS-4098) Add location relationship attribute for hive_db

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4098:
--
Issue Type: New Feature  (was: Task)

> Add location relationship attribute for hive_db
> ---
>
> Key: ATLAS-4098
> URL: https://issues.apache.org/jira/browse/ATLAS-4098
> Project: Atlas
>  Issue Type: New Feature
>    Reporter: Radhika Kundam
>        Assignee: Radhika Kundam
>Priority: Major
>
> Requirement is to add "location" as one of the relationships to hive_db. With 
> this we can create a "location" entity based on the type of file storage and 
> assign it to hive_db relationship attributes.
> Since we are creating entities for location we can get more details about the 
> path. To support location entity with all types of file storage, need to 
> create a super type for all types of location entities.
> For that purpose, introduce new layer between DataSet and other location 
> entities which are derived from DataSet. Create "Path" entity which should be 
> derived from "DataSet" entity and "Path" should be a super type of all other 
> location entities. AWS s3 directory(aws_s3_v2_directory ), Azure ADLS 
> storage(adls_gen2_directory), HDFS(hdfs_path ) are the few location entities 
> which will be subtypes of "Path" entity.
> This location relationship attribute should be created with endDef1 as 
> "hive_db" and endDef2 as "Path".



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

[jira] [Created] (ATLAS-4117) Rename hive_db relationship attributes location and managedLocation

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4117:
-

 Summary: Rename hive_db relationship attributes location and 
managedLocation
 Key: ATLAS-4117
 URL: https://issues.apache.org/jira/browse/ATLAS-4117
 Project: Atlas
  Issue Type: Task
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Rename hive_db relationship attributes as below to make differentiation between 
attributes & relationship attributes.

Rename "location" to "locationPath"

Rename "managedLocation" to "managedLocationPath"



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

[jira] [Updated] (ATLAS-4117) Rename hive_db relationship attributes location

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4117:
--
Summary: Rename hive_db relationship attributes location  (was: Rename 
hive_db relationship attributes location and managedLocation)

> Rename hive_db relationship attributes location
> ---
>
> Key: ATLAS-4117
> URL: https://issues.apache.org/jira/browse/ATLAS-4117
> Project: Atlas
>  Issue Type: Task
>    Reporter: Radhika Kundam
>        Assignee: Radhika Kundam
>Priority: Major
>
> Rename hive_db relationship attributes as below to make differentiation 
> between attributes & relationship attributes.
> Rename "location" to "locationPath"
> Rename "managedLocation" to "managedLocationPath"



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

[jira] [Updated] (ATLAS-4117) Rename hive_db relationship attributes location

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4117:
--
Description: 
Rename hive_db relationship attributes as below to make differentiation between 
attributes & relationship attributes.

Rename "location" to "locationPath"

  was:
Rename hive_db relationship attributes as below to make differentiation between 
attributes & relationship attributes.

Rename "location" to "locationPath"

Rename "managedLocation" to "managedLocationPath"


> Rename hive_db relationship attributes location
> ---
>
> Key: ATLAS-4117
> URL: https://issues.apache.org/jira/browse/ATLAS-4117
>     Project: Atlas
>      Issue Type: Task
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Rename hive_db relationship attributes as below to make differentiation 
> between attributes & relationship attributes.
> Rename "location" to "locationPath"



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

[jira] [Created] (ATLAS-4125) Create JavaPatch to add new supertypes to existing entities

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4125:
-

 Summary: Create JavaPatch to add new supertypes to existing 
entities
 Key: ATLAS-4125
 URL: https://issues.apache.org/jira/browse/ATLAS-4125
 Project: Atlas
  Issue Type: Task
Reporter: Radhika Kundam
Assignee: Radhika Kundam


As part of ATLAS-4098 introduced adding new super type for existing entity type 
which is done by new action type "ADD_SUPER_TYPES" for Typedef patches. With 
this patch, it will update entityType's definition with new superTypes.

To provide backward compatibility for the above feature, we need to update 
__superTypes for below.

1. All vertices with type of updated entityDef

2. All vertices of all sub-types of updated entityDef 



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

[jira] [Created] (ATLAS-4169) Add Hive Location Path entities to HMS Hook

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4169:
-

 Summary: Add Hive Location Path entities to HMS Hook
 Key: ATLAS-4169
 URL: https://issues.apache.org/jira/browse/ATLAS-4169
 Project: Atlas
  Issue Type: Bug
Reporter: Radhika Kundam
Assignee: Radhika Kundam


In ATLAS-4098 added location path entity to hive_db entity. This feature was 
handled only for HS2 but missing for HMS.

When hive_db created either using HMS or HS2, hive_db entity should have path 
entity as new relationship attribute.



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

[jira] [Commented] (ATLAS-4169) Add Hive Location Path entities to HMS Hook

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4169:
---

Submitted review request: [https://reviews.apache.org/r/73192/]

 

> Add Hive Location Path entities to HMS Hook
> ---
>
> Key: ATLAS-4169
> URL: https://issues.apache.org/jira/browse/ATLAS-4169
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
>
> In ATLAS-4098 added location path entity to hive_db entity. This feature was 
> handled only for HS2 but missing for HMS.
> When hive_db created either using HMS or HS2, hive_db entity should have path 
> entity as new relationship attribute.



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

[jira] [Created] (ATLAS-4181) Add mandatory attributes to existing entity definition

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4181:
-

 Summary: Add mandatory attributes to existing entity definition
 Key: ATLAS-4181
 URL: https://issues.apache.org/jira/browse/ATLAS-4181
 Project: Atlas
  Issue Type: Bug
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Currently, Atlas allows to add only optional attributes to existing entity type 
and it doesn’t allow to add any mandatory attribute.

Atlas should allow users to add mandatory attributes to existing entity types. 
To provide backward compatibility without breaking any contract between updated 
entity definition and existing entities, once entity def gets updated with 
mandatory attribute it should update all entities of same type and all subtypes 
with mandatory attribute.

This feature should allow only if new mandatory attribute has non-empty default 
value.



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

[jira] [Updated] (ATLAS-4181) Provide option to add mandatory attribute to existing entity definition

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4181:
--
Issue Type: Improvement  (was: Bug)

> Provide option to add mandatory attribute to existing entity definition
> ---
>
> Key: ATLAS-4181
> URL: https://issues.apache.org/jira/browse/ATLAS-4181
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Currently, Atlas allows to add only optional attributes to existing entity 
> type and it doesn’t allow to add any mandatory attribute.
> Atlas should allow users to add mandatory attributes to existing entity 
> types. To provide backward compatibility without breaking any contract 
> between updated entity definition and existing entities, once entity def gets 
> updated with mandatory attribute it should update all entities of same type 
> and all subtypes with mandatory attribute.
> This feature should allow only if new mandatory attribute has non-empty 
> default value.



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

[jira] [Updated] (ATLAS-4181) Provide option to add mandatory attribute to existing entity definition

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4181:
--
Summary: Provide option to add mandatory attribute to existing entity 
definition  (was: Add mandatory attributes to existing entity definition)

> Provide option to add mandatory attribute to existing entity definition
> ---
>
> Key: ATLAS-4181
> URL: https://issues.apache.org/jira/browse/ATLAS-4181
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Currently, Atlas allows to add only optional attributes to existing entity 
> type and it doesn’t allow to add any mandatory attribute.
> Atlas should allow users to add mandatory attributes to existing entity 
> types. To provide backward compatibility without breaking any contract 
> between updated entity definition and existing entities, once entity def gets 
> updated with mandatory attribute it should update all entities of same type 
> and all subtypes with mandatory attribute.
> This feature should allow only if new mandatory attribute has non-empty 
> default value.



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

[jira] [Updated] (ATLAS-4181) Provide option to add mandatory attribute to existing entity definition

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4181:
--
Description: 
Currently, Atlas allows to add only optional attributes to existing entity type 
and it doesn’t allow to add any mandatory attribute.

Atlas should allow users to add mandatory attributes to existing entity types. 
To provide backward compatibility without breaking any contract between updated 
entity definition and existing entities, once entity def gets updated with 
mandatory attribute it should update all entities of same type and all subtypes 
with mandatory attribute.

This feature should allow only if new mandatory attribute has non-empty default 
value.

Design diagram attached for reference.

  was:
Currently, Atlas allows to add only optional attributes to existing entity type 
and it doesn’t allow to add any mandatory attribute.

Atlas should allow users to add mandatory attributes to existing entity types. 
To provide backward compatibility without breaking any contract between updated 
entity definition and existing entities, once entity def gets updated with 
mandatory attribute it should update all entities of same type and all subtypes 
with mandatory attribute.

This feature should allow only if new mandatory attribute has non-empty default 
value.


> Provide option to add mandatory attribute to existing entity definition
> ---
>
> Key: ATLAS-4181
> URL: https://issues.apache.org/jira/browse/ATLAS-4181
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Design_Diagram_For_Add_Mandatory_Attribute.png
>
>
> Currently, Atlas allows to add only optional attributes to existing entity 
> type and it doesn’t allow to add any mandatory attribute.
> Atlas should allow users to add mandatory attributes to existing entity 
> types. To provide backward compatibility without breaking any contract 
> between updated entity definition and existing entities, once entity def gets 
> updated with mandatory attribute it should update all entities of same type 
> and all subtypes with mandatory attribute.
> This feature should allow only if new mandatory attribute has non-empty 
> default value.
> Design diagram attached for reference.



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

[jira] [Updated] (ATLAS-4181) Provide option to add mandatory attribute to existing entity definition

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4181:
--
Attachment: Design_Diagram_For_Add_Mandatory_Attribute.png

> Provide option to add mandatory attribute to existing entity definition
> ---
>
> Key: ATLAS-4181
> URL: https://issues.apache.org/jira/browse/ATLAS-4181
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Design_Diagram_For_Add_Mandatory_Attribute.png
>
>
> Currently, Atlas allows to add only optional attributes to existing entity 
> type and it doesn’t allow to add any mandatory attribute.
> Atlas should allow users to add mandatory attributes to existing entity 
> types. To provide backward compatibility without breaking any contract 
> between updated entity definition and existing entities, once entity def gets 
> updated with mandatory attribute it should update all entities of same type 
> and all subtypes with mandatory attribute.
> This feature should allow only if new mandatory attribute has non-empty 
> default value.
> Design diagram attached for reference.



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

[jira] [Updated] (ATLAS-4181) Provide option to add mandatory attribute to existing entity definition

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4181:
--
Description: 
Currently, Atlas allows to add only optional attributes to existing entity type 
and it doesn’t allow to add any mandatory attribute.

Atlas should allow users to add mandatory attributes to existing entity types. 
To provide backward compatibility without breaking any contract between updated 
entity definition and existing entities, once entity def gets updated with 
mandatory attribute it should update all entities of same type and all subtypes 
with mandatory attribute.

This feature should allow only if new mandatory attribute is primitive type and 
has non-empty default value.

Design diagram attached for reference.

  was:
Currently, Atlas allows to add only optional attributes to existing entity type 
and it doesn’t allow to add any mandatory attribute.

Atlas should allow users to add mandatory attributes to existing entity types. 
To provide backward compatibility without breaking any contract between updated 
entity definition and existing entities, once entity def gets updated with 
mandatory attribute it should update all entities of same type and all subtypes 
with mandatory attribute.

This feature should allow only if new mandatory attribute has non-empty default 
value.

Design diagram attached for reference.


> Provide option to add mandatory attribute to existing entity definition
> ---
>
> Key: ATLAS-4181
> URL: https://issues.apache.org/jira/browse/ATLAS-4181
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Design_Diagram_For_Add_Mandatory_Attribute.png
>
>
> Currently, Atlas allows to add only optional attributes to existing entity 
> type and it doesn’t allow to add any mandatory attribute.
> Atlas should allow users to add mandatory attributes to existing entity 
> types. To provide backward compatibility without breaking any contract 
> between updated entity definition and existing entities, once entity def gets 
> updated with mandatory attribute it should update all entities of same type 
> and all subtypes with mandatory attribute.
> This feature should allow only if new mandatory attribute is primitive type 
> and has non-empty default value.
> Design diagram attached for reference.



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

[jira] [Updated] (ATLAS-4181) Provide option to add mandatory attribute to existing entity definition

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4181:
--
Description: 
Currently, Atlas allows to add only optional attributes to existing entity type 
and it doesn’t allow to add any mandatory attribute.

Atlas should allow users to add mandatory attributes to existing entity types. 
To provide backward compatibility without breaking any contract between updated 
entity definition and existing entities, once entity def gets updated with 
mandatory attribute it should update all entities of same type and all subtypes 
with mandatory attribute.

This feature should allow only if new mandatory attribute is primitive type, 
non-unique and has non-empty default value.

Design diagram attached for reference.

With this feature, mandatory attributes can be added to existing typedef using 
"ADD_MANDATORY_ATTRIBUTE" typedef patch action.

Below is the sample of data to be used to patch.

{
 "id": "",
 "description": "",
 "action": "*ADD_MANDATORY_ATTRIBUTE*",
 "typeName": "",
 "applyToVersion": "1.1",
 "updateToVersion": "1.2",
 "params": null,
 "attributeDefs": [
 {
 "name": "",
 "typeName": "",
 "cardinality": "SINGLE",
 "isIndexable": false,
"isOptional": false,
 "isUnique": false,
 "defaultValue": ""
 }
 ]
}

  was:
Currently, Atlas allows to add only optional attributes to existing entity type 
and it doesn’t allow to add any mandatory attribute.

Atlas should allow users to add mandatory attributes to existing entity types. 
To provide backward compatibility without breaking any contract between updated 
entity definition and existing entities, once entity def gets updated with 
mandatory attribute it should update all entities of same type and all subtypes 
with mandatory attribute.

This feature should allow only if new mandatory attribute is primitive type and 
has non-empty default value.

Design diagram attached for reference.


> Provide option to add mandatory attribute to existing entity definition
> ---
>
> Key: ATLAS-4181
> URL: https://issues.apache.org/jira/browse/ATLAS-4181
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Design_Diagram_For_Add_Mandatory_Attribute.png
>
>
> Currently, Atlas allows to add only optional attributes to existing entity 
> type and it doesn’t allow to add any mandatory attribute.
> Atlas should allow users to add mandatory attributes to existing entity 
> types. To provide backward compatibility without breaking any contract 
> between updated entity definition and existing entities, once entity def gets 
> updated with mandatory attribute it should update all entities of same type 
> and all subtypes with mandatory attribute.
> This feature should allow only if new mandatory attribute is primitive type, 
> non-unique and has non-empty default value.
> Design diagram attached for reference.
> With this feature, mandatory attributes can be added to existing typedef 
> using "ADD_MANDATORY_ATTRIBUTE" typedef patch action.
> Below is the sample of data to be used to patch.
> {
>  "id": "",
>  "description": "",
>  "action": "*ADD_MANDATORY_ATTRIBUTE*",
>  "typeName": "",
>  "applyToVersion": "1.1",
>  "updateToVersion": "1.2",
>  "params": null,
>  "attributeDefs": [
>  {
>  "name": "",
>  "typeName": "",
>  "cardinality": "SINGLE",
>  "isIndexable": false,
> "isOptional": false,
>  "isUnique": false,
>  "defaultValue": ""
>  }
>  ]
> }



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

[jira] [Assigned] (ATLAS-4241) import-hbase.sh get map error

[Radhika Kundam (Jira)]

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

Radhika Kundam reassigned ATLAS-4241:
-

Assignee: Radhika Kundam

> import-hbase.sh get map error
> -
>
> Key: ATLAS-4241
> URL: https://issues.apache.org/jira/browse/ATLAS-4241
> Project: Atlas
>  Issue Type: Bug
>  Components: hbase-integration
>Affects Versions: 2.1.0
>Reporter: junsionzhang
>    Assignee: Radhika Kundam
>Priority: Major
>
> when run import-hbase.sh ,errors is as follows:
> 2021-04-12 14:34:25,865 ERROR - [main:] ~ ImportHBaseEntities failed 
> (HBaseBridge:197)
> org.apache.atlas.AtlasException: Failed to load application properties
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:147)
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:100)
>  at org.apache.atlas.hbase.bridge.HBaseBridge.main(HBaseBridge.java:139)
> Caused by: org.apache.commons.configuration.ConversionException: 
> 'atlas.graph.index.search.solr.wait-searcher' doesn't map to a List object: 
> true, a java.lang.Boolean
>  at 
> org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1144)
>  at 
> org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1109)
>  at 
> org.apache.commons.configuration.AbstractConfiguration.interpolatedConfiguration(AbstractConfiguration.java:1274)
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:142)
>  ... 2 more
>  
> It seems the common-configuration does not work correctly . the hbasebridge 
> use common-configuration 1.10 ,but the version also exists.  could somebody 
> upgrade from 1.x to 2.x
>  
> https://commons.apache.org/proper/commons-configuration/userguide/upgradeto2_0.html



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

[jira] [Created] (ATLAS-4249) DML statements like "insert", "delete" are captured by Atlas

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4249:
-

 Summary: DML statements like "insert", "delete" are captured by 
Atlas
 Key: ATLAS-4249
 URL: https://issues.apache.org/jira/browse/ATLAS-4249
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
        Reporter: Radhika Kundam
        Assignee: Radhika Kundam


Extra audits are generated by Atlas for DML statements on tables like insert 
and delete values on table.

Notification for `insert into db_dbmch.table_wilfp values(1,'Tom','19/02/1988')`
{code:java}
{"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"172.27.109.4","msgCreatedBy":"","msgCreationTime":1613131228459,"message":{"type":"ENTITY_NOTIFICATION_V2","entity":{"typeName":"hive_table","attributes":{"owner":"hrt_qa","createTime":1613129664000,"qualifiedName":"db_dbmch.table_wilfp@cl1","name":"table_wilfp"},"guid":"81bc8fe2-ffcf-41a5-a4ff-5f43aafb4f22","displayText":"table_wilfp","isIncomplete":false},"operationType":"ENTITY_UPDATE","eventTime":1613131228304}}
 {code}



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

[jira] [Updated] (ATLAS-4249) DML statements like "insert", "delete" are captured by Atlas

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4249:
--
Affects Version/s: 2.1.0

> DML statements like "insert", "delete" are captured by Atlas
> 
>
> Key: ATLAS-4249
> URL: https://issues.apache.org/jira/browse/ATLAS-4249
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Extra audits are generated by Atlas for DML statements on tables like insert 
> and delete values on table.
> Notification for `insert into db_dbmch.table_wilfp 
> values(1,'Tom','19/02/1988')`
> {code:java}
> {"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"172.27.109.4","msgCreatedBy":"","msgCreationTime":1613131228459,"message":{"type":"ENTITY_NOTIFICATION_V2","entity":{"typeName":"hive_table","attributes":{"owner":"hrt_qa","createTime":1613129664000,"qualifiedName":"db_dbmch.table_wilfp@cl1","name":"table_wilfp"},"guid":"81bc8fe2-ffcf-41a5-a4ff-5f43aafb4f22","displayText":"table_wilfp","isIncomplete":false},"operationType":"ENTITY_UPDATE","eventTime":1613131228304}}
>  {code}



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

[jira] [Commented] (ATLAS-4241) import-hbase.sh get map error

[Radhika Kundam (Jira)]

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

Radhika Kundam commented on ATLAS-4241:
---

[~junsionzhang],

Could you please provide the steps for reproducing the issue along with HBase 
and Hadoop versions you are using.

It would be helpful if you can print the classpath while executing 
import-hbase.sh and provide that classpath.

 

> import-hbase.sh get map error
> -
>
> Key: ATLAS-4241
> URL: https://issues.apache.org/jira/browse/ATLAS-4241
> Project: Atlas
>  Issue Type: Bug
>  Components: hbase-integration
>Affects Versions: 2.1.0
>Reporter: junsionzhang
>Assignee: Radhika Kundam
>Priority: Major
>
> when run import-hbase.sh ,errors is as follows:
> 2021-04-12 14:34:25,865 ERROR - [main:] ~ ImportHBaseEntities failed 
> (HBaseBridge:197)
> org.apache.atlas.AtlasException: Failed to load application properties
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:147)
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:100)
>  at org.apache.atlas.hbase.bridge.HBaseBridge.main(HBaseBridge.java:139)
> Caused by: org.apache.commons.configuration.ConversionException: 
> 'atlas.graph.index.search.solr.wait-searcher' doesn't map to a List object: 
> true, a java.lang.Boolean
>  at 
> org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1144)
>  at 
> org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1109)
>  at 
> org.apache.commons.configuration.AbstractConfiguration.interpolatedConfiguration(AbstractConfiguration.java:1274)
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:142)
>  ... 2 more
>  
> It seems the common-configuration does not work correctly . the hbasebridge 
> use common-configuration 1.10 ,but the version also exists.  could somebody 
> upgrade from 1.x to 2.x
>  
> https://commons.apache.org/proper/commons-configuration/userguide/upgradeto2_0.html



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

[jira] [Created] (ATLAS-4257) Atlas - Upgrade groovy to 2.4.21+, 2.5.14+, 3.0.7+, or 4.0.0-alpha-2+ due to CVE-2020-17521

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4257:
-

 Summary: Atlas - Upgrade groovy to 2.4.21+, 2.5.14+, 3.0.7+, or 
4.0.0-alpha-2+ due to CVE-2020-17521
 Key: ATLAS-4257
 URL: https://issues.apache.org/jira/browse/ATLAS-4257
 Project: Atlas
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Atlas is pulling in groovy 2.5.7 due to tinkerpop gremlin.

Need to upgrade to groovy 2.5.14+

This comes up in a few paths:
 * ./usr/lib/atlas/server/webapp/atlas/WEB-INF/lib/groovy-2.5.7-indy.jar
 * ./usr/lib/atlas/server/webapp/atlas/WEB-INF/lib/groovy-xml-2.5.7.jar



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

[jira] [Updated] (ATLAS-4257) Atlas - Upgrade groovy to 2.4.21+, 2.5.14+, 3.0.7+, or 4.0.0-alpha-2+ due to CVE-2020-17521

[Radhika Kundam (Jira)]

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

Radhika Kundam updated ATLAS-4257:
--
Description: 
Atlas is pulling in groovy 2.5.7 due to tinkerpop gremlin.

Need to upgrade to groovy 2.5.14+ to stay on the 2.5.x line like gremlin has.

This comes up in a few paths:
 * ./usr/lib/atlas/server/webapp/atlas/WEB-INF/lib/groovy-2.5.7-indy.jar
 * ./usr/lib/atlas/server/webapp/atlas/WEB-INF/lib/groovy-xml-2.5.7.jar

  was:
Atlas is pulling in groovy 2.5.7 due to tinkerpop gremlin.

Need to upgrade to groovy 2.5.14+

This comes up in a few paths:
 * ./usr/lib/atlas/server/webapp/atlas/WEB-INF/lib/groovy-2.5.7-indy.jar
 * ./usr/lib/atlas/server/webapp/atlas/WEB-INF/lib/groovy-xml-2.5.7.jar


> Atlas - Upgrade groovy to 2.4.21+, 2.5.14+, 3.0.7+, or 4.0.0-alpha-2+ due to 
> CVE-2020-17521
> ---
>
> Key: ATLAS-4257
> URL: https://issues.apache.org/jira/browse/ATLAS-4257
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>    Reporter: Radhika Kundam
>    Assignee: Radhika Kundam
>Priority: Major
>
> Atlas is pulling in groovy 2.5.7 due to tinkerpop gremlin.
> Need to upgrade to groovy 2.5.14+ to stay on the 2.5.x line like gremlin has.
> This comes up in a few paths:
>  * ./usr/lib/atlas/server/webapp/atlas/WEB-INF/lib/groovy-2.5.7-indy.jar
>  * ./usr/lib/atlas/server/webapp/atlas/WEB-INF/lib/groovy-xml-2.5.7.jar



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