[jira] [Created] (ATLAS-3236) Relationship traversal through DSL search queries

[Kirankumar D G (JIRA)]

Kirankumar D G created ATLAS-3236:
-

 Summary: Relationship traversal through DSL search queries
 Key: ATLAS-3236
 URL: https://issues.apache.org/jira/browse/ATLAS-3236
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Affects Versions: trunk
Reporter: Kirankumar D G
Assignee: Kirankumar D G


Enhance Atlas DSL grammar to support relationship traversal.

 

Examples:

from hive_db as db where db.name="hive_db_g_test_2" hasr hive_table as tb where 
tb.name="hive_table_g_test_2" hasr hive_column as c where  
c.name="hive_column_g_test_2" and c is realm

 

query should be transformed into gremlin query as below

g.V().has('__typeName', 'hive_db').as('db').has('Asset.name', 
eq("hive_db_g_test_2")).bothE().bothV().has('__typeName','hive_table').as('tb').has('Asset.name',
 
eq("hive_table_g_test_2")).bothE().bothV().has('__typeName','hive_column').as('c').and(__.has('Asset.name',
 eq("hive_column_g_test_2")),__.outE('classifiedAs').has('__name', 
within('realm')).outV()).dedup().limit(25).toList(

 



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

[jira] [Created] (ATLAS-3235) Change the display name of hive process and hive process execution

[Aadarsh Jajodia (JIRA)]

Aadarsh Jajodia created ATLAS-3235:
--

 Summary: Change the display name of hive process and hive process 
execution
 Key: ATLAS-3235
 URL: https://issues.apache.org/jira/browse/ATLAS-3235
 Project: Atlas
  Issue Type: Improvement
Reporter: Aadarsh Jajodia
Assignee: Aadarsh Jajodia


Currently the display name of a process and a process execution shows the query 
text. This needs to change because the query text can become too large. Either 
the qualifiedName or some other text needs to be shown for the display name of 
these



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

[jira] [Commented] (ATLAS-3230) Change Impala Hook API Names

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3230:


Commit 5196fd7122d09ccc3b0b65fb7bd0aab99379bf76 in atlas's branch 
refs/heads/master from lina.li
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5196fd7 ]

ATLAS-3230: Change Impala Hook API Names

Signed-off-by: Sarath Subramanian 


> Change Impala Hook API Names
> 
>
> Key: ATLAS-3230
> URL: https://issues.apache.org/jira/browse/ATLAS-3230
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Reporter: Na Li
>Assignee: Na Li
>Priority: Major
> Attachments: ATLAS-3230.002.patch
>
>
> Impala has made the following changes:
> 1) "createTime" to "tableCreateTime"
> 2) "PostQueryHookContext" to "QueryCompleteContext"
> 3) "QueryExecHook" to "QueryEventHook"
> Atlas needs to make corresponding changes to keep end-to-end work.



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

Re: Review Request 70708: ATLAS-3185: Create process execution for Impala integration

[Aadarsh Jajodia]

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


Fix it, then Ship it!




Overall looks good to me. Some minor comments.


addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
Lines 561-562 (patched)


Maybe use long for both?



addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
Lines 120 (patched)


Change to processExecution != null



addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
Lines 201-205 (patched)


Can we also add a unit test which produces more than one execution?


- Aadarsh Jajodia


On May 23, 2019, 9:11 p.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70708/
> ---
> 
> (Updated May 23, 2019, 9:11 p.m.)
> 
> 
> Review request for atlas, Aadarsh Jajodia, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-3133 adds a new feature to track metadata for different executions of 
> the same process in Atlas. Need to add this in Impala integration
> 
> 
> Diffs
> -
> 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/AtlasImpalaHookContext.java
>  88faace 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
>  232a569 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
>  63c5f87 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
>  0dc520c 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageITBase.java
>  0138d88 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java
>  033a518 
>   
> addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java
>  86801e3 
> 
> 
> Diff: https://reviews.apache.org/r/70708/diff/1/
> 
> 
> Testing
> ---
> 
> Integration tests
> 
> 
> Thanks,
> 
> Na Li
> 
>

