[jira] [Resolved] (ATLAS-4043) Atlas import-kafka.sh does not import "__consumer_offsets" topic

2020-12-02 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian resolved ATLAS-4043.
---
Resolution: Fixed

> Atlas import-kafka.sh does not import "__consumer_offsets" topic
> 
>
> Key: ATLAS-4043
> URL: https://issues.apache.org/jira/browse/ATLAS-4043
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Assignee: Deep Singh
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Fixed import __consumer_offsets.png, Screenshot 
> 2020-11-20 at 11.23.47 PM.png
>
>
> Even though kafka-topics.sh --list, lists the __consumer_offsets topic as 
> below, this topic alone is not imported into Atlas when import-kafka.sh 
> script is run
> {code:java}
> ATLAS_ENTITIES 
> ATLAS_HOOK 
> ATLAS_SPARK_HOOK 
> __consumer_offsets 
> connect-configs 
> connect-offsets 
> connect-status  {code}
> I did not find anything unusual in atlas/application.log. This was working 
> fine before, seems like a regression.
> As per official Kafka documentation, __consumer_offsets is used to store 
> information about committed offsets for each topic:partition per group of 
> consumers (groupID). It is compacted topic, so data will be periodically 
> compressed and only latest offsets information available.
> Since __consumer_offsets has __ in the beginning, I have created a topic 
> starting with __ and ran the import-kafka script. And it works fine. So that 
> leaves us with having issue with __consumer_offsets alone.



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


[jira] [Updated] (ATLAS-4043) Atlas import-kafka.sh does not import "__consumer_offsets" topic

2020-12-02 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4043:
--
Fix Version/s: 2.2.0
   3.0.0

> Atlas import-kafka.sh does not import "__consumer_offsets" topic
> 
>
> Key: ATLAS-4043
> URL: https://issues.apache.org/jira/browse/ATLAS-4043
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Assignee: Deep Singh
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Fixed import __consumer_offsets.png, Screenshot 
> 2020-11-20 at 11.23.47 PM.png
>
>
> Even though kafka-topics.sh --list, lists the __consumer_offsets topic as 
> below, this topic alone is not imported into Atlas when import-kafka.sh 
> script is run
> {code:java}
> ATLAS_ENTITIES 
> ATLAS_HOOK 
> ATLAS_SPARK_HOOK 
> __consumer_offsets 
> connect-configs 
> connect-offsets 
> connect-status  {code}
> I did not find anything unusual in atlas/application.log. This was working 
> fine before, seems like a regression.
> As per official Kafka documentation, __consumer_offsets is used to store 
> information about committed offsets for each topic:partition per group of 
> consumers (groupID). It is compacted topic, so data will be periodically 
> compressed and only latest offsets information available.
> Since __consumer_offsets has __ in the beginning, I have created a topic 
> starting with __ and ran the import-kafka script. And it works fine. So that 
> leaves us with having issue with __consumer_offsets alone.



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


[jira] [Commented] (ATLAS-4046) Use Jetty BOM to simplify dependency management

2020-11-23 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-4046:
---

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

> Use Jetty BOM to simplify dependency management
> ---
>
> Key: ATLAS-4046
> URL: https://issues.apache.org/jira/browse/ATLAS-4046
> Project: Atlas
>  Issue Type: Task
>Reporter: Kevin Risden
>Priority: Minor
> Attachments: ATLAS-4046.patch
>
>
> There are a bunch of defined jetty artifacts in dependencyManagement in the 
> root pom.xml. Jetty has a BOM maven artifact that simplifies this to ensure 
> that all the dependencies are the correct version:
> https://github.com/apache/atlas/blob/master/pom.xml#L1207
> https://mvnrepository.com/artifact/org.eclipse.jetty/jetty-bom



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


[jira] [Resolved] (ATLAS-4037) Empty Client ID Field in Admin audits

2020-11-23 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian resolved ATLAS-4037.
---
Resolution: Fixed

> Empty Client ID Field in Admin audits
> -
>
> Key: ATLAS-4037
> URL: https://issues.apache.org/jira/browse/ATLAS-4037
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Deep Singh
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> TYPE_DEF_CREATE and TYPE_DEF_UPDATE have empty "*Client ID*" field.
> These should be updated for all entries that are generated by system
> Example: The following result shows where *clientID* is not available
> {code:java}
> {
>  "guid": "",
>  "operation": "TYPE_DEF_UPDATE",
>  "params": "RELATIONSHIP,ENTITY",
>  "startTime": 1605585786541,
>  "endTime": 1605585786747,
>  "result": "<>",
>  "resultCount": 3
> }
> {code}
>  
> Result where all fiends are available:
> {code:java}
> {
>  "guid": "",
>  "userName": "",
>  "operation": "TYPE_DEF_UPDATE",
>  "params": "CLASSIFICATION",
>  "startTime": 1605700613879,
>  "endTime": 1605700614297,
>  "clientId": "",
>  "result": "",
>  "resultCount": 1
>  }
> {code}



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


[jira] [Updated] (ATLAS-4037) Empty Client ID Field in Admin audits

2020-11-23 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4037:
--
Fix Version/s: 2.2.0
   3.0.0

> Empty Client ID Field in Admin audits
> -
>
> Key: ATLAS-4037
> URL: https://issues.apache.org/jira/browse/ATLAS-4037
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Deep Singh
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> TYPE_DEF_CREATE and TYPE_DEF_UPDATE have empty "*Client ID*" field.
> These should be updated for all entries that are generated by system
> Example: The following result shows where *clientID* is not available
> {code:java}
> {
>  "guid": "",
>  "operation": "TYPE_DEF_UPDATE",
>  "params": "RELATIONSHIP,ENTITY",
>  "startTime": 1605585786541,
>  "endTime": 1605585786747,
>  "result": "<>",
>  "resultCount": 3
> }
> {code}
>  
> Result where all fiends are available:
> {code:java}
> {
>  "guid": "",
>  "userName": "",
>  "operation": "TYPE_DEF_UPDATE",
>  "params": "CLASSIFICATION",
>  "startTime": 1605700613879,
>  "endTime": 1605700614297,
>  "clientId": "",
>  "result": "",
>  "resultCount": 1
>  }
> {code}



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


[jira] [Updated] (ATLAS-4036) Empty "Users" Field in Admin audits

2020-11-23 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4036:
--
Affects Version/s: 2.1.0

> Empty "Users" Field in Admin audits
> ---
>
> Key: ATLAS-4036
> URL: https://issues.apache.org/jira/browse/ATLAS-4036
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Deep Singh
>Priority: Major
>
> TYPE_DEF_CREATE, TYPE_DEF_UPDATE, SERVER_START and SERVER_STATE_ACTIVE have 
> empty "*Users*" field.
> If the changes are being done by the system/admin the same should be updated 
> there like "System generated"/ "System"/"Admin" or something similar
> Example: Here is a *SERVER_START* operation audit. Here There is no 
> *userName* field, resulting in empty Users in UI
> {code}
> [
>  {
>  "guid": "",
>  "operation": "SERVER_START",
>  "startTime": 1605585671419,
>  "endTime": 1605585837730,
>  "clientId": "",
>  "resultCount": 0
>  }
> ]
> {code}



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


[jira] [Resolved] (ATLAS-4036) Empty "Users" Field in Admin audits

2020-11-23 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian resolved ATLAS-4036.
---
Resolution: Fixed

> Empty "Users" Field in Admin audits
> ---
>
> Key: ATLAS-4036
> URL: https://issues.apache.org/jira/browse/ATLAS-4036
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Deep Singh
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> TYPE_DEF_CREATE, TYPE_DEF_UPDATE, SERVER_START and SERVER_STATE_ACTIVE have 
> empty "*Users*" field.
> If the changes are being done by the system/admin the same should be updated 
> there like "System generated"/ "System"/"Admin" or something similar
> Example: Here is a *SERVER_START* operation audit. Here There is no 
> *userName* field, resulting in empty Users in UI
> {code}
> [
>  {
>  "guid": "",
>  "operation": "SERVER_START",
>  "startTime": 1605585671419,
>  "endTime": 1605585837730,
>  "clientId": "",
>  "resultCount": 0
>  }
> ]
> {code}



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


[jira] [Updated] (ATLAS-4037) Empty Client ID Field in Admin audits

2020-11-23 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4037:
--
Affects Version/s: 2.1.0

> Empty Client ID Field in Admin audits
> -
>
> Key: ATLAS-4037
> URL: https://issues.apache.org/jira/browse/ATLAS-4037
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Deep Singh
>Priority: Major
>
> TYPE_DEF_CREATE and TYPE_DEF_UPDATE have empty "*Client ID*" field.
> These should be updated for all entries that are generated by system
> Example: The following result shows where *clientID* is not available
> {code:java}
> {
>  "guid": "",
>  "operation": "TYPE_DEF_UPDATE",
>  "params": "RELATIONSHIP,ENTITY",
>  "startTime": 1605585786541,
>  "endTime": 1605585786747,
>  "result": "<>",
>  "resultCount": 3
> }
> {code}
>  
> Result where all fiends are available:
> {code:java}
> {
>  "guid": "",
>  "userName": "",
>  "operation": "TYPE_DEF_UPDATE",
>  "params": "CLASSIFICATION",
>  "startTime": 1605700613879,
>  "endTime": 1605700614297,
>  "clientId": "",
>  "result": "",
>  "resultCount": 1
>  }
> {code}



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


[jira] [Updated] (ATLAS-4036) Empty "Users" Field in Admin audits

2020-11-23 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4036:
--
Fix Version/s: 2.2.0
   3.0.0

> Empty "Users" Field in Admin audits
> ---
>
> Key: ATLAS-4036
> URL: https://issues.apache.org/jira/browse/ATLAS-4036
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Deep Singh
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> TYPE_DEF_CREATE, TYPE_DEF_UPDATE, SERVER_START and SERVER_STATE_ACTIVE have 
> empty "*Users*" field.
> If the changes are being done by the system/admin the same should be updated 
> there like "System generated"/ "System"/"Admin" or something similar
> Example: Here is a *SERVER_START* operation audit. Here There is no 
> *userName* field, resulting in empty Users in UI
> {code}
> [
>  {
>  "guid": "",
>  "operation": "SERVER_START",
>  "startTime": 1605585671419,
>  "endTime": 1605585837730,
>  "clientId": "",
>  "resultCount": 0
>  }
> ]
> {code}



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


