Re: Review Request 70236: ATLAS-3077: Handle java patches in patch framework

[madhan]

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




repository/src/main/java/org/apache/atlas/repository/patches/PatchContext.java
Lines 41 (patched)


Patch context instances shouldn't need to be serialized. Please review and 
remove "implements Serializable" and Json serailizaion annotations.



repository/src/main/java/org/apache/atlas/repository/patches/PatchContext.java
Lines 79 (patched)


are equals(), hashCode() and toString() methods necessary for PatchContext?



repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
Lines 101 (patched)


- consider changing the log level to "debug" - to avoid large number of 
logs for Atlas instances having millions of entities.
- consider adding "info" level logs at the start and end of each 
entity-type - line #76, #124
- consider logging progress periodically, like (in #123):
  if (entityCount % 1000 == 0) {
LOG.info("JavaPatch({}): processed {} entities", getPatchId(), 
entityCount);
  }



repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
Lines 104 (patched)


isPatchApplied will be false only if there are no entity that needed 
unique-key property to be set. Such cases should be treated as success, rather 
than skipped - since the patch has nothing to do.



repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
Lines 120 (patched)


IndexException could be due to presence of multiple entities with the same 
unique key value. Instead of treating this as a failure and abort processing, 
consider adding a warn log and continue:

  LOG.warn("JavaPatch({}): failed to update entity guid={}, typeName={}, 
attrName={}, attrValue={}", getPatchId(), typeName, attribute.getName(),  
uniqAttrValue);

Above log will be helpful in manually fixing the condition.



repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
Lines 132 (patched)


Consider moving this method to base class 'AtlasJavaPatchHandler', as this 
could be useful for other Java patches as well.



repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
Lines 200 (patched)


Every startup will print this info log, followed by a "ignoring" log 
(UniqueAttributePatchHandler.java#64).  Consider the following:

for (AtlasJavaPatchHandler patch : patches) {
  PatchStatus patchStatus = patch.getPatchStatus();

  if (patchStatus == APPLIED || patchStatus == SKIPPED) {
LOG.info("Ignoring java patch {}; status: {}", patch.getPatchId(), 
patchStatus);
  } else {
patch.applyPatch();
  }
}



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasGraphUtilsV2.java
Lines 562 (patched)


Consider renaming this method: findEntityVerticesByType() => 
findActiveEntityVerticesByType()


- madhan


On March 20, 2019, 9:29 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70236/
> ---
> 
> (Updated March 20, 2019, 9:29 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Kapildeo Nayak, madhan, Nikhil 
> Bonte, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-3077
> https://issues.apache.org/jira/browse/ATLAS-3077
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> We have Atlas typedef patches available to update out of box type 
> definitions. This JIRA will introduce a new java patch framework to handle 
> changes to the graph database not specific to type changes.
> 
> For e.g. In case of migration, to add/update property keys in vertices - java 
> patch framework can be used, which will be run at the atlas startup time 
> during bootstrap.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/model/patches/AtlasPatch.java cdf2441d2 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  4805435c7 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/AtlasJavaPatchHandler.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/PatchContext.java
>  PRE-CREATION 
>   
> 

Re: Review Request 70236: ATLAS-3077: Handle java patches in patch framework

[Ashutosh Mestry]

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




repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
Lines 93 (patched)


Consider ProducerConsumer framwork for handling large datasets.



repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
Lines 108 (patched)


Consider periodic commits. Have a batch size and commit each time N number 
of vertices are processed. That will alleviate long startup times on failures.


- Ashutosh Mestry


On March 20, 2019, 9:29 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70236/
> ---
> 
> (Updated March 20, 2019, 9:29 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Kapildeo Nayak, madhan, Nikhil 
> Bonte, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-3077
> https://issues.apache.org/jira/browse/ATLAS-3077
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> We have Atlas typedef patches available to update out of box type 
> definitions. This JIRA will introduce a new java patch framework to handle 
> changes to the graph database not specific to type changes.
> 
> For e.g. In case of migration, to add/update property keys in vertices - java 
> patch framework can be used, which will be run at the atlas startup time 
> during bootstrap.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/model/patches/AtlasPatch.java cdf2441d2 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  4805435c7 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/AtlasJavaPatchHandler.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/PatchContext.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
>  337a6db6c 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasGraphUtilsV2.java
>  2d5fd9706 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> 01bdcf7e2 
> 
> 
> Diff: https://reviews.apache.org/r/70236/diff/2/
> 
> 
> Testing
> ---
> 
> Verified with migrated data that patch was applied cleanly
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 70236: ATLAS-3077: Handle java patches in patch framework

[Sarath Subramanian]

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

(Updated March 20, 2019, 2:29 p.m.)


Review request for atlas, Ashutosh Mestry, Kapildeo Nayak, madhan, Nikhil 
Bonte, and Nixon Rodrigues.


Changes
---

addressed review comments.


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


Repository: atlas


Description
---

We have Atlas typedef patches available to update out of box type definitions. 
This JIRA will introduce a new java patch framework to handle changes to the 
graph database not specific to type changes.

For e.g. In case of migration, to add/update property keys in vertices - java 
patch framework can be used, which will be run at the atlas startup time during 
bootstrap.


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/model/patches/AtlasPatch.java cdf2441d2 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
 4805435c7 
  
repository/src/main/java/org/apache/atlas/repository/patches/AtlasJavaPatchHandler.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/patches/PatchContext.java 
PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
 337a6db6c 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasGraphUtilsV2.java
 2d5fd9706 
  webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
01bdcf7e2 


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

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


Testing
---

Verified with migrated data that patch was applied cleanly


Thanks,

Sarath Subramanian

Re: Review Request 70236: ATLAS-3077: Handle java patches in patch framework

[Sarath Subramanian]

> On March 20, 2019, 8:50 a.m., Xinran Tinney wrote:
> > intg/src/main/java/org/apache/atlas/model/patches/AtlasPatch.java
> > Line 53 (original), 53 (patched)
> > 
> >
> > Is there any reason the order is changed?

no specific reason, just to maintain some logical order


- Sarath


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


On March 18, 2019, 4:15 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70236/
> ---
> 
> (Updated March 18, 2019, 4:15 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Kapildeo Nayak, madhan, Nikhil 
> Bonte, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-3077
> https://issues.apache.org/jira/browse/ATLAS-3077
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> We have Atlas typedef patches available to update out of box type 
> definitions. This JIRA will introduce a new java patch framework to handle 
> changes to the graph database not specific to type changes.
> 
> For e.g. In case of migration, to add/update property keys in vertices - java 
> patch framework can be used, which will be run at the atlas startup time 
> during bootstrap.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/model/patches/AtlasPatch.java cdf2441d2 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  4805435c7 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/AtlasJavaPatchHandler.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/PatchContext.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
>  337a6db6c 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasGraphUtilsV2.java
>  5827dad52 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> 01bdcf7e2 
> 
> 
> Diff: https://reviews.apache.org/r/70236/diff/1/
> 
> 
> Testing
> ---
> 
> Verified with migrated data that patch was applied cleanly
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

[jira] [Commented] (ATLAS-3067) update hive types to remove use of ownedRef/inverseRef constraints for relationships

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3067:


Commit c4ce2b4c06e9ae5aae62161828658ce4df6561f8 in atlas's branch 
refs/heads/branch-1.0 from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c4ce2b4 ]

ATLAS-3067: fix for IT failure in EntityJerseyResourceIT.testCompleteUpdate()

(cherry picked from commit 2c0a8bcc1afe1588a1ffc3ea175bb29055c55894)


> update hive types to remove use of ownedRef/inverseRef constraints for 
> relationships
> 
>
> Key: ATLAS-3067
> URL: https://issues.apache.org/jira/browse/ATLAS-3067
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3067.patch
>
>
> Similar to recent updates in RDBMS entity-types (ATLAS-3056), Hive 
> entity-types should be updated to remove attributes that refer to other 
> entities, as equivalent relationship-types already cover the relationship 
> between these entity-types. Here is the list of attributes to be removed:
>  - hive_table.db (covered by hive_table_db)
>  - hive_table.sd, hive_storagedesc.table (covered by hive_table_storagedesc)
>  - hive_table.partitionKeys, hive_column.table (covered by 
> hive_table_partitionkeys)
>  - hive_table.columns, hive_column.table (covered by hive_table_columns)
>  - hive_column_lineage.query (covered by hive_process_column_lineage)



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

[jira] [Commented] (ATLAS-3067) update hive types to remove use of ownedRef/inverseRef constraints for relationships

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3067:


Commit 2c0a8bcc1afe1588a1ffc3ea175bb29055c55894 in atlas's branch 
refs/heads/master from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2c0a8bc ]

ATLAS-3067: fix for IT failure in EntityJerseyResourceIT.testCompleteUpdate()


> update hive types to remove use of ownedRef/inverseRef constraints for 
> relationships
> 
>
> Key: ATLAS-3067
> URL: https://issues.apache.org/jira/browse/ATLAS-3067
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3067.patch
>
>
> Similar to recent updates in RDBMS entity-types (ATLAS-3056), Hive 
> entity-types should be updated to remove attributes that refer to other 
> entities, as equivalent relationship-types already cover the relationship 
> between these entity-types. Here is the list of attributes to be removed:
>  - hive_table.db (covered by hive_table_db)
>  - hive_table.sd, hive_storagedesc.table (covered by hive_table_storagedesc)
>  - hive_table.partitionKeys, hive_column.table (covered by 
> hive_table_partitionkeys)
>  - hive_table.columns, hive_column.table (covered by hive_table_columns)
>  - hive_column_lineage.query (covered by hive_process_column_lineage)



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

[jira] [Commented] (ATLAS-3031) UI : Allow user to export the lineage in PNG or JPEG format

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3031:


Commit 622d7d32073bbe037da3a38d11da06acfe7503e6 in atlas's branch 
refs/heads/branch-1.0 from gutkaBinit
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=622d7d3 ]

ATLAS-3031: UI : Allow user to export the lineage in PNG formatt

Signed-off-by: Sarath Subramanian 
(cherry picked from commit 27916dd49f854678b84bde8023aee6e47cbeb7ce)


> UI : Allow user to export the lineage in PNG or JPEG format
> ---
>
> Key: ATLAS-3031
> URL: https://issues.apache.org/jira/browse/ATLAS-3031
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Binit Gutka
>Priority: Major
> Attachments: ATLAS-3031.patch
>
>




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

[jira] [Commented] (ATLAS-3031) UI : Allow user to export the lineage in PNG or JPEG format

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3031:


Commit 27916dd49f854678b84bde8023aee6e47cbeb7ce in atlas's branch 
refs/heads/master from gutkaBinit
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=27916dd ]

ATLAS-3031: UI : Allow user to export the lineage in PNG formatt

Signed-off-by: Sarath Subramanian 


> UI : Allow user to export the lineage in PNG or JPEG format
> ---
>
> Key: ATLAS-3031
> URL: https://issues.apache.org/jira/browse/ATLAS-3031
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Binit Gutka
>Priority: Major
> Attachments: ATLAS-3031.patch
>
>




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

[jira] [Commented] (ATLAS-3031) UI : Allow user to export the lineage in PNG or JPEG format

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian commented on ATLAS-3031:
---

+1 for the patch. Thanks [~binitgutka].

> UI : Allow user to export the lineage in PNG or JPEG format
> ---
>
> Key: ATLAS-3031
> URL: https://issues.apache.org/jira/browse/ATLAS-3031
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Binit Gutka
>Priority: Major
> Attachments: ATLAS-3031.patch
>
>




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

Atlas Hive Hook Setting ClassLoader Issue

[Shawn Weeks]

Hi, I'm tracking down an issue with Hive ClassLoading for UDFs and I discovered 
that after calling the Atlas Hook Hive's current thread had a different class 
loader than before the hook. I'm looking in AtlasPluginClassLoader.java at the 
deactivate method and it looks like it's setting the threads class loader back 
to savedClassLoader.getParent() instead of savedClassLoader. Why is this? I'm 
pretty sure it's causing Hive to then add jars to the wrong classloader.

Thanks
Shawn Weeks

[jira] [Created] (ATLAS-3086) Regression : Atlas Hive Hook doesn't capture insert into table values() queries

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3086:


 Summary: Regression : Atlas Hive Hook doesn't capture insert into 
table values() queries
 Key: ATLAS-3086
 URL: https://issues.apache.org/jira/browse/ATLAS-3086
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
 Fix For: 2.0.0


Atlas Hive Hook doesn't capture the query "insert into table values()" . This 
is a regression as this event was captured in 0.8

Other queries like 
"from table1 a insert overwrite table bkp_table select a.id",
"insert into tableB select c1,c2 from tableA" , information is captured and 
lineage is created in 1.0



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

Re: Review Request 70236: ATLAS-3077: Handle java patches in patch framework

[Xinran Tinney]

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




intg/src/main/java/org/apache/atlas/model/patches/AtlasPatch.java
Line 53 (original), 53 (patched)


Is there any reason the order is changed?



repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
Lines 52 (patched)


nit: attributes -> attribute



repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
Lines 149 (patched)


nit: do we have to indent here


- Xinran Tinney


On March 18, 2019, 11:15 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70236/
> ---
> 
> (Updated March 18, 2019, 11:15 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Kapildeo Nayak, madhan, Nikhil 
> Bonte, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-3077
> https://issues.apache.org/jira/browse/ATLAS-3077
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> We have Atlas typedef patches available to update out of box type 
> definitions. This JIRA will introduce a new java patch framework to handle 
> changes to the graph database not specific to type changes.
> 
> For e.g. In case of migration, to add/update property keys in vertices - java 
> patch framework can be used, which will be run at the atlas startup time 
> during bootstrap.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/model/patches/AtlasPatch.java cdf2441d2 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  4805435c7 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/AtlasJavaPatchHandler.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/PatchContext.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatchHandler.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
>  337a6db6c 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasGraphUtilsV2.java
>  5827dad52 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> 01bdcf7e2 
> 
> 
> Diff: https://reviews.apache.org/r/70236/diff/1/
> 
> 
> Testing
> ---
> 
> Verified with migrated data that patch was applied cleanly
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

[jira] [Commented] (ATLAS-2945) UI - If a Term is assigned to an Category then to user is able to assign the same term again

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-2945:


Commit f92e06cda0833d5840015a18ec8f5c5f30b582a3 in atlas's branch 
refs/heads/master from gutkaBinit
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f92e06c ]

ATLAS-2945 UI - If a Term is assigned to an Category then to user is able to 
assign the same term again

Signed-off-by: nixonrodrigues 


> UI - If a Term is assigned to an Category then to user is able to assign the 
> same term again
> 
>
> Key: ATLAS-2945
> URL: https://issues.apache.org/jira/browse/ATLAS-2945
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Tejas Rawool
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2945.patch, ATLAS-2945_1.patch, SS1.png, SS2.png
>
>




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

[jira] [Created] (ATLAS-3085) Capturing Hive DMLs through HiveHook can expose sensitive data

[Chiran Ravani (JIRA)]

Chiran Ravani created ATLAS-3085:


 Summary: Capturing Hive DMLs through HiveHook can expose sensitive 
data
 Key: ATLAS-3085
 URL: https://issues.apache.org/jira/browse/ATLAS-3085
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.1.0
Reporter: Chiran Ravani


When Atlas HiveHook is enabled, it captures DML statements which can have 
sensitive data and the entity is created under type hive_process with the name 
as DML Statement itself.

Steps to reproduce:
{code:java}
CREATE TABLE test_hive_atlas
(SSIN int,
name string)
CLUSTERED BY (SSIN) INTO 3 BUCKETS STORED AS ORC 
TBLPROPERTIES('transactional'='true');

set hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager;
set hive.support.concurrency=true;
set hive.enforce.bucketing=true;
set hive.exec.dynamic.partition.mode=nonstrict;
set hive.txn.strict.locking.mode=true;

insert into test_hive_atlas(12398431, 'Name1');
insert into test_hive_atlas values(342198432, 'Name2');{code}
 

After running the above statements, an entity is created in atlas under 
hive_process with its name as insert statement, a configuration to disable DMLs 
for HiveHook will help.



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

[jira] [Commented] (ATLAS-2945) UI - If a Term is assigned to an Category then to user is able to assign the same term again

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues commented on ATLAS-2945:


Thanks [~binitgutka] for improvement, fix looks good.

> UI - If a Term is assigned to an Category then to user is able to assign the 
> same term again
> 
>
> Key: ATLAS-2945
> URL: https://issues.apache.org/jira/browse/ATLAS-2945
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Tejas Rawool
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2945.patch, ATLAS-2945_1.patch, SS1.png, SS2.png
>
>




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

[jira] [Updated] (ATLAS-2945) UI - If a Term is assigned to an Category then to user is able to assign the same term again

[Binit Gutka (JIRA)]

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

Binit Gutka updated ATLAS-2945:
---
Attachment: ATLAS-2945_1.patch

> UI - If a Term is assigned to an Category then to user is able to assign the 
> same term again
> 
>
> Key: ATLAS-2945
> URL: https://issues.apache.org/jira/browse/ATLAS-2945
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Tejas Rawool
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2945.patch, ATLAS-2945_1.patch, SS1.png, SS2.png
>
>




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

[jira] [Updated] (ATLAS-2945) UI - If a Term is assigned to an Category then to user is able to assign the same term again

[Binit Gutka (JIRA)]

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

Binit Gutka updated ATLAS-2945:
---
Attachment: (was: ATLAS-2945_1.patch)

> UI - If a Term is assigned to an Category then to user is able to assign the 
> same term again
> 
>
> Key: ATLAS-2945
> URL: https://issues.apache.org/jira/browse/ATLAS-2945
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Tejas Rawool
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2945.patch, SS1.png, SS2.png
>
>




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

[jira] [Commented] (ATLAS-3083) Disable SSLAndKerberosTest & SSLTest etc Unitcases on Master

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3083:


Commit 4c7c911c3d64ede6bbb2d8cafb9cbc50c399cbc1 in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4c7c911 ]