Re: Review Request 70710: ATLAS-3230: Change Impala Hook API Names

[Sarath Subramanian]

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


Ship it!




Ship It!

- Sarath Subramanian


On May 24, 2019, 10:25 a.m., Na Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70710/
> ---
> 
> (Updated May 24, 2019, 10:25 a.m.)
> 
> 
> Review request for atlas and Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Impala has made the following changes:
> 
> 1) "createTime" to "tableCreateTime"
> 2) "PostQueryHookContext" to "QueryCompleteContext"
> 3) "QueryExecHook" to "QueryEventHook"
> 
> Atlas needs to make corresponding changes to keep end-to-end work.
> 
> 
> Diffs
> -
> 
>   
> addons/impala-bridge-shim/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
>  b796f37 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaHook.java
>  2afb4eb 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
>  63c5f87 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
>  0dc520c 
>   
> addons/impala-bridge/src/main/java/org/apache/atlas/impala/model/LineageVertexMetadata.java
>  0bd236d 
>   addons/impala-bridge/src/test/resources/impalaAlterViewAsSelect.json 
> f8de7e3 
>   addons/impala-bridge/src/test/resources/impalaCreateTableAsSelect.json 
> b6ac516 
>   addons/impala-bridge/src/test/resources/impalaCreateView.json ffdc658 
>   addons/impala-bridge/src/test/resources/impalaInsertIntoAsSelect.json 
> 140eced 
>   
> addons/impala-hook-api/src/main/java/org/apache/impala/hooks/PostQueryHookContext.java
>  c8a5b64 
>   
> addons/impala-hook-api/src/main/java/org/apache/impala/hooks/QueryCompleteContext.java
>  PRE-CREATION 
>   
> addons/impala-hook-api/src/main/java/org/apache/impala/hooks/QueryEventHook.java
>  PRE-CREATION 
>   
> addons/impala-hook-api/src/main/java/org/apache/impala/hooks/QueryExecHook.java
>  a7d84d4 
> 
> 
> Diff: https://reviews.apache.org/r/70710/diff/3/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Na Li
> 
>

[jira] [Commented] (ATLAS-3230) Change Impala Hook API Names

[Na Li (JIRA)]

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

Na Li commented on ATLAS-3230:
--

pre-commit test succeeded at 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1137/console

> Change Impala Hook API Names
> 
>
> Key: ATLAS-3230
> URL: https://issues.apache.org/jira/browse/ATLAS-3230
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Reporter: Na Li
>Assignee: Na Li
>Priority: Major
> Attachments: ATLAS-3230.002.patch
>
>
> Impala has made the following changes:
> 1) "createTime" to "tableCreateTime"
> 2) "PostQueryHookContext" to "QueryCompleteContext"
> 3) "QueryExecHook" to "QueryEventHook"
> Atlas needs to make corresponding changes to keep end-to-end work.



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

[jira] [Updated] (ATLAS-3227) Bulk delete does not delete the indexes properly

[Diego Marino Monetti (JIRA)]

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

Diego Marino Monetti updated ATLAS-3227:

Attachment: ATLAS-3227.patch