[jira] [Updated] (ATLAS-4042) "Error while authentication" grammatical error

2020-11-18 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4042:
--
Attachment: ATLAS-4042.001.patch

> "Error while authentication" grammatical error
> --
>
> Key: ATLAS-4042
> URL: https://issues.apache.org/jira/browse/ATLAS-4042
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Alasdair Brown
>Assignee: Sarath Subramanian
>Priority: Trivial
> Attachments: ATLAS-4042.001.patch, image-2020-11-18-17-58-00-819.png
>
>
> Just a grammatical error -  An error when authenticating generates this error 
> on the login screen "Error while authentication" should probably be "Error 
> while authenticating"
> !image-2020-11-18-17-58-00-819.png|width=377,height=355!



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


[jira] [Assigned] (ATLAS-4042) "Error while authentication" grammatical error

2020-11-18 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian reassigned ATLAS-4042:
-

Assignee: Sarath Subramanian

> "Error while authentication" grammatical error
> --
>
> Key: ATLAS-4042
> URL: https://issues.apache.org/jira/browse/ATLAS-4042
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Alasdair Brown
>Assignee: Sarath Subramanian
>Priority: Trivial
> Attachments: ATLAS-4042.001.patch, image-2020-11-18-17-58-00-819.png
>
>
> Just a grammatical error -  An error when authenticating generates this error 
> on the login screen "Error while authentication" should probably be "Error 
> while authenticating"
> !image-2020-11-18-17-58-00-819.png|width=377,height=355!



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


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

2020-11-18 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4028:
--
Fix Version/s: 2.2.0
   3.0.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
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> 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-4013) JanusGraph 0.5.1 is not compatible with elasticsearch 5.*

2020-11-18 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4013:
--
Fix Version/s: 2.2.0
   3.0.0

> 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
> Fix For: 3.0.0, 2.2.0
>
> 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] [Updated] (ATLAS-4027) Update Atlas with latest version of slf4j - 1.7.30

2020-11-18 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4027:
--
Fix Version/s: 2.2.0
   3.0.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
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> 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-4026) Update Atlas with latest version of JanusGraph - 0.5.2

2020-11-16 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-4026:
--
Fix Version/s: 2.2.0
   3.0.0

> 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
> Fix For: 3.0.0, 2.2.0
>
>
> 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-4023) Import Service: Labels Not Importing Correctly

2020-11-13 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-4023:
---

+1. Thanks for the patch [~amestry]

> Import Service: Labels Not Importing Correctly
> --
>
> Key: ATLAS-4023
> URL: https://issues.apache.org/jira/browse/ATLAS-4023
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: 
> ATLAS-4023-Import-Service-Label-and-Classification-e.patch
>
>
> *Steps to Duplicate*
>  # Create dataset with _hive_db, hive_table,_ say _t1_.
>  # Add label to _hive_table,_ say _label1, label2_.
>  # Perform _Import_. Import succeeds with _hive_table_ getting assigned 
> labels _label1_ and _label2_.
>  # Modify _t1_ such that it has only _label1_.
>  # Perform Import.
> Expected result: _t1_ should have _label1._
> Actual result: _t1_ has _label1_ and _label2._
>  Original reporter: [~umesh.padashetty]  Thanks you!



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


[jira] [Commented] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication

2020-10-09 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3989:
---

Looks good +1. Thanks [~amestry].

> Behavior change in Atlas API to get Atlas Server object during metadata 
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: 
> ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
>
>
> There is a change being noticed in the Atlas server API used during atlas 
> metadata replication in hive.
>  Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster 
> name, used to work.
>  Now, it doesn't work any more. This Api is used during replication to get 
> the changeMarker info.
>  Now the API works with some thing called server name which is 'default' by 
> default.
>  Also, now the prerequisite is to at least have one export or import API call 
> in order to get this 'default' initialized.
>  The change-marker is obtained prior to invoking export and hence the all 
> policy is bound to fail unless we mandate calling Export or Import API 
> outside hive replication once to get this object initialized, even if hive 
> uses 'default' in the call.
>  
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}



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


[jira] [Commented] (ATLAS-3948) Entity Creation: Index Consistency: Java Patch Handler: Provide Option to Disable

2020-09-17 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3948:
---

thanks for the patch [~amestry] +1

> Entity Creation: Index Consistency: Java Patch Handler: Provide Option to 
> Disable
> -
>
> Key: ATLAS-3948
> URL: https://issues.apache.org/jira/browse/ATLAS-3948
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3948-index-consistency-conditional.patch
>
>
> *Background*
> The ATLAS-3907 provided ability to apply index consistency to existing 
> indexes via Java patch handler.
> However, when _atlas.graph.storage.consistency-lock.enabled=false_ this patch 
> still gets applied.
> *Solution*
> Check for the property in Java patch handler and avoid applying it if the 
> property is set to false.



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


[jira] [Commented] (ATLAS-3941) NotificationHookConsumer: Reduce Retry Pause Interval

2020-09-14 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3941:
---

Thanks for the patch. +1

> NotificationHookConsumer: Reduce Retry Pause Interval
> -
>
> Key: ATLAS-3941
> URL: https://issues.apache.org/jira/browse/ATLAS-3941
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 2.1.0
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: 
> ATLAS-3941-NotificationHookConsumer-Reduce-wait-time.patch
>
>
> *Background*
> The retry logic introduced earlier, had a long wait time in case a concurrent 
> entity create was detected. This adversely affect ingest speed in the case 
> where there are a lot of errors in the data being ingested.
> *Solution*
> Reduce the wait time.



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


[jira] [Updated] (ATLAS-3898) Authorize read of typedefs

2020-08-14 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3898:
--
Fix Version/s: 3.0.0

> Authorize read of typedefs
> --
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>  Labels: authorization, ranger
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3898.1.patch
>
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This patch authorize read for all typedefs. It implicitly add read permission 
> if create,update or delete permission is assigned to user.



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


[jira] [Updated] (ATLAS-3898) Authorize read of typedefs

2020-08-14 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3898:
--
Fix Version/s: 2.2.0

> Authorize read of typedefs
> --
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>  Labels: authorization, ranger
> Fix For: 2.2.0
>
> Attachments: ATLAS-3898.1.patch
>
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This patch authorize read for all typedefs. It implicitly add read permission 
> if create,update or delete permission is assigned to user.



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


[jira] [Updated] (ATLAS-3898) Authorize read of typedefs

2020-08-14 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3898:
--
Affects Version/s: 2.1.0

> Authorize read of typedefs
> --
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3898.1.patch
>
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This patch authorize read for all typedefs. It implicitly add read permission 
> if create,update or delete permission is assigned to user.



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


[jira] [Updated] (ATLAS-3898) Authorize read of typedefs

2020-08-14 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3898:
--
Labels: authorization ranger  (was: )

> Authorize read of typedefs
> --
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>  Labels: authorization, ranger
> Attachments: ATLAS-3898.1.patch
>
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This patch authorize read for all typedefs. It implicitly add read permission 
> if create,update or delete permission is assigned to user.



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


[jira] [Updated] (ATLAS-3898) Authorize read of typedefs

2020-08-14 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3898:
--
Component/s:  atlas-core

> Authorize read of typedefs
> --
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3898.1.patch
>
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This patch authorize read for all typedefs. It implicitly add read permission 
> if create,update or delete permission is assigned to user.



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


[jira] [Commented] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-08-12 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3900:
---

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

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
>  Labels: basic-search, datetimepicker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900-2.patch, 
> ATLAS-3900-3.patch, ATLAS-3900.patch, Screen Shot 2020-07-21 at 10.59.59 
> PM.png, Screen Shot 2020-07-21 at 11.00.08 PM.png, Screen Shot 2020-07-21 at 
> 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-21 at 10.59.59 PM.png|width=631,height=282!
>  
> !Screen Shot 2020-07-21 at 11.00.08 PM.png|width=630,height=302!
>  
> !Screen Shot 2020-07-21 at 11.00.15 PM.png|width=630,height=304!



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


[jira] [Updated] (ATLAS-3919) Handling classification propagation as deferred-action

2020-08-12 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3919:
--
Affects Version/s: 2.0.0
   2.1.0

> Handling classification propagation as deferred-action
> --
>
> Key: ATLAS-3919
> URL: https://issues.apache.org/jira/browse/ATLAS-3919
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Jayendra Parab
>Assignee: Jayendra Parab
>Priority: Major
>
> Currently, whenever a user assigns a tag or updates a tag on an entity, it 
> gets propagated to all the entities derived from the tagged entity. This 
> operation takes quite a lot of time to complete (sometimes into minutes) and 
> causes usability issues on the UI and other clients invoking the REST API
> To resolve this issue, tag-propagation needs to be handled as 
> deferred-action, so that time consuming like propagation, audits & 
> notifications can be processed in background threads



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


[jira] [Commented] (ATLAS-3916) Get metrics according to the user permissions

2020-08-11 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3916:
---

[~yued], good requirement. The way metrics query works today is we rely on solr 
to provide you with the totalCount of a specific type. 
{code:java}
atlasGraph.indexQuery(VERTEX_INDEX, indexQuery).vertexTotals();
{code}
If metrics query should display the count of only those entities which user has 
read authorization.

We may need to go over individual entities for each type and check if user has 
authorization. 

 

> Get metrics according to the user permissions
> -
>
> Key: ATLAS-3916
> URL: https://issues.apache.org/jira/browse/ATLAS-3916
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Yue Dong
>Priority: Major
> Attachments: Captura-de-pantalla-de-2020-08-11-10-20-06.png
>
>
> I have two user groups: admin who has access to all tables and reader can 
> only see public data and module A tables. So I have configured Atlas to use a 
> simple authorizer with a little variation, which is to hide entities that are 
> not accessible to the user.
> The searches and displaying results work properly.
> The only problem I find is that the metrics. In the elements of search by 
> type, it indicates the number of all the entities of each type in the system. 
> And this is not consistent with the search result of a reader user. 
> !Captura-de-pantalla-de-2020-08-11-10-20-06.png!
>  
> I have verified that these numbers come from the getMetrics method, which is 
> not secured so it does not obtain the numbers according to the users' 
> configuration. Am I missing something? Is there any way to change these 
> numbers?
> Maybe it'd be nice to have something that allows to modify the querys of the 
> metrics based on security and authorization, like 
> AtlasAuthorizer.scrubSearchResults in search methods.
>  



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