ATLAS-3083 :- Disable SSLAndKerberosTest & SSLTest etc Unitcases

Change-Id: I55f6ea20b0643821996721d3a7370a44729d5ea2


> Disable SSLAndKerberosTest & SSLTest etc Unitcases on Master
> 
>
> Key: ATLAS-3083
> URL: https://issues.apache.org/jira/browse/ATLAS-3083
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-ATLAS-3083-Disable-SSLAndKerberosTest-SSLTest-etc-Un.patch
>
>
> SSLAndKerberosTest & SSLTest etc Unitcases on Master are failing due to 
> version change for hadoop3 in ATLAS-2987.
> This testcases need to be revisited with proper configs for hadoop3



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

[jira] [Updated] (ATLAS-2458) RelationshipApi Delete doesnt remove relationshipAttributes from entity

[Kapildeo Nayak (JIRA)]

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

Kapildeo Nayak updated ATLAS-2458:
--
Attachment: ATLAS-2458.patch

> RelationshipApi Delete doesnt remove relationshipAttributes from entity
> ---
>
> Key: ATLAS-2458
> URL: https://issues.apache.org/jira/browse/ATLAS-2458
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Brandon Kirchner
>Assignee: Kapildeo Nayak
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2458.patch
>
>
> When I create a Process and DataSet entity, and create a 
> process_dataset_outputs relationship between the two, when I delete the 
> relationship, the relationshipAttributes are not removed from the Process or 
> DataSet entities. full reproduction steps and output are below --
>  
> step 1 -- create dataset and process (through UI)
> step 2 -- create relationship
> http post http://localhost:21000/api/atlas/v2/relationship
> PAYLOAD
> {
>  "end1" : {
>  "guid" : "d456dc93-8832-4a36-8ae0-071946c653fc"
>  },
>  "end2" : {
>  "guid" : "247bc2d1-de27-4c50-a35b-b62350dc7979"
>  },
>  "typeName":"process_dataset_outputs"
> }
> RESPONSE
> {
>  "createTime": 1519335073389,
>  "createdBy": "admin",
>  "end1": {
>  "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
>  "typeName": "Process"
>  },
>  "end2": {
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  "typeName": "DataSet"
>  },
>  "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "label": "__Process.outputs",
>  "propagateTags": "ONE_TO_TWO",
>  "status": "ACTIVE",
>  "typeName": "process_dataset_outputs",
>  "updateTime": 1519335073389,
>  "updatedBy": "admin",
>  "version": 0
> }
> step 3 -- verify relationship on entities
> http get 
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
>  "entity": {
>  "attributes": {
>  "description": null,
>  "name": "dataset",
>  "owner": null,
>  "qualifiedName": "dataset"
>  },
>  "classifications": [],
>  "createTime": 1519334042139,
>  "createdBy": "admin",
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  "relationshipAttributes": {
>  "sinkFromProcesses": [
>  {
>  "displayText": "process",
>  "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
>  "relationshipAttributes": {
>  "typeName": "process_dataset_outputs"
>  },
>  "relationshipGuid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "typeName": "Process"
>  }
>  ],
>  "sourceToProcesses": []
>  },
>  "status": "ACTIVE",
>  "typeName": "DataSet",
>  "updateTime": 1519334042139,
>  "updatedBy": "admin",
>  "version": 0
>  },
>  "referredEntities": {}
> }
> http get 
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
>  "entity": {
>  "attributes": {
>  "description": null,
>  "name": "dataset",
>  "owner": null,
>  "qualifiedName": "dataset"
>  },
>  "classifications": [],
>  "createTime": 1519334042139,
>  "createdBy": "admin",
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  "relationshipAttributes": {
>  "sinkFromProcesses": [
>  {
>  "displayText": "process",
>  "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
>  "relationshipAttributes": {
>  "typeName": "process_dataset_outputs"
>  },
>  "relationshipGuid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "typeName": "Process"
>  }
>  ],
>  "sourceToProcesses": []
>  },
>  "status": "ACTIVE",
>  "typeName": "DataSet",
>  "updateTime": 1519334042139,
>  "updatedBy": "admin",
>  "version": 0
>  },
>  "referredEntities": {}
> }
> step 4 -- delete relationship
> http delete 
> http://localhost:21000/api/atlas/v2/relationship/guid/bb9dfa43-c193-4cbb-9472-6b9421f43701
> HTTP/1.1 204 No Content
> step 5 -- verify deletion
> http get 
> http://localhost:21000/api/atlas/v2/relationship/guid/bb9dfa43-c193-4cbb-9472-6b9421f43701
> HTTP/1.1 200 OK
> {
>  "createTime": 1519334256264,
>  "createdBy": "admin",
>  "end1": {
>  "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "typeName": "Process"
>  },
>  "end2": {
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  "typeName": "DataSet"
>  },
>  "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "label": "__Process.outputs",
>  "propagateTags": "ONE_TO_TWO",
>  "status": "DELETED",
>  "typeName": "process_dataset_outputs",
>  "updateTime": 1519334383683,
>  "updatedBy": "admin",
>  "version": 0
> }
> step 6 -- verify relationship removed from entities (FAILS)
> http get 
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
>  "entity": {
>  "attributes": {
>  "description": null,
>  "name": "dataset",
>  "owner": null,
>  "qualifiedName": "dataset"
>  },
>  "classifications": [],
>  "createTime": 1519334042139,
>  "createdBy": "admin",
>  "guid": 

[jira] [Assigned] (ATLAS-2458) RelationshipApi Delete doesnt remove relationshipAttributes from entity

[Kapildeo Nayak (JIRA)]

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

Kapildeo Nayak reassigned ATLAS-2458:
-

Assignee: Kapildeo Nayak

> RelationshipApi Delete doesnt remove relationshipAttributes from entity
> ---
>
> Key: ATLAS-2458
> URL: https://issues.apache.org/jira/browse/ATLAS-2458
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Brandon Kirchner
>Assignee: Kapildeo Nayak
>Priority: Major
> Fix For: 1.0.0
>
>
> When I create a Process and DataSet entity, and create a 
> process_dataset_outputs relationship between the two, when I delete the 
> relationship, the relationshipAttributes are not removed from the Process or 
> DataSet entities. full reproduction steps and output are below --
>  
> step 1 -- create dataset and process (through UI)
> step 2 -- create relationship
> http post http://localhost:21000/api/atlas/v2/relationship
> PAYLOAD
> {
>  "end1" : {
>  "guid" : "d456dc93-8832-4a36-8ae0-071946c653fc"
>  },
>  "end2" : {
>  "guid" : "247bc2d1-de27-4c50-a35b-b62350dc7979"
>  },
>  "typeName":"process_dataset_outputs"
> }
> RESPONSE
> {
>  "createTime": 1519335073389,
>  "createdBy": "admin",
>  "end1": {
>  "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
>  "typeName": "Process"
>  },
>  "end2": {
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  "typeName": "DataSet"
>  },
>  "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "label": "__Process.outputs",
>  "propagateTags": "ONE_TO_TWO",
>  "status": "ACTIVE",
>  "typeName": "process_dataset_outputs",
>  "updateTime": 1519335073389,
>  "updatedBy": "admin",
>  "version": 0
> }
> step 3 -- verify relationship on entities
> http get 
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
>  "entity": {
>  "attributes": {
>  "description": null,
>  "name": "dataset",
>  "owner": null,
>  "qualifiedName": "dataset"
>  },
>  "classifications": [],
>  "createTime": 1519334042139,
>  "createdBy": "admin",
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  "relationshipAttributes": {
>  "sinkFromProcesses": [
>  {
>  "displayText": "process",
>  "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
>  "relationshipAttributes": {
>  "typeName": "process_dataset_outputs"
>  },
>  "relationshipGuid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "typeName": "Process"
>  }
>  ],
>  "sourceToProcesses": []
>  },
>  "status": "ACTIVE",
>  "typeName": "DataSet",
>  "updateTime": 1519334042139,
>  "updatedBy": "admin",
>  "version": 0
>  },
>  "referredEntities": {}
> }
> http get 
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
>  "entity": {
>  "attributes": {
>  "description": null,
>  "name": "dataset",
>  "owner": null,
>  "qualifiedName": "dataset"
>  },
>  "classifications": [],
>  "createTime": 1519334042139,
>  "createdBy": "admin",
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  "relationshipAttributes": {
>  "sinkFromProcesses": [
>  {
>  "displayText": "process",
>  "guid": "d456dc93-8832-4a36-8ae0-071946c653fc",
>  "relationshipAttributes": {
>  "typeName": "process_dataset_outputs"
>  },
>  "relationshipGuid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "typeName": "Process"
>  }
>  ],
>  "sourceToProcesses": []
>  },
>  "status": "ACTIVE",
>  "typeName": "DataSet",
>  "updateTime": 1519334042139,
>  "updatedBy": "admin",
>  "version": 0
>  },
>  "referredEntities": {}
> }
> step 4 -- delete relationship
> http delete 
> http://localhost:21000/api/atlas/v2/relationship/guid/bb9dfa43-c193-4cbb-9472-6b9421f43701
> HTTP/1.1 204 No Content
> step 5 -- verify deletion
> http get 
> http://localhost:21000/api/atlas/v2/relationship/guid/bb9dfa43-c193-4cbb-9472-6b9421f43701
> HTTP/1.1 200 OK
> {
>  "createTime": 1519334256264,
>  "createdBy": "admin",
>  "end1": {
>  "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "typeName": "Process"
>  },
>  "end2": {
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  "typeName": "DataSet"
>  },
>  "guid": "bb9dfa43-c193-4cbb-9472-6b9421f43701",
>  "label": "__Process.outputs",
>  "propagateTags": "ONE_TO_TWO",
>  "status": "DELETED",
>  "typeName": "process_dataset_outputs",
>  "updateTime": 1519334383683,
>  "updatedBy": "admin",
>  "version": 0
> }
> step 6 -- verify relationship removed from entities (FAILS)
> http get 
> http://localhost:21000/api/atlas/v2/entity/guid/247bc2d1-de27-4c50-a35b-b62350dc7979
> HTTP/1.1 200 OK
> {
>  "entity": {
>  "attributes": {
>  "description": null,
>  "name": "dataset",
>  "owner": null,
>  "qualifiedName": "dataset"
>  },
>  "classifications": [],
>  "createTime": 1519334042139,
>  "createdBy": "admin",
>  "guid": "247bc2d1-de27-4c50-a35b-b62350dc7979",
>  

[jira] [Updated] (ATLAS-3081) Expose Gremlin Search API

[Ayush Nigam (JIRA)]

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

Ayush Nigam updated ATLAS-3081:
---
Priority: Minor  (was: Major)

> Expose Gremlin Search API
> -
>
> Key: ATLAS-3081
> URL: https://issues.apache.org/jira/browse/ATLAS-3081
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Ayush Nigam
>Assignee: Ayush Nigam
>Priority: Minor
> Attachments: ATLAS_3081.patch
>
>
> Expose Gremlin Search API to solve more complex usecases.



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

[jira] [Updated] (ATLAS-3083) Disable SSLAndKerberosTest & SSLTest etc Unitcases on Master

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-3083:
---
Attachment: 0001-ATLAS-3083-Disable-SSLAndKerberosTest-SSLTest-etc-Un.patch

> Disable SSLAndKerberosTest & SSLTest etc Unitcases on Master
> 
>
> Key: ATLAS-3083
> URL: https://issues.apache.org/jira/browse/ATLAS-3083
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-ATLAS-3083-Disable-SSLAndKerberosTest-SSLTest-etc-Un.patch
>
>
> SSLAndKerberosTest & SSLTest etc Unitcases on Master are failing due to 
> version change for hadoop3 in ATLAS-2987.
> This testcases need to be revisited with proper configs for hadoop3



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

[jira] [Assigned] (ATLAS-3084) Adding default value to the relationship

[Kirankumar D G (JIRA)]

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

Kirankumar D G reassigned ATLAS-3084:
-

Assignee: Kirankumar D G

> Adding default value to the relationship 
> -
>
> Key: ATLAS-3084
> URL: https://issues.apache.org/jira/browse/ATLAS-3084
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Kirankumar D G
>Assignee: Kirankumar D G
>Priority: Minor
>
> Adding default value to the relationship 



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

[jira] [Reopened] (ATLAS-2945) UI - If a Term is assigned to an Category then to user is able to assign the same term again

[Binit Gutka (JIRA)]

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

Binit Gutka reopened ATLAS-2945:


> UI - If a Term is assigned to an Category then to user is able to assign the 
> same term again
> 
>
> Key: ATLAS-2945
> URL: https://issues.apache.org/jira/browse/ATLAS-2945
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Tejas Rawool
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2945.patch, SS1.png, SS2.png
>
>




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

Re: would like to be a contributor

[Madhan Neethiraj]

Kiran,

 

Thanks for your interest in contributing to Apache Atlas. You have been added 
as a contributor. Welcome to Apache Atlas community!

 

Regards,

Madhan

 

From: kirankumar D G 
Date: Wednesday, March 20, 2019 at 12:37 AM
To: Madhan Neethiraj 
Cc: "dev@atlas.apache.org" 
Subject: Re: would like to be a contributor

 

my jira id: kirankumardg

 

On Wed, Mar 20, 2019 at 1:03 PM kirankumar D G  wrote:

This is the my jira id. Please add me to contributor list. 

 

https://issues.apache.org/jira/browse/ATLAS-3084

 

Thanks

Kiran D G

 

On Wed, Mar 20, 2019 at 12:03 PM kirankumar D G  wrote:

Sure, I will do that. 

 

On Wed, Mar 20, 2019 at 11:59 AM Madhan Neethiraj  wrote:

Kiran,

Thank you for your interest in contributing to Apache Atlas. Can you please 
send your Apache JIRA id, so that I can add you as a contributor? If you don't 
have one yet, please signup for one at 
https://issues.apache.org/jira/secure/Signup!default.jspa.

Regards,
Madhan

On 3/19/19, 8:55 PM, "kirankumar D G" <

kirankuma...@gmail.com> wrote:

Hi,

I would like to be contributor to apache atlas. Please add me to the
contributor list.

Thanks
Kiran D G

[jira] [Assigned] (ATLAS-2945) UI - If a Term is assigned to an Category then to user is able to assign the same term again

[Binit Gutka (JIRA)]

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

Binit Gutka reassigned ATLAS-2945:
--

Assignee: Binit Gutka  (was: Abhishek Kadam)

> UI - If a Term is assigned to an Category then to user is able to assign the 
> same term again
> 
>
> Key: ATLAS-2945
> URL: https://issues.apache.org/jira/browse/ATLAS-2945
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Tejas Rawool
>Assignee: Binit Gutka
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-2945.patch, SS1.png, SS2.png
>
>




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

Re: would like to be a contributor

[kirankumar D G]

my jira id: kirankumardg

On Wed, Mar 20, 2019 at 1:03 PM kirankumar D G 
wrote:

> This is the my jira id. Please add me to contributor list.
>
> https://issues.apache.org/jira/browse/ATLAS-3084
>
> Thanks
> Kiran D G
>
> On Wed, Mar 20, 2019 at 12:03 PM kirankumar D G 
> wrote:
>
>> Sure, I will do that.
>>
>> On Wed, Mar 20, 2019 at 11:59 AM Madhan Neethiraj 
>> wrote:
>>
>>> Kiran,
>>>
>>> Thank you for your interest in contributing to Apache Atlas. Can you
>>> please send your Apache JIRA id, so that I can add you as a contributor? If
>>> you don't have one yet, please signup for one at
>>> https://issues.apache.org/jira/secure/Signup!default.jspa.
>>>
>>> Regards,
>>> Madhan
>>>
>>> On 3/19/19, 8:55 PM, "kirankumar D G" <
>>>
>>> kirankuma...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> I would like to be contributor to apache atlas. Please add me to the
>>> contributor list.
>>>
>>> Thanks
>>> Kiran D G
>>>
>>>
>>>
>>>

[jira] [Commented] (ATLAS-3070) Create patch framework to persist typedef patches applied to atlas

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3070:


Commit fa2c3e2cc6afc8d06a943a589502d0e1004cdd62 in atlas's branch 
refs/heads/master from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fa2c3e2 ]

ATLAS-3070: Create patch framework to persist typedef patches applied to atlas 
#2 fix getPatches() method


> Create patch framework to persist typedef patches applied to atlas
> --
>
> Key: ATLAS-3070
> URL: https://issues.apache.org/jira/browse/ATLAS-3070
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 1.1.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0
>
>
> In Atlas, we don't have a way to see all the type patches applied. The patch 
> framework will create a new vertex in the graph database and update its 
> application state. This will be useful when applying new patches and to make 
> sure not to apply applied patches again. A new REST API is also made 
> available to display all the list of patches and its application status.



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

Re: would like to be a contributor

[kirankumar D G]

This is the my jira id. Please add me to contributor list.

https://issues.apache.org/jira/browse/ATLAS-3084

Thanks
Kiran D G

On Wed, Mar 20, 2019 at 12:03 PM kirankumar D G 
wrote:

> Sure, I will do that.
>
> On Wed, Mar 20, 2019 at 11:59 AM Madhan Neethiraj 
> wrote:
>
>> Kiran,
>>
>> Thank you for your interest in contributing to Apache Atlas. Can you
>> please send your Apache JIRA id, so that I can add you as a contributor? If
>> you don't have one yet, please signup for one at
>> https://issues.apache.org/jira/secure/Signup!default.jspa.
>>
>> Regards,
>> Madhan
>>
>> On 3/19/19, 8:55 PM, "kirankumar D G" <
>>
>> kirankuma...@gmail.com> wrote:
>>
>> Hi,
>>
>> I would like to be contributor to apache atlas. Please add me to the
>> contributor list.
>>
>> Thanks
>> Kiran D G
>>
>>
>>
>>

[jira] [Created] (ATLAS-3084) Adding default value to the relationship

[Kirankumar D G (JIRA)]

Kirankumar D G created ATLAS-3084:
-

 Summary: Adding default value to the relationship 
 Key: ATLAS-3084
 URL: https://issues.apache.org/jira/browse/ATLAS-3084
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.1.0
Reporter: Kirankumar D G


Adding default value to the relationship 



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

Re: Atlas Contributor Request

[Madhan Neethiraj]

Umesh,

Thanks for your interest in contributing to Apache Atlas. You have been added 
as a contributor. Welcome to Apache Atlas community!

Regards,
Madhan

On 3/20/19, 12:02 AM, "Umesh S. Padashetty"  wrote:

Hi Atlas Team,

I am interested in contributing to Apache Atlas project, kindly add me as a
contributor.

My Jira id is umesh.padashetty

--
Thanks and Regards,
Umesh S. Padashetty

Atlas Contributor Request

[Umesh S. Padashetty]

Hi Atlas Team,

I am interested in contributing to Apache Atlas project, kindly add me as a
contributor.

My Jira id is umesh.padashetty

--
Thanks and Regards,
Umesh S. Padashetty

[jira] [Created] (ATLAS-3083) Disable SSLAndKerberosTest & SSLTest etc Unitcases on Master

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-3083:
--

 Summary: Disable SSLAndKerberosTest & SSLTest etc Unitcases on 
Master
 Key: ATLAS-3083
 URL: https://issues.apache.org/jira/browse/ATLAS-3083
 Project: Atlas
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: 2.0.0


SSLAndKerberosTest & SSLTest etc Unitcases on Master are failing due to version 
change for hadoop3 in ATLAS-2987.

This testcases need to be revisited with proper configs for hadoop3



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

[jira] [Assigned] (ATLAS-3001) AtlasClientV2.updateClassifications() throws a serialization error

[chaitali borole (JIRA)]

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

chaitali borole reassigned ATLAS-3001:
--

Assignee: chaitali borole

> AtlasClientV2.updateClassifications() throws a serialization error
> --
>
> Key: ATLAS-3001
> URL: https://issues.apache.org/jira/browse/ATLAS-3001
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Paul Khermouch
>Assignee: chaitali borole
>Priority: Major
>
> The REST API specifies that the updateClassifications Atlas REST endpoint 
> returns `204 No content` with an empty response body. However, the 
> AtlasClientV2.updateClassifications() endpoint attempts to deserialize the 
> response body into an AtlasClassifications object, which throws a 
> deserialization error.



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

Re: would like to be a contributor

[kirankumar D G]

Sure, I will do that.

On Wed, Mar 20, 2019 at 11:59 AM Madhan Neethiraj  wrote:

> Kiran,
>
> Thank you for your interest in contributing to Apache Atlas. Can you
> please send your Apache JIRA id, so that I can add you as a contributor? If
> you don't have one yet, please signup for one at
> https://issues.apache.org/jira/secure/Signup!default.jspa.
>
> Regards,
> Madhan
>
> On 3/19/19, 8:55 PM, "kirankumar D G" <
>
> kirankuma...@gmail.com> wrote:
>
> Hi,
>
> I would like to be contributor to apache atlas. Please add me to the
> contributor list.
>
> Thanks
> Kiran D G
>
>
>
>

Re: would like to be a contributor

[Madhan Neethiraj]

Kiran,

Thank you for your interest in contributing to Apache Atlas. Can you please 
send your Apache JIRA id, so that I can add you as a contributor? If you don't 
have one yet, please signup for one at 
https://issues.apache.org/jira/secure/Signup!default.jspa.

Regards,
Madhan

On 3/19/19, 8:55 PM, "kirankumar D G" <

kirankuma...@gmail.com> wrote:

Hi,

I would like to be contributor to apache atlas. Please add me to the
contributor list.

Thanks
Kiran D G

Re: Add me as a Contributor for Atlas

[Madhan Neethiraj]

Chaitali,

Thanks for your interest in contributing to Apache Atlas. You have been added 
as a contributor. Welcome to Apache Atlas community!

Regards,
Madhan



On 3/19/19, 11:23 PM, "Chaitali Borole" 
 wrote:

Hello,

I would like to be a contributor for Apache Atlas. My jira id is chaitali

Thanks,

Chaitali Borole.

Atlas - Elasticsearch custom analyzer issue

[Nallapati, Sreenivasulu]

Hi,

We are using Apache atlas with Elastic Search as a search engine.
Our users create entities with underscore (_) in its name or description (ex. 
ABC_XYZ).
As the janusgraph_fulutext_index created by janusgraph uses a the standard 
analyser which will not tokenize the words with underscore.

We tried, creating janusgraph_fulutext_index  with custom analyser and 
mappings. But when launching the atals, janusgraph also trying to add the 
mappings to the index. Because there is a custom analyser on the mappings that 
we created, janusgraph will fail to update the mappings.

Janusgraph will not create the index if already exists, but it doens’t have a 
mechanism to avoid mappings if already exists.

use-external-mappings
 – if we use this flag, we need to create all the three indexes 
(janusgraph_fulltext_index, janusgraph_edge_index, janusgraph_vertex_index)  
upfront and we don’t want to do this because janusgraph_vertex_index indexes 
are created based on the model that we post. The model may change over the time 
it will be a dependency on the model changes.

Is there any way that we can use the custom analyser   with a simple 
configurable way.




---
Regards,
Sreeni

Add me as a Contributor for Atlas

[Chaitali Borole]

Hello,

I would like to be a contributor for Apache Atlas. My jira id is chaitali

Thanks,

Chaitali Borole.

[jira] [Updated] (ATLAS-3079) Corrected Atlas advanced search invalid link and Updated broken links

[Umesh Padashetty (JIRA)]

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

Umesh Padashetty updated ATLAS-3079:

Description: 
On the Atlas homepage, on click of (?) next to Advanced toggle button, lists 
out a window. On click of "More sample queries and use-cases", it is taking the 
user to [http://atlas.apache.org/Search.html] which is throwing 404 error. This 
is because the page has moved to 
[http://atlas.apache.org/Search-Advanced.html.] 

Attached are the screenshots.

Also, update the links to [https://gitbox.apache.org/repos/asf?p=atlas.git] 
which were previously pointing to 
[https://git-wip-us.apache.org/repos/asf?p=atlas.git]

  was:
On the Atlas homepage, on click of (?) next to Advanced toggle button, lists 
out a window. On click of "More sample queries and use-cases", it is taking the 
user to [http://atlas.apache.org/Search.html] which is throwing 404 error. This 
is because the page has moved to 
[http://atlas.apache.org/Search-Advanced.html.] 

Attached are the screenshots.


> Corrected Atlas advanced search invalid link and Updated broken links
> -
>
> Key: ATLAS-3079
> URL: https://issues.apache.org/jira/browse/ATLAS-3079
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8.2, 1.1.0, 1.2.0, 2.0.0
>Reporter: Umesh Padashetty
>Priority: Trivial
> Attachments: ATLAS-3079-1.patch, ATLAS-3079.patch, Screenshot 
> 2019-03-18 at 6.28.05 PM.png, Screenshot 2019-03-18 at 6.28.42 PM.png
>
>
> On the Atlas homepage, on click of (?) next to Advanced toggle button, lists 
> out a window. On click of "More sample queries and use-cases", it is taking 
> the user to [http://atlas.apache.org/Search.html] which is throwing 404 
> error. This is because the page has moved to 
> [http://atlas.apache.org/Search-Advanced.html.] 
> Attached are the screenshots.
> Also, update the links to [https://gitbox.apache.org/repos/asf?p=atlas.git] 
> which were previously pointing to 
> [https://git-wip-us.apache.org/repos/asf?p=atlas.git]



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

[jira] [Updated] (ATLAS-3079) Corrected Atlas advanced search invalid link and Updated broken links

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-3079:
---
Summary: Corrected Atlas advanced search invalid link and Updated broken 
links  (was: Incorrect link of Advanced Search in Search Page )

> Corrected Atlas advanced search invalid link and Updated broken links
> -
>
> Key: ATLAS-3079
> URL: https://issues.apache.org/jira/browse/ATLAS-3079
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8.2, 1.1.0, 1.2.0, 2.0.0
>Reporter: Umesh Padashetty
>Priority: Trivial
> Attachments: ATLAS-3079-1.patch, ATLAS-3079.patch, Screenshot 
> 2019-03-18 at 6.28.05 PM.png, Screenshot 2019-03-18 at 6.28.42 PM.png
>
>
> On the Atlas homepage, on click of (?) next to Advanced toggle button, lists 
> out a window. On click of "More sample queries and use-cases", it is taking 
> the user to [http://atlas.apache.org/Search.html] which is throwing 404 
> error. This is because the page has moved to 
> [http://atlas.apache.org/Search-Advanced.html.] 
> Attached are the screenshots.



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

[jira] [Commented] (ATLAS-3079) Corrected Atlas advanced search invalid link and Updated broken links

[Keval Bhatt (JIRA)]

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

Keval Bhatt commented on ATLAS-3079:


Committed to the
Master: 74728b84da11370c8d975539a068d498c00fc3bd
branch-1.0: 57548ded725dda1eaefb9317fd2fb1e111a8b476

> Corrected Atlas advanced search invalid link and Updated broken links
> -
>
> Key: ATLAS-3079
> URL: https://issues.apache.org/jira/browse/ATLAS-3079
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8.2, 1.1.0, 1.2.0, 2.0.0
>Reporter: Umesh Padashetty
>Priority: Trivial
> Attachments: ATLAS-3079-1.patch, ATLAS-3079.patch, Screenshot 
> 2019-03-18 at 6.28.05 PM.png, Screenshot 2019-03-18 at 6.28.42 PM.png
>
>
> On the Atlas homepage, on click of (?) next to Advanced toggle button, lists 
> out a window. On click of "More sample queries and use-cases", it is taking 
> the user to [http://atlas.apache.org/Search.html] which is throwing 404 
> error. This is because the page has moved to 
> [http://atlas.apache.org/Search-Advanced.html.] 
> Attached are the screenshots.



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