> Bulk delete does not delete the indexes properly
> 
>
> Key: ATLAS-3227
> URL: https://issues.apache.org/jira/browse/ATLAS-3227
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.0.0
>
> Attachments: ATLAS-3227.patch, application-with-patch.log, 
> application-without-patch.log, bulkCreateType, bulkDeleteType, 
> sample_type.json
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the Bulk Delete, first clears the cache and then does physical 
> deletion from Janus of the required types. At the end of this operation it 
> cycles through the attributes of the deleted types and for those attributes 
> for which it is possible to have indexes, built-ins, enums and structs, marks 
> the indexes as deleted. Since for each attribute the routine goes back to the 
> type of attribute using the typeRegistry, that is the cache, if this 
> attribute is a custom type the attribute was deleted before and the bulk 
> delete partially fails.
> In particular, for each attribute in which this error does not occur, for 
> example because built-in type, a label delete is added to the property key 
> with the number of occurrences with which this property key is present in the 
> store. Something like property_key_deleted_0. In fact, if you try to reload 
> the same types and re-delete,  the property keys are now marked as 
> property_key_deleted_1.
> If, however, for the aforementioned reason the search for the type in the 
> cache fails the property key is not marked and remains fully active, which, 
> from what I can understand at this level of my knowledge, generates at least 
> some MEMORY LEAKs.
> If I reload the types with the same entities and attributes it seems to be 
> all right, but if I change some attributes, in my opinion, the result is 
> unpredictable.
> This path tested on version 2.0 and SNAPSHOT 3.0 would resolve this issue.
> In attachment there is a small example that shows this behavior with and 
> without this patch



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

[jira] [Commented] (ATLAS-3234) Add option in Precommit-Atlas to build and run tests on git pull request

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry commented on ATLAS-3234:


+1 for the patch. 

> Add option in Precommit-Atlas to build and run tests on git pull request
> 
>
> Key: ATLAS-3234
> URL: https://issues.apache.org/jira/browse/ATLAS-3234
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3234.001.patch
>
>
> [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test]
> Add option to provide git pull request id to build and run tests on git pull 
> requests.



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

[jira] [Updated] (ATLAS-3234) Add option in Precommit-Atlas to build and run tests on git pull request

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian updated ATLAS-3234:
--
Attachment: ATLAS-3234.001.patch

> Add option in Precommit-Atlas to build and run tests on git pull request
> 
>
> Key: ATLAS-3234
> URL: https://issues.apache.org/jira/browse/ATLAS-3234
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3234.001.patch
>
>
> [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test]
> Add option to provide git pull request id to build and run tests on git pull 
> requests.



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

[jira] [Created] (ATLAS-3234) Add option in Precommit-Atlas to build and run tests on git pull request

[Sarath Subramanian (JIRA)]

Sarath Subramanian created ATLAS-3234:
-

 Summary: Add option in Precommit-Atlas to build and run tests on 
git pull request
 Key: ATLAS-3234
 URL: https://issues.apache.org/jira/browse/ATLAS-3234
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 2.0.0, trunk
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: trunk


[https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test]

Add option to provide git pull request id to build and run tests on git pull 
requests.



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

[jira] [Closed] (ATLAS-3098) Missing getTypesDef with AtlasRelationshipDef param in AtlasTypeUtil.

[Diego Marino Monetti (JIRA)]

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

Diego Marino Monetti closed ATLAS-3098.
---

> Missing getTypesDef with AtlasRelationshipDef param in AtlasTypeUtil.
> -
>
> Key: ATLAS-3098
> URL: https://issues.apache.org/jira/browse/ATLAS-3098
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 2.0.0
> Environment: all OS
>Reporter: Diego Marino Monetti
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In AtlasTypesDef.java Atlas team introduced the AtlasTypesDef .ctor with the 
> List parameter but in AtlasTypeUtil the getTypesDef 
> method does not accept 5 parameters.
> I think we can use directly the AtlasTypesDef contructors so this Bug in my 
> opinion is a minor issue. Any way I submitted the pull-request.



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

[jira] [Commented] (ATLAS-3201) getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or invalid

[Diego Marino Monetti (JIRA)]

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

Diego Marino Monetti commented on ATLAS-3201:
-

Did it, Thx !

>  getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or 
> invalid
> ---
>
> Key: ATLAS-3201
> URL: https://issues.apache.org/jira/browse/ATLAS-3201
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0, 1.2.0, 2.0.0
> Environment: All os
>Reporter: Diego Marino Monetti
>Priority: Major
>  Labels: ready-to-commit
> Fix For: 1.2.0, trunk
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The BUG was fixed



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

[jira] [Commented] (ATLAS-2779) Create Hive Metastore Event listener to push table changes to Atlas.

[Aadarsh Jajodia (JIRA)]

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