[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs

2020-08-07 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3913:
--
Labels: REST_API swagger  (was: )

> Swagger documentation for APIs
> --
>
> Key: ATLAS-3913
> URL: https://issues.apache.org/jira/browse/ATLAS-3913
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>  Labels: REST_API, swagger
>
> Current packaging does not package swagger ui into Atlas war.
> This change will pack swagger ui into the war file.
> Also update enunciate version from 2.11.1 to 2.13.1



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


[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs

2020-08-07 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3913:
--
Affects Version/s: 2.1.0

> Swagger documentation for APIs
> --
>
> Key: ATLAS-3913
> URL: https://issues.apache.org/jira/browse/ATLAS-3913
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>  Labels: REST_API, swagger
>
> Current packaging does not package swagger ui into Atlas war.
> This change will pack swagger ui into the war file.
> Also update enunciate version from 2.11.1 to 2.13.1



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


[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs

2020-08-07 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3913:
--
Fix Version/s: 2.2.0
   3.0.0

> Swagger documentation for APIs
> --
>
> Key: ATLAS-3913
> URL: https://issues.apache.org/jira/browse/ATLAS-3913
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 2.1.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>  Labels: REST_API, swagger
> Fix For: 3.0.0, 2.2.0
>
>
> Current packaging does not package swagger ui into Atlas war.
> This change will pack swagger ui into the war file.
> Also update enunciate version from 2.11.1 to 2.13.1



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


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-08-07 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3900:
--
Labels: basic-search datetimepicker  (was: )

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
>  Labels: basic-search, datetimepicker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900-2.patch, 
> ATLAS-3900.patch, Screen Shot 2020-07-21 at 10.59.59 PM.png, Screen Shot 
> 2020-07-21 at 11.00.08 PM.png, Screen Shot 2020-07-21 at 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-21 at 10.59.59 PM.png|width=631,height=282!
>  
> !Screen Shot 2020-07-21 at 11.00.08 PM.png|width=630,height=302!
>  
> !Screen Shot 2020-07-21 at 11.00.15 PM.png|width=630,height=304!



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


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-08-07 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3900:
--
Affects Version/s: 2.1.0

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900-2.patch, 
> ATLAS-3900.patch, Screen Shot 2020-07-21 at 10.59.59 PM.png, Screen Shot 
> 2020-07-21 at 11.00.08 PM.png, Screen Shot 2020-07-21 at 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-21 at 10.59.59 PM.png|width=631,height=282!
>  
> !Screen Shot 2020-07-21 at 11.00.08 PM.png|width=630,height=302!
>  
> !Screen Shot 2020-07-21 at 11.00.15 PM.png|width=630,height=304!



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


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-08-07 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3900:
--
Component/s: atlas-webui

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900-2.patch, 
> ATLAS-3900.patch, Screen Shot 2020-07-21 at 10.59.59 PM.png, Screen Shot 
> 2020-07-21 at 11.00.08 PM.png, Screen Shot 2020-07-21 at 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-21 at 10.59.59 PM.png|width=631,height=282!
>  
> !Screen Shot 2020-07-21 at 11.00.08 PM.png|width=630,height=302!
>  
> !Screen Shot 2020-07-21 at 11.00.15 PM.png|width=630,height=304!



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


[jira] [Updated] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases

2020-07-16 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3875:
--
Affects Version/s: 2.1.0

> Adding missing APIs in AtlasClient with test cases
> --
>
> Key: ATLAS-3875
> URL: https://issues.apache.org/jira/browse/ATLAS-3875
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Jyoti Singh
>Assignee: Jyoti Singh
>Priority: Major
>  Labels: api, client
> Attachments: ATLAS-3875-1.patch
>
>
> There are many new APIs added to Atlas Project but the corresponding  APIs 
> are missing from AtlasClientv2. The aim of this task is to complete the gap 
> amongst existing APIs and their endpoints in Atls client. This will also 
> include adding test cases via integration testing.
> There are functions from AtlasClient for the following REST endpoints
>  * TypeRest
>  * EntityRest
>  * LineageRest
>  * DiscoveryRest
>  * GlossaryRest
>  * RelationshipRest



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


[jira] [Updated] (ATLAS-3885) import-hive.sh: Hive entities with Ozone location created by import-hive.sh creates hdfs_path entity instead of ozone in Atlas

2020-07-13 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3885:
--
Labels: import ozone  (was: ozone)

> import-hive.sh: Hive entities with Ozone location created by import-hive.sh 
> creates hdfs_path entity instead of ozone in Atlas
> --
>
> Key: ATLAS-3885
> URL: https://issues.apache.org/jira/browse/ATLAS-3885
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>  Labels: import, ozone
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3885-import-hive-Hive-entities-with-Ozone-v0.patch
>
>
> import-hive.sh when attempts to import hive entities with Ozone location 
> expected is that ozone_key should get created as path entity, but script 
> creates hdfs_path entity instead of ozone_key in Atlas.
>  
> Steps to reproduce
>  # Disable HMS Hook and Hive Hook
>  # Create external table with ozone location
>  # Run import-hive.sh
> The location entity is created as an hdfs_path entity instead of ozone_key.



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


[jira] [Updated] (ATLAS-3885) import-hive.sh: Hive entities with Ozone location created by import-hive.sh creates hdfs_path entity instead of ozone in Atlas

2020-07-13 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3885:
--
Fix Version/s: 2.1.0
   trunk

> import-hive.sh: Hive entities with Ozone location created by import-hive.sh 
> creates hdfs_path entity instead of ozone in Atlas
> --
>
> Key: ATLAS-3885
> URL: https://issues.apache.org/jira/browse/ATLAS-3885
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>  Labels: ozone
> Fix For: trunk, 2.1.0
>
> Attachments: ATLAS-3885-import-hive-Hive-entities-with-Ozone-v0.patch
>
>
> import-hive.sh when attempts to import hive entities with Ozone location 
> expected is that ozone_key should get created as path entity, but script 
> creates hdfs_path entity instead of ozone_key in Atlas.
>  
> Steps to reproduce
>  # Disable HMS Hook and Hive Hook
>  # Create external table with ozone location
>  # Run import-hive.sh
> The location entity is created as an hdfs_path entity instead of ozone_key.



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


[jira] [Updated] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases

2020-07-01 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3875:
--
Labels: api client  (was: )

> Adding missing APIs in AtlasClient with test cases
> --
>
> Key: ATLAS-3875
> URL: https://issues.apache.org/jira/browse/ATLAS-3875
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Jyoti Singh
>Assignee: Jyoti Singh
>Priority: Major
>  Labels: api, client
>
> There are many new APIs added to Atlas Project but the corresponding  APIs 
> are missing from AtlasClientv2. The aim of this task is to complete the gap 
> amongst existing APIs and their endpoints in Atls client. This will also 
> include adding test cases via integration testing.
> There are functions from AtlasClient for the following REST endpoints
>  * TypeRest
>  * EntityRest
>  * LineageRest
>  * DiscoveryRest
>  * GlossaryRest
>  * RelationshipRest



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


[jira] [Updated] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases

2020-07-01 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3875:
--
Component/s:  atlas-core

> Adding missing APIs in AtlasClient with test cases
> --
>
> Key: ATLAS-3875
> URL: https://issues.apache.org/jira/browse/ATLAS-3875
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Jyoti Singh
>Assignee: Jyoti Singh
>Priority: Major
>
> There are many new APIs added to Atlas Project but the corresponding  APIs 
> are missing from AtlasClientv2. The aim of this task is to complete the gap 
> amongst existing APIs and their endpoints in Atls client. This will also 
> include adding test cases via integration testing.
> There are functions from AtlasClient for the following REST endpoints
>  * TypeRest
>  * EntityRest
>  * LineageRest
>  * DiscoveryRest
>  * GlossaryRest
>  * RelationshipRest



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


[jira] [Commented] (ATLAS-3869) Upgrade httpclient from 4.5.3 to 4.5.4

2020-07-01 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3869:
---

[~nixon], consider merging this to branch-2.0 as well.

> Upgrade httpclient from 4.5.3 to 4.5.4
> --
>
> Key: ATLAS-3869
> URL: https://issues.apache.org/jira/browse/ATLAS-3869
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3869-Upgrade-httpclient-from-4.5.3-to-4.5.4.patch
>
>
> Found below exception where data was not getting added in SOLR from 
> janusgraph.
>  
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to java.lang.String
>   at 
> org.apache.http.conn.ssl.DefaultHostnameVerifier.getSubjectAltNames(DefaultHostnameVerifier.java:309)
>   at 
> org.apache.http.conn.ssl.DefaultHostnameVerifier.verify(DefaultHostnameVerifier.java:112)
>   at 
> org.apache.http.conn.ssl.DefaultHostnameVerifier.verify(DefaultHostnameVerifier.java:99)
>   at 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:463)
>   at 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:397)
>   at 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355)
>   at 
> org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
>   at 
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:359)
>   at 
> org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
>   at 
> org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
>   at 
> org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
>   at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
>   at 
> org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
>   at 
> org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
>   at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
>   at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
>   at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:526)
>   at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:253)
>   at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:242)
>   at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:483)
>   ... 7 more
> 2020-06-29 07:31:25,893 WARN  - [SIGTERM handler:] ~ Unable to close 
> transaction standardjanusgraphtx[0x18d7a16a] (StandardJanusGraph:230)
> java.lang.IllegalArgumentException: The transaction has already been closed
>   at 
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:142)
>   at 
> org.janusgraph.graphdb.transaction.StandardJanusGraphTx.rollback(StandardJanusGraphTx.java:1401)
>   at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction$1.doRollback(JanusGraphBlueprintsTransaction.java:190)
>   at 
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.rollback(AbstractTransaction.java:114)
>   at 
> org.apache.tinkerpop.gremlin.structure.Transaction$CLOSE_BEHAVIOR$2.accept(Transaction.java:182)
>   at 
> org.apache.tinkerpop.gremlin.structure.Transaction$CLOSE_BEHAVIOR$2.accept(Transaction.java:179)
>   at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.close(JanusGraphBlueprintsGraph.java:327)
>   at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction$1.doClose(JanusGraphBlueprintsTransaction.java:205)
>   at 
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.close(AbstractTransaction.java:139)
>   at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction.close(JanusGraphBlueprintsTransaction.java:215)
>   at 
> org.janusgraph.graphdb.database.StandardJanusGraph.closeInternal(StandardJanusGraph.java:226)
>   at 
> org.janusgraph.graphdb.database.StandardJanusGraph.access$500(StandardJanusGraph.java:91)
>   at 
> org.janusgraph.graphdb.database.StandardJanusGraph$ShutdownThread.start(StandardJanusGraph.java:818)
>   at 
> java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:102)
>   at 
> java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)

[jira] [Updated] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases

2020-07-01 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3875:
--
Affects Version/s: 2.0.0

> Adding missing APIs in AtlasClient with test cases
> --
>
> Key: ATLAS-3875
> URL: https://issues.apache.org/jira/browse/ATLAS-3875
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Jyoti Singh
>Assignee: Jyoti Singh
>Priority: Major
>
> There are many new APIs added to Atlas Project but the corresponding  APIs 
> are missing from AtlasClientv2. The aim of this task is to complete the gap 
> amongst existing APIs and their endpoints in Atls client. This will also 
> include adding test cases via integration testing.
> There are functions from AtlasClient for the following REST endpoints
>  * TypeRest
>  * EntityRest
>  * LineageRest
>  * DiscoveryRest
>  * GlossaryRest
>  * RelationshipRest



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


[jira] [Commented] (ATLAS-3871) Add unit tests to path extractor utility for s3, s3 v2, adls path entities

2020-07-01 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3871:
---

please merge this in branch-2.0 as well.

> Add unit tests to path extractor utility for s3, s3 v2, adls path entities
> --
>
> Key: ATLAS-3871
> URL: https://issues.apache.org/jira/browse/ATLAS-3871
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> AtlasPathExtractorUtilTest added in ATLAS-3836 which covers unit tests for 
> ozone & hdfs path entites.
>  
> This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & 
> adls path entities.
> Would add more tests for ozone as well.



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


[jira] [Updated] (ATLAS-3870) UI: hive_table entity table not updating queryparams based on filter selected

2020-06-30 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3870:
--
Component/s: atlas-webui

> UI: hive_table entity table not updating queryparams based on filter selected
> -
>
> Key: ATLAS-3870
> URL: https://issues.apache.org/jira/browse/ATLAS-3870
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3870.patch, Screenshot 2020-06-30 at 2.33.11 
> PM.png, Screenshot 2020-06-30 at 2.34.06 PM.png
>
>
> * Go to hive_db entity detail page
>  * Click on Table tab
>  * toggle "Show historical entities" checkbox and check the network for the 
> API
> API always send the same value for
> {code:java}
> excludeDeletedEntities: true
> {code}
> !Screenshot 2020-06-30 at 2.33.11 PM.png|width=374,height=219!
> !Screenshot 2020-06-30 at 2.34.06 PM.png|width=397,height=142!



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


[jira] [Updated] (ATLAS-3870) UI: hive_table entity table not updating queryparams based on filter selected

2020-06-30 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3870:
--
Labels: ui  (was: )

> UI: hive_table entity table not updating queryparams based on filter selected
> -
>
> Key: ATLAS-3870
> URL: https://issues.apache.org/jira/browse/ATLAS-3870
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
>  Labels: ui
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3870.patch, Screenshot 2020-06-30 at 2.33.11 
> PM.png, Screenshot 2020-06-30 at 2.34.06 PM.png
>
>
> * Go to hive_db entity detail page
>  * Click on Table tab
>  * toggle "Show historical entities" checkbox and check the network for the 
> API
> API always send the same value for
> {code:java}
> excludeDeletedEntities: true
> {code}
> !Screenshot 2020-06-30 at 2.33.11 PM.png|width=374,height=219!
> !Screenshot 2020-06-30 at 2.34.06 PM.png|width=397,height=142!



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


[jira] [Resolved] (ATLAS-3836) Add Apache Ozone support in hive hook

2020-06-30 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian resolved ATLAS-3836.
---
Resolution: Fixed