Aadarsh Jajodia commented on ATLAS-2779:


This is duplicate of ATLAS-3148 which is resolved. Hence closing this one

> Create Hive Metastore Event listener to push table changes to Atlas.
> 
>
> Key: ATLAS-2779
> URL: https://issues.apache.org/jira/browse/ATLAS-2779
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 1.0.0-alpha
>Reporter: Tiffany Nguyen
>Priority: Major
> Fix For: 1.0.0-alpha
>
>
> Create Hive Metastore Event listener to push table changes to Atlas. This 
> will help push changes done via SparkSQL which does not go through hivehook 
> to reflect in Atlas.
> Furthermore, this will eliminate the need to set hook on the client side to 
> capture DDL. For example, using hive CLI (by typing hive at command line) 
> would require changes in hive-site.xml on the client side to include hook 
> property (hive.exec.post.hooks). The benefit of no change needed on client 
> side is amplified in environment where there are hundreds of clients.



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

Re: Review Request 70710: ATLAS-3230: Change Impala Hook API Names

[Na Li via Review Board]

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

(Updated May 24, 2019, 5:25 p.m.)


Review request for atlas and Sarath Subramanian.


Repository: atlas


Description
---

Impala has made the following changes:

1) "createTime" to "tableCreateTime"
2) "PostQueryHookContext" to "QueryCompleteContext"
3) "QueryExecHook" to "QueryEventHook"

Atlas needs to make corresponding changes to keep end-to-end work.


Diffs (updated)
-

  
addons/impala-bridge-shim/src/main/java/org/apache/atlas/impala/hook/ImpalaLineageHook.java
 b796f37 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/ImpalaHook.java 
2afb4eb 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java
 63c5f87 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/CreateImpalaProcess.java
 0dc520c 
  
addons/impala-bridge/src/main/java/org/apache/atlas/impala/model/LineageVertexMetadata.java
 0bd236d 
  addons/impala-bridge/src/test/resources/impalaAlterViewAsSelect.json f8de7e3 
  addons/impala-bridge/src/test/resources/impalaCreateTableAsSelect.json 
b6ac516 
  addons/impala-bridge/src/test/resources/impalaCreateView.json ffdc658 
  addons/impala-bridge/src/test/resources/impalaInsertIntoAsSelect.json 140eced 
  
addons/impala-hook-api/src/main/java/org/apache/impala/hooks/PostQueryHookContext.java
 c8a5b64 
  
addons/impala-hook-api/src/main/java/org/apache/impala/hooks/QueryCompleteContext.java
 PRE-CREATION 
  
addons/impala-hook-api/src/main/java/org/apache/impala/hooks/QueryEventHook.java
 PRE-CREATION 
  
addons/impala-hook-api/src/main/java/org/apache/impala/hooks/QueryExecHook.java 
a7d84d4 


Diff: https://reviews.apache.org/r/70710/diff/3/

Changes: https://reviews.apache.org/r/70710/diff/2-3/


Testing
---


Thanks,

Na Li

[jira] [Resolved] (ATLAS-3201) getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or invalid

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues resolved ATLAS-3201.

   Resolution: Fixed
Fix Version/s: (was: 2.0.0)
   trunk
   1.2.0

>  getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or 
> invalid
> ---
>
> Key: ATLAS-3201
> URL: https://issues.apache.org/jira/browse/ATLAS-3201
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0, 1.2.0, 2.0.0
> Environment: All os
>Reporter: Diego Marino Monetti
>Priority: Major
>  Labels: ready-to-commit
> Fix For: 1.2.0, trunk
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The BUG was fixed



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

[jira] [Commented] (ATLAS-3201) getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or invalid

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues commented on ATLAS-3201:


[~Zep] Thanks for the patch. I have committed to master and branch1.0.

Please send email to dev@atlas.apache.org for Adding you as a contributor in 
Atlas project, so that this issue can linked to your account.