> Add Apache Ozone support in hive hook
> -
>
> Key: ATLAS-3836
> URL: https://issues.apache.org/jira/browse/ATLAS-3836
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Nikhil Bonte
>Priority: Major
>  Labels: hive-hooks, ozone
> Fix For: 2.1.0
>
> Attachments: Hive_table_lineage.png, 
> Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png, 
> Ozone_volume.png
>
>
> Apache Ozone is the new object store for Hadoop - 
> [https://hadoop.apache.org/ozone/]
> Apache Atlas needs to add entity types to support creation of Ozone entities. 
> Hive hook should also be updated to create lineage between ozone entities and 
> hive tables (for EXTERNAL TABLE)



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


[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook

2020-06-30 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3836:
--
Labels: hive-hooks ozone  (was: )

> Add Apache Ozone support in hive hook
> -
>
> Key: ATLAS-3836
> URL: https://issues.apache.org/jira/browse/ATLAS-3836
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Nikhil Bonte
>Priority: Major
>  Labels: hive-hooks, ozone
> Fix For: 2.1.0
>
> Attachments: Hive_table_lineage.png, 
> Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png, 
> Ozone_volume.png
>
>
> Apache Ozone is the new object store for Hadoop - 
> [https://hadoop.apache.org/ozone/]
> Apache Atlas needs to add entity types to support creation of Ozone entities. 
> Hive hook should also be updated to create lineage between ozone entities and 
> hive tables (for EXTERNAL TABLE)



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


[jira] [Updated] (ATLAS-3868) [Regression] removing a term-association doesn't remove classifications propagated from the term

2020-06-29 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3868:
--
Labels: glossary tagpropagation terms  (was: glossary tagpropagation)

> [Regression] removing a term-association doesn't remove classifications 
> propagated from the term
> 
>
> Key: ATLAS-3868
> URL: https://issues.apache.org/jira/browse/ATLAS-3868
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>  Labels: glossary, tagpropagation, terms
> Fix For: 2.1.0
>
>
> # Create a business term – *term1*
>  # Associate classification *PII* to *term1*
>  # Associate *term1* to an entity
>  # Entity will now have PII classification propagated from the term
>  # Now remove *term1* association with the entity
>  # Entity still shows *PII* classification, propagated from the term => this 
> is a regression
>  
> This regression is caused by ATLAS-3863



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


[jira] [Updated] (ATLAS-3868) [Regression] removing a term-association doesn't remove classifications propagated from the term

2020-06-29 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3868:
--
Labels: glossary tagpropagation  (was: )

> [Regression] removing a term-association doesn't remove classifications 
> propagated from the term
> 
>
> Key: ATLAS-3868
> URL: https://issues.apache.org/jira/browse/ATLAS-3868
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>  Labels: glossary, tagpropagation
> Fix For: 2.1.0
>
>
> # Create a business term – *term1*
>  # Associate classification *PII* to *term1*
>  # Associate *term1* to an entity
>  # Entity will now have PII classification propagated from the term
>  # Now remove *term1* association with the entity
>  # Entity still shows *PII* classification, propagated from the term => this 
> is a regression
>  
> This regression is caused by ATLAS-3863



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


[jira] [Updated] (ATLAS-3868) [Regression] removing a term-association doesn't remove classifications propagated from the term

2020-06-29 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3868:
--
Description: 
# Create a business term – *term1*
 # Associate classification *PII* to *term1*
 # Associate *term1* to an entity
 # Entity will now have PII classification propagated from the term
 # Now remove *term1* association with the entity
 # Entity still shows *PII* classification, propagated from the term => this is 
a regression

 

This regression is caused by ATLAS-3863

  was:
# Create a business term – *term1*
 # Associate classification *PII* to *term1*
 # Associate *term1* to an entity
 # Entity will now have PII classification propagated from the term
 # Now remove *term1* association with the entity
 # Entity still shows *PII* classification, propagated from the term => this is 
a regression

 

This regression is caused by ATLAS-3863


> [Regression] removing a term-association doesn't remove classifications 
> propagated from the term
> 
>
> Key: ATLAS-3868
> URL: https://issues.apache.org/jira/browse/ATLAS-3868
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
>
> # Create a business term – *term1*
>  # Associate classification *PII* to *term1*
>  # Associate *term1* to an entity
>  # Entity will now have PII classification propagated from the term
>  # Now remove *term1* association with the entity
>  # Entity still shows *PII* classification, propagated from the term => this 
> is a regression
>  
> This regression is caused by ATLAS-3863



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


[jira] [Created] (ATLAS-3868) [Regression] removing a term-association doesn't remove classifications propagated from the term

2020-06-29 Thread Sarath Subramanian (Jira)
Sarath Subramanian created ATLAS-3868:
-

 Summary: [Regression] removing a term-association doesn't remove 
classifications propagated from the term
 Key: ATLAS-3868
 URL: https://issues.apache.org/jira/browse/ATLAS-3868
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 2.1.0


# Create a business term – *term1*
 # Associate classification *PII* to *term1*
 # Associate *term1* to an entity
 # Entity will now have PII classification propagated from the term
 # Now remove *term1* association with the entity
 # Entity still shows *PII* classification, propagated from the term => this is 
a regression

 

This regression is caused by ATLAS-3863



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


[jira] [Updated] (ATLAS-3838) Support multiple tag/classification in basic/quick search API

2020-06-29 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3838:
--
Fix Version/s: (was: 2.1.0)

> Support multiple tag/classification in basic/quick search API
> -
>
> Key: ATLAS-3838
> URL: https://issues.apache.org/jira/browse/ATLAS-3838
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 3.0.0
>
>
> it will allow user to search with multiple tags and the tag attribute filters 
> (attribute should System attributes or attribute which common for all the 
> mentioned tags)



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


[jira] [Updated] (ATLAS-3849) UI: Create icons for new entity types for Apache ozone

2020-06-26 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3849:
--
Labels: ui  (was: )

> UI: Create icons for new entity types for Apache ozone
> --
>
> Key: ATLAS-3849
> URL: https://issues.apache.org/jira/browse/ATLAS-3849
> Project: Atlas
>  Issue Type: New Feature
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Keval Bhatt
>Priority: Major
>  Labels: ui
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3849.patch
>
>
> New typeDefs:
>  * ozone_volume
>  * ozone_bucket
>  * ozone_key



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


[jira] [Updated] (ATLAS-3855) Bulk entity tag association and bulk api enhancement

2020-06-25 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3855:
--
Affects Version/s: (was: 3.0.0)
   2.0.0

> Bulk entity tag association and bulk api enhancement
> 
>
> Key: ATLAS-3855
> URL: https://issues.apache.org/jira/browse/ATLAS-3855
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> API : /api/atlas/v2/entity/bulk/classification
> Body :
> {code:java}
> {"classification":{"typeName":"PII","attributes":{},"propagate":true,"removePropagationsOnEntityDelete":false,"validityPeriods":[]},"entityGuids":["guid1","guid2"]}
>  {code}
> when user doesn't have authorisation on either of guid1 or guid2 , the bulk 
> entity call fails with 403. 
> bulk api _v2/entity/bulk_ to retrieve a list of entities identified by its 
> guids.
> This bulk api fails with 403 if some guids belong to entities on which user 
> is *unauthorized* and other guids belong to entities on which user is 
> *authorized*.



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


[jira] [Updated] (ATLAS-3855) Bulk entity tag association and bulk api enhancement

2020-06-25 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3855:
--
Component/s:  atlas-core

> Bulk entity tag association and bulk api enhancement
> 
>
> Key: ATLAS-3855
> URL: https://issues.apache.org/jira/browse/ATLAS-3855
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.1.0
>
>
> API : /api/atlas/v2/entity/bulk/classification
> Body :
> {code:java}
> {"classification":{"typeName":"PII","attributes":{},"propagate":true,"removePropagationsOnEntityDelete":false,"validityPeriods":[]},"entityGuids":["guid1","guid2"]}
>  {code}
> when user doesn't have authorisation on either of guid1 or guid2 , the bulk 
> entity call fails with 403. 
> bulk api _v2/entity/bulk_ to retrieve a list of entities identified by its 
> guids.
> This bulk api fails with 403 if some guids belong to entities on which user 
> is *unauthorized* and other guids belong to entities on which user is 
> *authorized*.



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


[jira] [Updated] (ATLAS-3855) Bulk entity tag association and bulk api enhancement

2020-06-25 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3855:
--
Fix Version/s: 2.1.0

> Bulk entity tag association and bulk api enhancement
> 
>
> Key: ATLAS-3855
> URL: https://issues.apache.org/jira/browse/ATLAS-3855
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.1.0
>
>
> API : /api/atlas/v2/entity/bulk/classification
> Body :
> {code:java}
> {"classification":{"typeName":"PII","attributes":{},"propagate":true,"removePropagationsOnEntityDelete":false,"validityPeriods":[]},"entityGuids":["guid1","guid2"]}
>  {code}
> when user doesn't have authorisation on either of guid1 or guid2 , the bulk 
> entity call fails with 403. 
> bulk api _v2/entity/bulk_ to retrieve a list of entities identified by its 
> guids.
> This bulk api fails with 403 if some guids belong to entities on which user 
> is *unauthorized* and other guids belong to entities on which user is 
> *authorized*.



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


[jira] [Updated] (ATLAS-3855) Bulk entity tag association and bulk api enhancement

2020-06-25 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3855:
--
Labels: api-change  (was: )

> Bulk entity tag association and bulk api enhancement
> 
>
> Key: ATLAS-3855
> URL: https://issues.apache.org/jira/browse/ATLAS-3855
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>  Labels: api-change
> Fix For: 2.1.0
>
>
> API : /api/atlas/v2/entity/bulk/classification
> Body :
> {code:java}
> {"classification":{"typeName":"PII","attributes":{},"propagate":true,"removePropagationsOnEntityDelete":false,"validityPeriods":[]},"entityGuids":["guid1","guid2"]}
>  {code}
> when user doesn't have authorisation on either of guid1 or guid2 , the bulk 
> entity call fails with 403. 
> bulk api _v2/entity/bulk_ to retrieve a list of entities identified by its 
> guids.
> This bulk api fails with 403 if some guids belong to entities on which user 
> is *unauthorized* and other guids belong to entities on which user is 
> *authorized*.



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


[jira] [Resolved] (ATLAS-3856) Create new entity typeDefs for Apache Ozone

2020-06-25 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian resolved ATLAS-3856.
---
Resolution: Fixed

> Create new entity typeDefs for Apache Ozone
> ---
>
> Key: ATLAS-3856
> URL: https://issues.apache.org/jira/browse/ATLAS-3856
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: 
> ATLAS-3856-Create-new-entity-typeDefs-for-Apache-Ozone-v0.patch
>
>
> Add following ozone typeDefs to Atlas models
>  * Ozone volume
>  * Ozone bucket
>  * Ozone key



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


[jira] [Updated] (ATLAS-3856) Create new entity typeDefs for Apache Ozone

2020-06-25 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3856:
--
Fix Version/s: 2.1.0

> Create new entity typeDefs for Apache Ozone
> ---
>
> Key: ATLAS-3856
> URL: https://issues.apache.org/jira/browse/ATLAS-3856
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: 
> ATLAS-3856-Create-new-entity-typeDefs-for-Apache-Ozone-v0.patch
>
>
> Add following ozone typeDefs to Atlas models
>  * Ozone volume
>  * Ozone bucket
>  * Ozone key



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


[jira] [Updated] (ATLAS-3863) Avoid re-evaluating tag propagation when deleting relationship (edge)

2020-06-24 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3863:
--
Description: 
Tag propagation is re-evaluated every time when a relationship (edge) is 
deleted.

Removal of propagated classifications is controlled at the assignment time to 
an entity:

!image-2020-06-24-12-51-38-941.png|width=716,height=272!

 
 * {color:#172b4d}Remove propagation on entity delete - *TRUE :* {color}
 ** _Propagated classifications (to all downstream entities) will be removed 
when the source entity where the classification is originally assigned is 
deleted._

 
 * Remove propagation on entity delete - *FALSE :* 
 ** _Propagated classifications (to all downstream entities) will *not* be 
removed when the          source entity where the classification is originally 
assigned is deleted._

 

There is no need to revaluate tag propagation during relationship (edge) 
deletion since removal of tag propagation depends on the above config

 

*Significant performance improvement observed: 83% performance improvement 
seen.*

Deleting a hive_table entity (with 44 columns and 16 propagated classifications)

{{Before patch : 279 secs (4 mins, 39 secs) }}

{{After patch  : 46.92 secs}}

 
 

  was:
Tag propagation is re-evaluated every time when a relationship (edge) is 
deleted.

Removal of propagated classifications is controlled at the assignment time to 
an entity:

!image-2020-06-24-12-51-38-941.png|width=716,height=272!

 
 * {color:#172b4d}Remove propagation on entity delete - *TRUE :* {color}
 ** _Propagated classifications (to all downstream entities) will be removed 
when the source entity where the classification is originally assigned is 
deleted._

 
 * Remove propagation on entity delete - *FALSE :* 
 ** _Propagated classifications (to all downstream entities) will *not* be 
removed when the          source entity where the classification is originally 
assigned is deleted._

 

There is no need to revaluate tag propagation during relationship (edge) 
deletion since removal of tag propagation depends on the above config.


> Avoid re-evaluating tag propagation when deleting relationship (edge)
> -
>
> Key: ATLAS-3863
> URL: https://issues.apache.org/jira/browse/ATLAS-3863
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>  Labels: classification, tagpropagation
> Fix For: 2.1.0
>
> Attachments: ATLAS-3863.001.patch, image-2020-06-24-12-51-38-941.png
>
>
> Tag propagation is re-evaluated every time when a relationship (edge) is 
> deleted.
> Removal of propagated classifications is controlled at the assignment time to 
> an entity:
> !image-2020-06-24-12-51-38-941.png|width=716,height=272!
>  
>  * {color:#172b4d}Remove propagation on entity delete - *TRUE :* {color}
>  ** _Propagated classifications (to all downstream entities) will be removed 
> when the source entity where the classification is originally assigned is 
> deleted._
>  
>  * Remove propagation on entity delete - *FALSE :* 
>  ** _Propagated classifications (to all downstream entities) will *not* be 
> removed when the          source entity where the classification is 
> originally assigned is deleted._
>  
> There is no need to revaluate tag propagation during relationship (edge) 
> deletion since removal of tag propagation depends on the above config
>  
> *Significant performance improvement observed: 83% performance improvement 
> seen.*
> Deleting a hive_table entity (with 44 columns and 16 propagated 
> classifications)
> {{Before patch : 279 secs (4 mins, 39 secs) }}
> {{After patch  : 46.92 secs}}
>  
>  



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


[jira] [Updated] (ATLAS-3863) Avoid re-evaluating tag propagation when deleting relationship (edge)

2020-06-24 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3863:
--
Attachment: ATLAS-3863.001.patch

> Avoid re-evaluating tag propagation when deleting relationship (edge)
> -
>
> Key: ATLAS-3863
> URL: https://issues.apache.org/jira/browse/ATLAS-3863
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>  Labels: classification, tagpropagation
> Fix For: 2.1.0
>
> Attachments: ATLAS-3863.001.patch, image-2020-06-24-12-51-38-941.png
>
>
> Tag propagation is re-evaluated every time when a relationship (edge) is 
> deleted.
> Removal of propagated classifications is controlled at the assignment time to 
> an entity:
> !image-2020-06-24-12-51-38-941.png|width=716,height=272!
>  
>  * {color:#172b4d}Remove propagation on entity delete - *TRUE :* {color}
>  ** _Propagated classifications (to all downstream entities) will be removed 
> when the source entity where the classification is originally assigned is 
> deleted._
>  
>  * Remove propagation on entity delete - *FALSE :* 
>  ** _Propagated classifications (to all downstream entities) will *not* be 
> removed when the          source entity where the classification is 
> originally assigned is deleted._
>  
> There is no need to revaluate tag propagation during relationship (edge) 
> deletion since removal of tag propagation depends on the above config.



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


[jira] [Updated] (ATLAS-3863) Avoid re-evaluating tag propagation when deleting relationship (edge)

2020-06-24 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3863:
--
Labels: classification tagpropagation  (was: )

> Avoid re-evaluating tag propagation when deleting relationship (edge)
> -
>
> Key: ATLAS-3863
> URL: https://issues.apache.org/jira/browse/ATLAS-3863
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>  Labels: classification, tagpropagation
> Fix For: 2.1.0
>
> Attachments: image-2020-06-24-12-51-38-941.png
>
>
> Tag propagation is re-evaluated every time when a relationship (edge) is 
> deleted.
> Removal of propagated classifications is controlled at the assignment time to 
> an entity:
> !image-2020-06-24-12-51-38-941.png|width=716,height=272!
>  
>  * {color:#172b4d}Remove propagation on entity delete - *TRUE :* {color}
>  ** _Propagated classifications (to all downstream entities) will be removed 
> when the source entity where the classification is originally assigned is 
> deleted._
>  
>  * Remove propagation on entity delete - *FALSE :* 
>  ** _Propagated classifications (to all downstream entities) will *not* be 
> removed when the          source entity where the classification is 
> originally assigned is deleted._
>  
> There is no need to revaluate tag propagation during relationship (edge) 
> deletion since removal of tag propagation depends on the above config.



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


[jira] [Updated] (ATLAS-3863) Avoid re-evaluating tag propagation when deleting relationship (edge)

2020-06-24 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3863:
--
Description: 
Tag propagation is re-evaluated every time when a relationship (edge) is 
deleted.

Removal of propagated classifications is controlled at the assignment time to 
an entity:

!image-2020-06-24-12-51-38-941.png|width=716,height=272!

 
 * {color:#172b4d}Remove propagation on entity delete - *TRUE :* {color}
 ** _Propagated classifications (to all downstream entities) will be removed 
when the source entity where the classification is originally assigned is 
deleted._

 
 * Remove propagation on entity delete - *FALSE :* 
 ** _Propagated classifications (to all downstream entities) will *not* be 
removed when the          source entity where the classification is originally 
assigned is deleted._

 

There is no need to revaluate tag propagation during relationship (edge) 
deletion since removal of tag propagation depends on the above config.

  was:
Tag propagation is re-evaluated every time when a relationship (edge) is 
deleted.

 

Removal of propagated classifications is controlled at the assignment time to 
an entity:

!image-2020-06-24-12-51-38-941.png|width=716,height=272!

 
 * Remove propagation on entity delete - *TRUE :* 
_Propagated classifications (to all downstream entities) will be removed when 
the source entity where the classification is originally assigned is deleted._

 
 * Remove propagation on entity delete - *FALSE :* 

           _Propagated classifications (to all downstream entities) will *not* 
be removed when the          source entity where the classification is 
originally assigned is deleted._

 

There is no need to revaluate tag propagation during relationship deletion 
since removal of tag propagation depends on the above config.


> Avoid re-evaluating tag propagation when deleting relationship (edge)
> -
>
> Key: ATLAS-3863
> URL: https://issues.apache.org/jira/browse/ATLAS-3863
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: image-2020-06-24-12-51-38-941.png
>
>
> Tag propagation is re-evaluated every time when a relationship (edge) is 
> deleted.
> Removal of propagated classifications is controlled at the assignment time to 
> an entity:
> !image-2020-06-24-12-51-38-941.png|width=716,height=272!
>  
>  * {color:#172b4d}Remove propagation on entity delete - *TRUE :* {color}
>  ** _Propagated classifications (to all downstream entities) will be removed 
> when the source entity where the classification is originally assigned is 
> deleted._
>  
>  * Remove propagation on entity delete - *FALSE :* 
>  ** _Propagated classifications (to all downstream entities) will *not* be 
> removed when the          source entity where the classification is 
> originally assigned is deleted._
>  
> There is no need to revaluate tag propagation during relationship (edge) 
> deletion since removal of tag propagation depends on the above config.



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


[jira] [Created] (ATLAS-3863) Avoid re-evaluating tag propagation when deleting relationship (edge)

2020-06-24 Thread Sarath Subramanian (Jira)
Sarath Subramanian created ATLAS-3863:
-

 Summary: Avoid re-evaluating tag propagation when deleting 
relationship (edge)
 Key: ATLAS-3863
 URL: https://issues.apache.org/jira/browse/ATLAS-3863
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 2.1.0
 Attachments: image-2020-06-24-12-51-38-941.png

Tag propagation is re-evaluated every time when a relationship (edge) is 
deleted.

 

Removal of propagated classifications is controlled at the assignment time to 
an entity:

!image-2020-06-24-12-51-38-941.png|width=716,height=272!

 
 * Remove propagation on entity delete - *TRUE :* 
_Propagated classifications (to all downstream entities) will be removed when 
the source entity where the classification is originally assigned is deleted._

 
 * Remove propagation on entity delete - *FALSE :* 

           _Propagated classifications (to all downstream entities) will *not* 
be removed when the          source entity where the classification is 
originally assigned is deleted._

 

There is no need to revaluate tag propagation during relationship deletion 
since removal of tag propagation depends on the above config.



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


[jira] [Updated] (ATLAS-3652) Quick Search: API requirement for GET request on multiple entity types

2020-06-24 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3652:
--
Labels: quicksearch  (was: )

> Quick Search: API requirement for GET request on multiple entity types
> --
>
> Key: ATLAS-3652
> URL: https://issues.apache.org/jira/browse/ATLAS-3652
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: quicksearch
> Fix For: 2.1.0
>
>
> Need an API that can be used to GET information of multiple selected entity 
> types. Currently it seems to support GET request for
>  # One type (typeName=someType)\{by specifying typeName in the call},
> OR 
>  # All types (typeName= )\{by leaving out typeName empty}.
>  
> Need an API that works for multiple selected types while also returning the 
> aggregationMetrics in the responseJSON as opposed to the POST call(where the 
> aggregationMetrics is left out as empty).
>  



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


[jira] [Updated] (ATLAS-3652) Quick Search: API requirement for GET request on multiple entity types

2020-06-24 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3652:
--
Fix Version/s: 2.1.0

> Quick Search: API requirement for GET request on multiple entity types
> --
>
> Key: ATLAS-3652
> URL: https://issues.apache.org/jira/browse/ATLAS-3652
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> Need an API that can be used to GET information of multiple selected entity 
> types. Currently it seems to support GET request for
>  # One type (typeName=someType)\{by specifying typeName in the call},
> OR 
>  # All types (typeName= )\{by leaving out typeName empty}.
>  
> Need an API that works for multiple selected types while also returning the 
> aggregationMetrics in the responseJSON as opposed to the POST call(where the 
> aggregationMetrics is left out as empty).
>  



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


[jira] [Updated] (ATLAS-3652) Quick Search: API requirement for GET request on multiple entity types

2020-06-24 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3652:
--
Affects Version/s: 2.0.0

> Quick Search: API requirement for GET request on multiple entity types
> --
>
> Key: ATLAS-3652
> URL: https://issues.apache.org/jira/browse/ATLAS-3652
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> Need an API that can be used to GET information of multiple selected entity 
> types. Currently it seems to support GET request for
>  # One type (typeName=someType)\{by specifying typeName in the call},
> OR 
>  # All types (typeName= )\{by leaving out typeName empty}.
>  
> Need an API that works for multiple selected types while also returning the 
> aggregationMetrics in the responseJSON as opposed to the POST call(where the 
> aggregationMetrics is left out as empty).
>  



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


[jira] [Updated] (ATLAS-3652) Quick Search: API requirement for GET request on multiple entity types

2020-06-24 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3652:
--
Component/s:  atlas-core

> Quick Search: API requirement for GET request on multiple entity types
> --
>
> Key: ATLAS-3652
> URL: https://issues.apache.org/jira/browse/ATLAS-3652
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> Need an API that can be used to GET information of multiple selected entity 
> types. Currently it seems to support GET request for
>  # One type (typeName=someType)\{by specifying typeName in the call},
> OR 
>  # All types (typeName= )\{by leaving out typeName empty}.
>  
> Need an API that works for multiple selected types while also returning the 
> aggregationMetrics in the responseJSON as opposed to the POST call(where the 
> aggregationMetrics is left out as empty).
>  



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


[jira] [Updated] (ATLAS-3845) Audit API returns the audit information for an unauthorised entity

2020-06-22 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3845:
--
Labels: audit  (was: )

> Audit API  returns the audit information for an unauthorised entity
> ---
>
> Key: ATLAS-3845
> URL: https://issues.apache.org/jira/browse/ATLAS-3845
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>  Labels: audit
> Fix For: 2.1.0
>
>




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


[jira] [Updated] (ATLAS-3845) Audit API returns the audit information for an unauthorised entity

2020-06-22 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3845:
--
Affects Version/s: (was: 3.0.0)
   2.0.0

> Audit API  returns the audit information for an unauthorised entity
> ---
>
> Key: ATLAS-3845
> URL: https://issues.apache.org/jira/browse/ATLAS-3845
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>




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


[jira] [Updated] (ATLAS-3845) Audit API returns the audit information for an unauthorised entity

2020-06-22 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3845:
--
Component/s:  atlas-core

> Audit API  returns the audit information for an unauthorised entity
> ---
>
> Key: ATLAS-3845
> URL: https://issues.apache.org/jira/browse/ATLAS-3845
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.1.0
>
>




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


[jira] [Updated] (ATLAS-3845) Audit API returns the audit information for an unauthorised entity

2020-06-22 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3845:
--
Fix Version/s: 2.1.0

> Audit API  returns the audit information for an unauthorised entity
> ---
>
> Key: ATLAS-3845
> URL: https://issues.apache.org/jira/browse/ATLAS-3845
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.1.0
>
>




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


[jira] [Resolved] (ATLAS-3854) Upgrade Spring Security version to 4.2.16

2020-06-22 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian resolved ATLAS-3854.
---
Resolution: Fixed

> Upgrade Spring Security version to 4.2.16
> -
>
> Key: ATLAS-3854
> URL: https://issues.apache.org/jira/browse/ATLAS-3854
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 2.1.0
>
>
> Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x 
> prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed 
> null initialization vector with CBC Mode in the implementation of the 
> queryable text encryptor. A malicious user with access to the data that has 
> been encrypted using such an encryptor may be able to derive the unencrypted 
> values using a dictionary attack.
>  To resolve this need to upgrade Spring security to 4.2.16



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


[jira] [Updated] (ATLAS-3854) Upgrade Spring Security version to 4.2.16

2020-06-22 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3854:
--
Fix Version/s: 2.1.0

> Upgrade Spring Security version to 4.2.16
> -
>
> Key: ATLAS-3854
> URL: https://issues.apache.org/jira/browse/ATLAS-3854
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 2.1.0
>
>
> Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x 
> prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed 
> null initialization vector with CBC Mode in the implementation of the 
> queryable text encryptor. A malicious user with access to the data that has 
> been encrypted using such an encryptor may be able to derive the unencrypted 
> values using a dictionary attack.
>  To resolve this need to upgrade Spring security to 4.2.16



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


[jira] [Updated] (ATLAS-3854) Upgrade Spring Security version to 4.2.16

2020-06-22 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3854:
--
Component/s:  atlas-core

> Upgrade Spring Security version to 4.2.16
> -
>
> Key: ATLAS-3854
> URL: https://issues.apache.org/jira/browse/ATLAS-3854
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 2.1.0
>
>
> Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x 
> prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed 
> null initialization vector with CBC Mode in the implementation of the 
> queryable text encryptor. A malicious user with access to the data that has 
> been encrypted using such an encryptor may be able to derive the unencrypted 
> values using a dictionary attack.
>  To resolve this need to upgrade Spring security to 4.2.16



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


[jira] [Updated] (ATLAS-3854) Upgrade Spring Security version to 4.2.16

2020-06-22 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3854:
--
Affects Version/s: 2.0.0

> Upgrade Spring Security version to 4.2.16
> -
>
> Key: ATLAS-3854
> URL: https://issues.apache.org/jira/browse/ATLAS-3854
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x 
> prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed 
> null initialization vector with CBC Mode in the implementation of the 
> queryable text encryptor. A malicious user with access to the data that has 
> been encrypted using such an encryptor may be able to derive the unencrypted 
> values using a dictionary attack.
>  To resolve this need to upgrade Spring security to 4.2.16



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


[jira] [Created] (ATLAS-3836) Create new entity types for Apache Ozone and update hive hook to handle reference to Ozone path

2020-06-10 Thread Sarath Subramanian (Jira)
Sarath Subramanian created ATLAS-3836:
-

 Summary: Create new entity types for Apache Ozone and update hive 
hook to handle reference to Ozone path
 Key: ATLAS-3836
 URL: https://issues.apache.org/jira/browse/ATLAS-3836
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 2.1.0


Apache Ozone is the new object store for Hadoop - 
[https://hadoop.apache.org/ozone/]

Apache Atlas needs to add entity types to support creation of Ozone entities. 
Hive hook should also be updated to create lineage between ozone entities and 
hive tables (for EXTERNAL TABLE)



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


[jira] [Updated] (ATLAS-3826) Basic search not using index query for string tokenized attributes

2020-06-08 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3826:
--
Labels: BasicSearch  (was: )

> Basic search not using index query for string tokenized attributes
> --
>
> Key: ATLAS-3826
> URL: https://issues.apache.org/jira/browse/ATLAS-3826
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0
>
>
> Basic search not using index query for string tokenized attributes. 
> The following string tokenized attributes:
> {code:java}
> Asset.__s_name
>  Asset.__s_owner
>  Asset.__s_displayName
>  Asset.__s_userDescription
>  _s__createdBy
>  _s__modifiedBy{code}
>  
> uses graph query and this might be expensive when there are large number of 
> entities in the graph. String tokenized attributes should use index query for 
> faster performance.
>  



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


[jira] [Updated] (ATLAS-3826) Basic search not using index query for string tokenized attributes

2020-06-08 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3826:
--
Description: 
Basic search not using index query for string tokenized attributes. 

The following string tokenized attributes:
{code:java}
Asset.__s_name
 Asset.__s_owner
 Asset.__s_displayName
 Asset.__s_userDescription
 _s__createdBy
 _s__modifiedBy{code}
 

uses graph query and this might be expensive when there are large number of 
entities in the graph. String tokenized attributes should use index query for 
faster performance.

 

  was:
Basic search not using index query for string tokenized attributes. 

The following string tokenized attributes:
Asset.__s_name
Asset.__s_owner
Asset.__s_displayName
Asset.__s_userDescription
__s___createdBy
__s___modifiedBy
 

uses graph query and this might be expensive when there are large number of 
entities in the graph. String tokenized attributes should use index query for 
faster performance.

 


> Basic search not using index query for string tokenized attributes
> --
>
> Key: ATLAS-3826
> URL: https://issues.apache.org/jira/browse/ATLAS-3826
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
>
> Basic search not using index query for string tokenized attributes. 
> The following string tokenized attributes:
> {code:java}
> Asset.__s_name
>  Asset.__s_owner
>  Asset.__s_displayName
>  Asset.__s_userDescription
>  _s__createdBy
>  _s__modifiedBy{code}
>  
> uses graph query and this might be expensive when there are large number of 
> entities in the graph. String tokenized attributes should use index query for 
> faster performance.
>  



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


[jira] [Created] (ATLAS-3826) Basic search not using index query for string tokenized attributes

2020-06-08 Thread Sarath Subramanian (Jira)
Sarath Subramanian created ATLAS-3826:
-

 Summary: Basic search not using index query for string tokenized 
attributes
 Key: ATLAS-3826
 URL: https://issues.apache.org/jira/browse/ATLAS-3826
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 2.1.0


Basic search not using index query for string tokenized attributes. 

The following string tokenized attributes:
Asset.__s_name
Asset.__s_owner
Asset.__s_displayName
Asset.__s_userDescription
__s___createdBy
__s___modifiedBy
 

uses graph query and this might be expensive when there are large number of 
entities in the graph. String tokenized attributes should use index query for 
faster performance.

 



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


[jira] [Commented] (ATLAS-3824) update README.txt to replace earlier version references to 2.1.0

2020-06-03 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3824:
---

+1. Thanks [~madhan]

> update README.txt to replace earlier version references to 2.1.0
> 
>
> Key: ATLAS-3824
> URL: https://issues.apache.org/jira/browse/ATLAS-3824
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3824.patch
>
>
> Update references to earlier version in README.txt with 2.1.0



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


[jira] [Updated] (ATLAS-3780) Change 'Status' from Classification System Attributes to EntityStatus

2020-06-01 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3780:
--
Labels: BasicSearch  (was: )

> Change 'Status' from Classification System Attributes to EntityStatus
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
> Attachments: Screen Shot 2020-05-05 at 4.40.40 PM.png
>
>




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


[jira] [Updated] (ATLAS-3780) Change 'Status' from Classification System Attributes to EntityStatus

2020-06-01 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3780:
--
Fix Version/s: 3.0.0
   2.1.0

> Change 'Status' from Classification System Attributes to EntityStatus
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: Screen Shot 2020-05-05 at 4.40.40 PM.png
>
>




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


[jira] [Updated] (ATLAS-3780) Change 'Status' from Classification System Attributes to EntityStatus

2020-06-01 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3780:
--
Affects Version/s: 2.0.0

> Change 'Status' from Classification System Attributes to EntityStatus
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Attachments: Screen Shot 2020-05-05 at 4.40.40 PM.png
>
>




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


[jira] [Updated] (ATLAS-3806) Classifications information missing in notification events during entity create/update

2020-05-31 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3806:
--
Affects Version/s: 2.0.0

> Classifications information missing in notification events during entity 
> create/update
> --
>
> Key: ATLAS-3806
> URL: https://issues.apache.org/jira/browse/ATLAS-3806
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3806.patch
>
>




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


[jira] [Commented] (ATLAS-3803) Update tag propagation to NONE for relationshipDefs in aws_s3_v2 and azure_adls_gen2 models

2020-05-20 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3803:
---

[^ATLAS-3803.002.patch] updates azure adls models realtionshipdefs (tag 
propagation to NONE) - *adls_gen2_account_containers* and 
*adls_gen2_parent_children*

> Update tag propagation to NONE for relationshipDefs in aws_s3_v2 and 
> azure_adls_gen2 models
> ---
>
> Key: ATLAS-3803
> URL: https://issues.apache.org/jira/browse/ATLAS-3803
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3803.001.patch, ATLAS-3803.002.patch
>
>
> The tag propagation value for AWS S3 model between "aws_s3_v2_container" and 
> "aws_s3_v2_contained" is ONE_TO_TWO. This change is to change the default 
> propagation direction to NONE.



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


[jira] [Updated] (ATLAS-3803) Update tag propagation to NONE for relationshipDefs in aws_s3_v2 and azure_adls_gen2 models

2020-05-20 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3803:
--
Attachment: ATLAS-3803.002.patch

> Update tag propagation to NONE for relationshipDefs in aws_s3_v2 and 
> azure_adls_gen2 models
> ---
>
> Key: ATLAS-3803
> URL: https://issues.apache.org/jira/browse/ATLAS-3803
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3803.001.patch, ATLAS-3803.002.patch
>
>
> The tag propagation value for AWS S3 model between "aws_s3_v2_container" and 
> "aws_s3_v2_contained" is ONE_TO_TWO. This change is to change the default 
> propagation direction to NONE.



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


[jira] [Updated] (ATLAS-3803) Update tag propagation to NONE for relationshipDefs in aws_s3_v2 and azure_adls_gen2 models

2020-05-20 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3803:
--
Summary: Update tag propagation to NONE for relationshipDefs in aws_s3_v2 
and azure_adls_gen2 models  (was: Update tag propagation to NONE between 
aws_s3_v2_container and aws_s3_v2_contained type)

> Update tag propagation to NONE for relationshipDefs in aws_s3_v2 and 
> azure_adls_gen2 models
> ---
>
> Key: ATLAS-3803
> URL: https://issues.apache.org/jira/browse/ATLAS-3803
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3803.001.patch, ATLAS-3803.002.patch
>
>
> The tag propagation value for AWS S3 model between "aws_s3_v2_container" and 
> "aws_s3_v2_contained" is ONE_TO_TWO. This change is to change the default 
> propagation direction to NONE.



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


[jira] [Updated] (ATLAS-3803) Update tag propagation to NONE between aws_s3_v2_container and aws_s3_v2_contained type

2020-05-20 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3803:
--
Attachment: ATLAS-3803.001.patch

> Update tag propagation to NONE between aws_s3_v2_container and 
> aws_s3_v2_contained type
> ---
>
> Key: ATLAS-3803
> URL: https://issues.apache.org/jira/browse/ATLAS-3803
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3803.001.patch
>
>
> The tag propagation value for AWS S3 model between "aws_s3_v2_container" and 
> "aws_s3_v2_contained" is ONE_TO_TWO. This change is to change the default 
> propagation direction to NONE.



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


[jira] [Created] (ATLAS-3803) Update tag propagation to NONE between aws_s3_v2_container and aws_s3_v2_contained type

2020-05-20 Thread Sarath Subramanian (Jira)
Sarath Subramanian created ATLAS-3803:
-

 Summary: Update tag propagation to NONE between 
aws_s3_v2_container and aws_s3_v2_contained type
 Key: ATLAS-3803
 URL: https://issues.apache.org/jira/browse/ATLAS-3803
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 2.1.0


The tag propagation value for AWS S3 model between "aws_s3_v2_container" and 
"aws_s3_v2_contained" is ONE_TO_TWO. This change is to change the default 
propagation direction to NONE.



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


[jira] [Updated] (ATLAS-3788) BasicSearch: Classification with System attribute(indexed) filters has pagination issue

2020-05-15 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3788:
--
Labels: BasicSearch  (was: )

> BasicSearch: Classification with System attribute(indexed) filters has 
> pagination issue
> ---
>
> Key: ATLAS-3788
> URL: https://issues.apache.org/jira/browse/ATLAS-3788
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0
>
>
> When selecting ALL_CLASSIFICATION_TYPES, with system attribute Created Time < 
> currentTimeStamp , it results to less or zero number of entities than actual.



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


[jira] [Updated] (ATLAS-3788) BasicSearch: Classification with System attribute(indexed) filters has pagination issue

2020-05-15 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3788:
--
Component/s:  atlas-core

> BasicSearch: Classification with System attribute(indexed) filters has 
> pagination issue
> ---
>
> Key: ATLAS-3788
> URL: https://issues.apache.org/jira/browse/ATLAS-3788
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> When selecting ALL_CLASSIFICATION_TYPES, with system attribute Created Time < 
> currentTimeStamp , it results to less or zero number of entities than actual.



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


[jira] [Updated] (ATLAS-3788) BasicSearch: Classification with System attribute(indexed) filters has pagination issue

2020-05-15 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3788:
--
Affects Version/s: 2.0.0

> BasicSearch: Classification with System attribute(indexed) filters has 
> pagination issue
> ---
>
> Key: ATLAS-3788
> URL: https://issues.apache.org/jira/browse/ATLAS-3788
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>
> When selecting ALL_CLASSIFICATION_TYPES, with system attribute Created Time < 
> currentTimeStamp , it results to less or zero number of entities than actual.



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


[jira] [Updated] (ATLAS-3788) BasicSearch: Classification with System attribute(indexed) filters has pagination issue

2020-05-15 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3788:
--
Fix Version/s: 2.1.0

> BasicSearch: Classification with System attribute(indexed) filters has 
> pagination issue
> ---
>
> Key: ATLAS-3788
> URL: https://issues.apache.org/jira/browse/ATLAS-3788
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0
>
>
> When selecting ALL_CLASSIFICATION_TYPES, with system attribute Created Time < 
> currentTimeStamp , it results to less or zero number of entities than actual.



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


[jira] [Updated] (ATLAS-3800) AWS scheme is missing the aws account id that contains the S3 bucket

2020-05-15 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3800:
--
Fix Version/s: 2.1.0

> AWS scheme is missing the aws account id that contains the S3 bucket
> 
>
> Key: ATLAS-3800
> URL: https://issues.apache.org/jira/browse/ATLAS-3800
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Ameer Assi
>Priority: Minor
> Fix For: 2.1.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We are using Atlas models in our product.
> the product gives scan capabilities for customer's S3 in AWS.
> when scan result shown based on the model, it is missing for which account 
> this bucket belongs. so it will be easy to access the account and review the 
> scanned information by the customer.
>  
> https://github.com/apache/atlas/pull/98



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


[jira] [Updated] (ATLAS-3800) AWS scheme is missing the aws account id that contains the S3 bucket

2020-05-15 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3800:
--
Affects Version/s: 2.0.0

> AWS scheme is missing the aws account id that contains the S3 bucket
> 
>
> Key: ATLAS-3800
> URL: https://issues.apache.org/jira/browse/ATLAS-3800
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Ameer Assi
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We are using Atlas models in our product.
> the product gives scan capabilities for customer's S3 in AWS.
> when scan result shown based on the model, it is missing for which account 
> this bucket belongs. so it will be easy to access the account and review the 
> scanned information by the customer.
>  
> https://github.com/apache/atlas/pull/98



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


[jira] [Updated] (ATLAS-3800) AWS scheme is missing the aws account id that contains the S3 bucket

2020-05-15 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3800:
--
Component/s:  atlas-core

> AWS scheme is missing the aws account id that contains the S3 bucket
> 
>
> Key: ATLAS-3800
> URL: https://issues.apache.org/jira/browse/ATLAS-3800
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Reporter: Ameer Assi
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We are using Atlas models in our product.
> the product gives scan capabilities for customer's S3 in AWS.
> when scan result shown based on the model, it is missing for which account 
> this bucket belongs. so it will be easy to access the account and review the 
> scanned information by the customer.
>  
> https://github.com/apache/atlas/pull/98



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


[jira] [Commented] (ATLAS-3796) Migration Import Display: StatusReporter Does not Remove Processed Items

2020-05-13 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian commented on ATLAS-3796:
---

+1 for the patch 
[^ATLAS-3796-Status-Reporter-processed-set-cleanup.patch]Thanks [~amestry].

> Migration Import Display: StatusReporter Does not Remove Processed Items
> 
>
> Key: ATLAS-3796
> URL: https://issues.apache.org/jira/browse/ATLAS-3796
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3796-Status-Reporter-processed-set-cleanup.patch
>
>
> *Background*
> _Migration Import_ implementation introduced _StatusReporter_. The class 
> maintains GUIDs of entities that are to be processed and entities that are 
> processed. When the entity is marked as processed, it needs to be removed 
> from the processed set.
> *Steps to Duplicate*
> _Pre-requisites_
> Large migration import dataset (over 50 M entities).
> _Steps to Duplicate_
>  * Start importing the dataset.
>  * After over 60%, the Atlas server will crash with out of memory exception.
> _Expected results_: Migration Import should continue without problems.
> _Actual results_: Atlas server crashes with out of memory exception, hprof 
> dump indicates large number of items allocated by 
> _StatusReporter.processedSet_.
> _Additional information_: This bug does not affect status reporting.
> _Work around_: Resume migration import. It will continue without problems.



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


[jira] [Updated] (ATLAS-3783) DSL query search should return results for both the relationship edge directions

2020-05-11 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3783:
--
Labels: AdvancedSearch DSL  (was: )

> DSL query search should return results for both the relationship edge 
> directions 
> -
>
> Key: ATLAS-3783
> URL: https://issues.apache.org/jira/browse/ATLAS-3783
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>  Labels: AdvancedSearch, DSL
>
> eg;hive_column where table.name="employee" doesn't give any results for 
> hive_column whereas 
> hive_table where columns.name="eid" gives results for hive_table.



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


[jira] [Updated] (ATLAS-3783) DSL query search should return results for both the relationship edge directions

2020-05-11 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3783:
--
Fix Version/s: 2.1.0

> DSL query search should return results for both the relationship edge 
> directions 
> -
>
> Key: ATLAS-3783
> URL: https://issues.apache.org/jira/browse/ATLAS-3783
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>  Labels: AdvancedSearch, DSL
> Fix For: 2.1.0
>
>
> eg;hive_column where table.name="employee" doesn't give any results for 
> hive_column whereas 
> hive_table where columns.name="eid" gives results for hive_table.



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


[jira] [Updated] (ATLAS-3783) DSL query search should return results for both the relationship edge directions

2020-05-11 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3783:
--
Affects Version/s: (was: 3.0.0)
   2.0.0

> DSL query search should return results for both the relationship edge 
> directions 
> -
>
> Key: ATLAS-3783
> URL: https://issues.apache.org/jira/browse/ATLAS-3783
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>  Labels: AdvancedSearch, DSL
>
> eg;hive_column where table.name="employee" doesn't give any results for 
> hive_column whereas 
> hive_table where columns.name="eid" gives results for hive_table.



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


[jira] [Updated] (ATLAS-3783) DSL query search should return results for both the relationship edge directions

2020-05-11 Thread Sarath Subramanian (Jira)


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

Sarath Subramanian updated ATLAS-3783:
--
Component/s:  atlas-core

> DSL query search should return results for both the relationship edge 
> directions 
> -
>
> Key: ATLAS-3783
> URL: https://issues.apache.org/jira/browse/ATLAS-3783
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>
> eg;hive_column where table.name="employee" doesn't give any results for 
> hive_column whereas 
> hive_table where columns.name="eid" gives results for hive_table.



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


  1   2   3   4   5   6   7   8   9   10   >