>  getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or 
> invalid
> ---
>
> Key: ATLAS-3201
> URL: https://issues.apache.org/jira/browse/ATLAS-3201
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0, 1.2.0, 2.0.0
> Environment: All os
>Reporter: Diego Marino Monetti
>Priority: Major
>  Labels: ready-to-commit
> Fix For: 2.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The BUG was fixed



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

[GitHub] [atlas] ZepHakase22 closed pull request #49: ATLAS-3180:New Bulk retrieval API with servicetype parameter

[GitBox]

ZepHakase22 closed pull request #49: ATLAS-3180:New Bulk retrieval API with 
servicetype parameter
URL: https://github.com/apache/atlas/pull/49
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [atlas] ZepHakase22 closed pull request #51: ATLAS-3201: getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or invalid

[GitBox]

ZepHakase22 closed pull request #51: ATLAS-3201: getByGuid in AtlasTypeRegistry 
doesn't raise exception if guid null or invalid
URL: https://github.com/apache/atlas/pull/51
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (ATLAS-3233) Relationships, Export & Import : Issue with ACTIVE and DELETED relationship-def instances

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3233:


 Summary: Relationships, Export & Import : Issue with ACTIVE and 
DELETED relationship-def instances
 Key: ATLAS-3233
 URL: https://issues.apache.org/jira/browse/ATLAS-3233
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
 Fix For: 2.0.0


1. In source cluster , create 2 types and a relationship-def between them.
2. Create 2 entities and create relationship instance between them. 
(relationship_guid_1 is created and it is ACTIVE)
3. Export & Import entity1.
4. On target cluster , relationship_guid_1 is imported and it is ACTIVE.
5. Now, on source cluster , delete relationship_guid_1 and create a new 
relationship between entity1 and entity2.
6. In source cluster , relationship_guid_1 is DELETED and new 
relationship_guid_2 is ACTIVE.
7. Export and Import the entity1 to target cluster.
8. In target cluster , relationship_guid_1 is still ACTIVE and 
relationship_guid_2 is not imported at all . (GET on relationship_guid_2 throws 
404 on target cluster)
9. In the exported zip , there is no information about relationship_guid_1 but 
only about relationship_guid_2.

CC : [~ashutoshm]



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

[jira] [Commented] (ATLAS-3201) getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or invalid

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3201:


Commit 794697f7a598826fa2a4231a7a3a6cd07086ac44 in atlas's branch 
refs/heads/branch-1.0 from Diego Marino Monetti
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=794697f ]

ATLAS-3201:- Fix getByGuid in AtlasTypeRegistry, doesn't raise exception if 
guid invalid

Signed-off-by: nixonrodrigues 


>  getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or 
> invalid
> ---
>
> Key: ATLAS-3201
> URL: https://issues.apache.org/jira/browse/ATLAS-3201
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0, 1.2.0, 2.0.0
> Environment: All os
>Reporter: Diego Marino Monetti
>Priority: Major
>  Labels: ready-to-commit
> Fix For: 2.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The BUG was fixed



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

[jira] [Commented] (ATLAS-3202) Hive hook: getStorageDescEntity() throws NPE if bucketCols is null

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3202:


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

ATLAS-3202: Hive hook: getStorageDescEntity() throws NPE if bucketCols is null


> Hive hook: getStorageDescEntity() throws NPE if bucketCols is null
> --
>
> Key: ATLAS-3202
> URL: https://issues.apache.org/jira/browse/ATLAS-3202
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: trunk
>
> Attachments: 
> 0001-ATLAS-3202-Hive-hook-getStorageDescEntity-throws-NPE.patch
>
>
> Null check needs to be added when we create a storageDesc entity in hive hook.
>  



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

[jira] [Commented] (ATLAS-3200) add missing memory requirements for dev-support/atlas-docker/Dockerfile

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3200:


Commit 362ed5f89a39c9d092851fc3aee7ba49f099e518 in atlas's branch 
refs/heads/branch-1.0 from Islam Azab
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=362ed5f ]

ATLAS-3200:- Add missing memory requirements for 
dev-support/atlas-docker/Dockerfile.


> add missing memory requirements for dev-support/atlas-docker/Dockerfile 
> 
>
> Key: ATLAS-3200
> URL: https://issues.apache.org/jira/browse/ATLAS-3200
> Project: Atlas
>  Issue Type: Bug
>Reporter: Islam Azab
>Priority: Major
> Fix For: trunk
>
>
> add missing memory requirements for 
> [dev-support/atlas-docker/Dockerfile|https://github.com/apache/atlas/pull/50/files#diff-f7608cd258a2c6d58d345aa0efcf9828R40]
> Without memory config, this error occurs
> {code}
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15:06 min
> [INFO] Finished at: 2019-05-07T12:50:22Z
> [INFO] 
> 
> [ERROR] GC overhead limit exceeded -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError
> {code}
> Open PR https://github.com/apache/atlas/pull/50



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

[jira] [Commented] (ATLAS-3201) getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or invalid

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on ATLAS-3201:


Commit 512906934b1907441e1648f36d18d87f91d6db82 in atlas's branch 
refs/heads/master from Diego Marino Monetti
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5129069 ]

ATLAS-3201:- Fix getByGuid in AtlasTypeRegistry, doesn't raise exception if 
guid invalid

Signed-off-by: nixonrodrigues 


>  getByGuid in AtlasTypeRegistry doesn't raise exception if guid null or 
> invalid
> ---
>
> Key: ATLAS-3201
> URL: https://issues.apache.org/jira/browse/ATLAS-3201
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0, 1.2.0, 2.0.0
> Environment: All os
>Reporter: Diego Marino Monetti
>Priority: Major
>  Labels: ready-to-commit
> Fix For: 2.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The BUG was fixed



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

[jira] [Updated] (ATLAS-3232) Relationships, Export & Import : Updates to relationshipDef are not honored during import

[Sharmadha Sainath (JIRA)]

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

Sharmadha Sainath updated ATLAS-3232:
-
Description: 
1. In source cluster , updated relationshipDef "hive_table_db" propagateTags to 
"ONE_TO_TWO" from NONE and exported.
2.In export zip  , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for 
"hive_table_db" . 
3. But in the import cluster, propagateTags value for hive_table_db is NONE 
still. In the import options , provided updateTypeDefinition to True too.

CC : [~ashutoshm] 

  was:
1. In source cluster , updated relationshipDef "hive_db_columns" propagateTags 
to "ONE_TO_TWO" from NONE and exported.
2.In export zip  , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for 
"hive_db_columns" . 
3. But in the import cluster, propagateTags value for hive_db_columns is NONE 
still. In the import options , provided updateTypeDefinition to True too.

CC : [~ashutoshm] 


> Relationships, Export & Import : Updates to relationshipDef are not honored 
> during import
> -
>
> Key: ATLAS-3232
> URL: https://issues.apache.org/jira/browse/ATLAS-3232
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 2.0.0
>
>
> 1. In source cluster , updated relationshipDef "hive_table_db" propagateTags 
> to "ONE_TO_TWO" from NONE and exported.
> 2.In export zip  , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value 
> for "hive_table_db" . 
> 3. But in the import cluster, propagateTags value for hive_table_db is NONE 
> still. In the import options , provided updateTypeDefinition to True too.
> CC : [~ashutoshm] 



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

[jira] [Created] (ATLAS-3232) Relationships, Export & Import : Updates to relationshipDef are not honored during import

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3232:


 Summary: Relationships, Export & Import : Updates to 
relationshipDef are not honored during import
 Key: ATLAS-3232
 URL: https://issues.apache.org/jira/browse/ATLAS-3232
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
 Fix For: 2.0.0


1. In source cluster , updated relationshipDef "hive_db_columns" propagateTags 
to "ONE_TO_TWO" from NONE and exported.
2.In export zip  , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for 
"hive_db_columns" . 
3. But in the import cluster, propagateTags value for hive_db_columns is NONE 
still. In the import options , provided updateTypeDefinition to True too.

CC : [~ashutoshm] 



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