[jira] [Updated] (ATLAS-4077) update Python client to work with Kerberos and 2.7

2021-01-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-4077:

Attachment: ATLAS-4077-3.patch

> update Python client to work with Kerberos and 2.7
> --
>
> Key: ATLAS-4077
> URL: https://issues.apache.org/jira/browse/ATLAS-4077
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4077-3.patch, ATLAS-4077.patch
>
>
> Python client for Atlas introduced in ATLAS-3875 requires Python 3.6 or 
> above. It will help make the client available for Python 2.7 as well. Also, 
> the client should support Kerberos authentication.



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


[jira] [Created] (ATLAS-4097) update zookeeper download url for recent zookeeper version upgrade

2021-01-07 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-4097:
---

 Summary: update zookeeper download url for recent zookeeper 
version upgrade
 Key: ATLAS-4097
 URL: https://issues.apache.org/jira/browse/ATLAS-4097
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 3.0.0, 2.2.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Zookeeper version was updated from 3.4.6 to 3.5.7 in ATLAS-4017. URL to 
download zookeeper needs to be updated for this change, since Zookeeper 
download now has 'apache-' prefix in path, as shown below:
- 3.4.6: 
https://archive.apache.org/dist/zookeeper/zookeeper-3.4.6/zookeeper-3.4.6.tar.gz
 
- 3.5.7: 
https://archive.apache.org/dist/zookeeper/zookeeper-3.5.7/apache-zookeeper-3.5.7-bin.tar.gz
 



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


[jira] [Assigned] (ATLAS-4090) Fix circular import in Pyhon Client

2020-12-30 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj reassigned ATLAS-4090:
---

Assignee: Mariusz Górski

> Fix circular import in Pyhon Client
> ---
>
> Key: ATLAS-4090
> URL: https://issues.apache.org/jira/browse/ATLAS-4090
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mariusz Górski
>Assignee: Mariusz Górski
>Priority: Minor
>
> After PEP8 refactor circular import prevents client creation



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


[jira] [Assigned] (ATLAS-4089) Refactor Python Atlas client to PEP8

2020-12-28 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj reassigned ATLAS-4089:
---

Assignee: Mariusz Górski

> Refactor Python Atlas client to PEP8
> 
>
> Key: ATLAS-4089
> URL: https://issues.apache.org/jira/browse/ATLAS-4089
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Mariusz Górski
>Assignee: Mariusz Górski
>Priority: Minor
>
> To enable easier spotting bugs and enable code/workflow native to Python 
> developers, we should include python linter (flake8) and static type checking 
> (mypy) to the repo. This issue suggest reformatting python client code to 
> pep8 following discussion in https://reviews.apache.org/r/73097/
> By running flake8/mypy just once we can easily spot obvious issues and 
> reformat the code so it follows best-practices regarding Python development. 
> It also helps developers using Python dedicated IDE to work in more native 
> workflow.



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


[jira] [Assigned] (ATLAS-4080) Add admin metrics API in Atlas Python Client

2020-12-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj reassigned ATLAS-4080:
---

Assignee: Verdan Mahmood

> Add admin metrics API in Atlas Python Client
> 
>
> Key: ATLAS-4080
> URL: https://issues.apache.org/jira/browse/ATLAS-4080
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Verdan Mahmood
>Assignee: Verdan Mahmood
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Atlas Python client is missing critical admin metrics API, which is being 
> used by many places in our case for the counts of entities. 



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


[jira] [Created] (ATLAS-4077) update Python client to work with Kerberos and 2.7

2020-12-11 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-4077:
---

 Summary: update Python client to work with Kerberos and 2.7
 Key: ATLAS-4077
 URL: https://issues.apache.org/jira/browse/ATLAS-4077
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 2.1.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Python client for Atlas introduced in ATLAS-3875 requires Python 3.6 or above. 
It will help make the client available for Python 2.7 as well. Also, the client 
should support Kerberos authentication.



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


[jira] [Commented] (ATLAS-4048) Entity Creation: Updates to Business Metadata

2020-11-24 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-4048:
-

[~umesh.padashetty] - classifications and business-metadata attributes of an 
entity are not modified during REST API call to update the entity. Allowing 
this could cause unintentional removal of classifications and business-metadata 
- as API client's are likely to deal only with attributes that are known when 
the client was developed; hence wouldn't know about classifications and 
business-metadata which could be dynamically added to entities.

Note that if REST API call creates an entity, provided classifications and 
business-metadata will be assigned to the entity - as there is no risk of 
removing existing value.

Also, note that import operation replaces classifications and business-metadata 
on entities with the values specified in the import file. This is an expected 
behavior.

> Entity Creation: Updates to Business Metadata
> -
>
> Key: ATLAS-4048
> URL: https://issues.apache.org/jira/browse/ATLAS-4048
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-4048-Entity-Update-Businessmetada-changes.patch
>
>
> *Background*
> Business Metadata attributes provide a simple way to augment attributes to 
> existing entity types.
> Updating Business Metadata for existing entities via REST APIs did not happen 
> as the changes were not tracked when considering entity for update.
> *Steps to Duplicate*
> Setup:
>  * Create Business Metadata and add 3 attributes.
> Steps to duplicate:
>  # Via REST API, create an entity with 3 Business Metadata attributes. 
>  # From the web UI, load the entity where attributes have been added.
>  # Delete 1 attribute.
>  # Use entity update REST API to update the entity from step 1.
> Expected results: Entity will have all 3 attributes.
> Actual result: Entity will contain only 2 attributes that were present in 
> step 2.
>  *Root Cause*
> During entity creation flow, the Business Metadata attributes are not 
> considered when detecting if entity has changes. 
> Solution: Add a step to detect changes to Business Metadata attributes.



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


[jira] [Updated] (ATLAS-4016) Update authorization - "admin-audits" for retrieving admin audits

2020-11-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-4016:

Fix Version/s: 2.2.0
   3.0.0

> Update authorization - "admin-audits" for retrieving admin audits
> -
>
> Key: ATLAS-4016
> URL: https://issues.apache.org/jira/browse/ATLAS-4016
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-4016-V2.patch, ATLAS-4016.patch
>
>
>  
>   
>  For Atlas Admin Audits we need to add new privilege - "*admin-audits*"  for 
> authorization
> Similar permission needs to be updated in ranger atlas service-def .



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


[jira] [Resolved] (ATLAS-4011) Docker: While running Atlas Docker container, data should be stored on host

2020-11-05 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-4011.
-
Fix Version/s: 2.2.0
   3.0.0
   Resolution: Fixed

> Docker: While running Atlas Docker container, data should be stored on host
> ---
>
> Key: ATLAS-4011
> URL: https://issues.apache.org/jira/browse/ATLAS-4011
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jayendra Parab
>Assignee: Jayendra Parab
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Currently, if Atlas is started with Embedded Solr and HBase in Docker 
> container, the data is persisted inside the container. So if the container is 
> destroyed and a new container is started, then its old data is lost.
> The data directory should be mounted as a volume, so that data can be 
> restored across container destroy and restore.
> To achieve this, Solr data directory should be configurable and by default it 
> should be $ATLAS_HOME/data/solr. HBase and Kafka data directory is already 
> configured to $ATLAS_HOME/data



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


[jira] [Resolved] (ATLAS-4009) Atlas Build with -Pdist,embedded-hbase-solr option fails on master.

2020-10-27 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-4009.
-
Fix Version/s: 2.2.0
   3.0.0
 Assignee: Madhan Neethiraj
   Resolution: Fixed

Fix merged into master and branch-2.0 with following commits:

 
master branch:
{noformat}
Commit 34709f229b62ce054ae819917dff9aad4cc976b8 in atlas's branch 
refs/heads/master from Madhan Neethiraj
[ [https://gitbox.apache.org/repos/asf?p=atlas.git;h=34709f2] ]

ATLAS-4000: fixed incorrect pom.xml update in earlier commit - #3
{noformat}

branch-2.0 branch:
{noformat}
Commit 7789380ac44896baabcdacd3882fcc3aa650cd26 in atlas's branch 
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7789380 ]

ATLAS-4000: fixed incorrect pom.xml update in earlier commit - #3

(cherry picked from commit 34709f229b62ce054ae819917dff9aad4cc976b8)
{noformat}

 

 

> Atlas Build with -Pdist,embedded-hbase-solr  option fails on master. 
> -
>
> Key: ATLAS-4009
> URL: https://issues.apache.org/jira/browse/ATLAS-4009
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Screenshot from 2020-10-27 19-24-54.png
>
>
> * Atlas Build with -Pdist,embedded-hbase-solr option fails on master with 
> Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.0:copy (copy-hook) on 
> project storm-bridge: Unable to parse configuration of mojo 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.0:copy
>  
> {noformat}
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Atlas Server Build Tools 1.0  SUCCESS [  0.876 
> s]
> [INFO] apache-atlas 3.0.0-SNAPSHOT  SUCCESS [ 22.974 
> s]
> [INFO] Apache Atlas Integration ... SUCCESS [ 27.070 
> s]
> [INFO] Apache Atlas Test Utility Tools  SUCCESS [ 14.643 
> s]
> [INFO] Apache Atlas Common  SUCCESS [ 12.393 
> s]
> [INFO] Apache Atlas Client  SUCCESS [  1.135 
> s]
> [INFO] atlas-client-common  SUCCESS [  7.428 
> s]
> [INFO] atlas-client-v1  SUCCESS [  7.253 
> s]
> [INFO] Apache Atlas Server API  SUCCESS [  9.529 
> s]
> [INFO] Apache Atlas Notification .. SUCCESS [ 15.347 
> s]
> [INFO] atlas-client-v2  SUCCESS [  7.187 
> s]
> [INFO] Apache Atlas Graph Database Projects ... SUCCESS [  0.759 
> s]
> [INFO] Apache Atlas Graph Database API  SUCCESS [  6.837 
> s]
> [INFO] Graph Database Common Code . SUCCESS [  5.506 
> s]
> [INFO] Apache Atlas JanusGraph-HBase2 Module .. SUCCESS [  8.404 
> s]
> [INFO] Apache Atlas JanusGraph DB Impl  SUCCESS [ 19.948 
> s]
> [INFO] Apache Atlas Graph Database Implementation Dependencies SUCCESS [  
> 2.546 s]
> [INFO] Apache Atlas Authorization . SUCCESS [ 10.379 
> s]
> [INFO] Apache Atlas Repository  SUCCESS [ 41.996 
> s]
> [INFO] Apache Atlas UI  SUCCESS [ 47.226 
> s]
> [INFO] Apache Atlas New UI  SUCCESS [ 47.325 
> s]
> [INFO] Apache Atlas Web Application ... SUCCESS [01:37 
> min]
> [INFO] Apache Atlas Documentation . SUCCESS [ 14.091 
> s]
> [INFO] Apache Atlas FileSystem Model .. SUCCESS [  4.903 
> s]
> [INFO] Apache Atlas Plugin Classloader  SUCCESS [  8.600 
> s]
> [INFO] Apache Atlas Hive Bridge Shim .. SUCCESS [  9.450 
> s]
> [INFO] Apache Atlas Hive Bridge ... SUCCESS [ 25.791 
> s]
> [INFO] Apache Atlas Falcon Bridge Shim  SUCCESS [  7.541 
> s]
> [INFO] Apache Atlas Falcon Bridge . SUCCESS [ 10.681 
> s]
> [INFO] Apache Atlas Sqoop Bridge Shim . SUCCESS [  5.474 
> s]
> [INFO] Apache Atlas Sqoop Bridge .. SUCCESS [ 18.287 
> s]
> [INFO] Apache Atlas Storm Bridge Shim . SUCCESS [  5.192 
> s]
> [INFO] Apache Atlas Storm Bridge .. FAILURE [  6.924 
> s]
> [INFO] Apache Atlas Hbase Bridge Shim . SKIPPED
> [INFO] Apache Atlas Hbase Bridge .. SKIPPED
> [INFO] Apache HBase - Testing Util  SKIPPED
> [INFO] Apache Atlas Kafka Bridge .. SKIPPED
> [INFO] 

[jira] [Resolved] (ATLAS-3219) Implemented new serviceType Rest API

2020-10-26 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-3219.
-
Resolution: Duplicate

> Implemented new serviceType Rest API
> 
>
> Key: ATLAS-3219
> URL: https://issues.apache.org/jira/browse/ATLAS-3219
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
> Environment: all
>Reporter: Diego Marino Monetti
>Assignee: Diego Marino Monetti
>Priority: Major
> Fix For: trunk
>
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> This pull request supersedes the pull request ATLAS-3180.
> The new basic attribute serviceType, introduced by Atlas Team, has no use if 
> it is not searchable ina any way. This pull request solves this problem by 
> adding the following REST APIs.
> GET / typedef / servicetype / \{servicetype}
> GET / typedefs / headers? Servicetype = \{serviceType}
> GET / typedefs? Servicetype = \{servicetype}
> GET / enumdef / servicetype / \{servicetype}
> GET / entitydef / servicetype / \{servicetype}
> GET / structdef / servicetype / \{servicetype}
> GET / relationshipdef / servicetype / \{servicetype}
> DELETE / typedef / servicetype / \{servicetype}
> The APIs were tested on ATLAS 2.0 and on the new SNAPSHOT 3.0



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


[jira] [Updated] (ATLAS-3219) Implemented new serviceType Rest API

2020-10-26 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3219:

Fix Version/s: (was: trunk)

> Implemented new serviceType Rest API
> 
>
> Key: ATLAS-3219
> URL: https://issues.apache.org/jira/browse/ATLAS-3219
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
> Environment: all
>Reporter: Diego Marino Monetti
>Assignee: Diego Marino Monetti
>Priority: Major
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> This pull request supersedes the pull request ATLAS-3180.
> The new basic attribute serviceType, introduced by Atlas Team, has no use if 
> it is not searchable ina any way. This pull request solves this problem by 
> adding the following REST APIs.
> GET / typedef / servicetype / \{servicetype}
> GET / typedefs / headers? Servicetype = \{serviceType}
> GET / typedefs? Servicetype = \{servicetype}
> GET / enumdef / servicetype / \{servicetype}
> GET / entitydef / servicetype / \{servicetype}
> GET / structdef / servicetype / \{servicetype}
> GET / relationshipdef / servicetype / \{servicetype}
> DELETE / typedef / servicetype / \{servicetype}
> The APIs were tested on ATLAS 2.0 and on the new SNAPSHOT 3.0



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


[jira] [Comment Edited] (ATLAS-4000) update Jetty version to 9.4.31

2020-10-23 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj edited comment on ATLAS-4000 at 10/23/20, 4:24 PM:


[Patch in review board - refactoring of UTs, 
ITs|https://reviews.apache.org/r/72986/]


was (Author: madhan.neethiraj):
[Patch in review board|https://reviews.apache.org/r/72978/]

> update Jetty version to 9.4.31
> --
>
> Key: ATLAS-4000
> URL: https://issues.apache.org/jira/browse/ATLAS-4000
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4000-tests.patch, ATLAS-4000.patch
>
>
> Atlas currently uses Jetty version 9.2.12, which is about 4 years old. This 
> should be upgraded to a recent version - like 9.4.31.



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


[jira] [Updated] (ATLAS-4000) update Jetty version to 9.4.31

2020-10-23 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-4000:

Attachment: ATLAS-4000-tests.patch

> update Jetty version to 9.4.31
> --
>
> Key: ATLAS-4000
> URL: https://issues.apache.org/jira/browse/ATLAS-4000
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4000-tests.patch, ATLAS-4000.patch
>
>
> Atlas currently uses Jetty version 9.2.12, which is about 4 years old. This 
> should be upgraded to a recent version - like 9.4.31.



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


[jira] [Updated] (ATLAS-3999) Update build to avoid distro in multiple formats - tar.gz and dir

2020-10-23 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3999:

Fix Version/s: 2.2.0

> Update build to avoid distro in multiple formats - tar.gz and dir
> -
>
> Key: ATLAS-3999
> URL: https://issues.apache.org/jira/browse/ATLAS-3999
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3999.patch
>
>
> Atlas build generates distro in multiple formats - for example: tar.gz or zip 
> and a directory. To save build time and disk space, build should be updated 
> to only generate archives - .tar.gz or .zip, and avoid creating directories 
> with the same contents.



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


[jira] [Created] (ATLAS-4000) update Jetty version to 9.4.31

2020-10-20 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-4000:
---

 Summary: update Jetty version to 9.4.31
 Key: ATLAS-4000
 URL: https://issues.apache.org/jira/browse/ATLAS-4000
 Project: Atlas
  Issue Type: Improvement
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Atlas currently uses Jetty version 9.2.12, which is about 4 years old. This 
should be upgraded to a recent version - like 9.4.31.



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


[jira] [Created] (ATLAS-3999) Update build to avoid distro in multiple formats - tar.gz and dir

2020-10-20 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3999:
---

 Summary: Update build to avoid distro in multiple formats - tar.gz 
and dir
 Key: ATLAS-3999
 URL: https://issues.apache.org/jira/browse/ATLAS-3999
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Atlas build generates distro in multiple formats - for example: tar.gz or zip 
and a directory. To save build time and disk space, build should be updated to 
only generate archives - .tar.gz or .zip, and avoid creating directories with 
the same contents.



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


[jira] [Created] (ATLAS-3983) Update handling of special characters in query-value for index-search

2020-10-06 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3983:
---

 Summary: Update handling of special characters in query-value for 
index-search
 Key: ATLAS-3983
 URL: https://issues.apache.org/jira/browse/ATLAS-3983
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


When query-value contains special characters, {{+-&|!(){}[]^"~*?:\/}}, Atlas 
skips index-search and switches to graph-query, which could be expensive. 
Index-search can still be used by escaping the special characters with a 
backslash, per following Lucene documentation 
[here|https://lucene.apache.org/core/6_5_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#Escaping_Special_Characters]:

{noformat}
Escaping Special Characters
Lucene supports escaping special characters that are part of the query syntax. 
The current list special characters are

+ - && || ! ( ) { } [ ] ^ " ~ * ? : \ /

To escape these character use the \ before the character. For example to search 
for (1+1):2 use the query:

\(1\+1\)\:2
{noformat}



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


[jira] [Assigned] (ATLAS-1926) Search using entity and trait attributes - Explicit escaping by user if string has space,colon and other special characters.

2020-10-06 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj reassigned ATLAS-1926:
---

Assignee: Apoorv Naik

> Search using entity and trait attributes - Explicit escaping by user if 
> string has space,colon and other special characters.
> 
>
> Key: ATLAS-1926
> URL: https://issues.apache.org/jira/browse/ATLAS-1926
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha S
>Assignee: Apoorv Naik
>Priority: Minor
> Fix For: 0.8.2, 1.0.0
>
>
> Provided filter for description of entity
> {code}
> Description = topic or message queue
> {code}
> which threw 500 internal server error.
> On escaping spaces with "\" , like
> {code}
> Description = topic\ or\ message\ queue
> {code}
>  the expected entity was fetched.
> This happens with other special characters also.
> This requires users to explicitly escape characters which is not very user 
> friendly.



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


[jira] [Updated] (ATLAS-2013) Audit - add non-hbase, persistent audit repository

2020-10-04 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-2013:

Attachment: ATLAS-2013.patch

> Audit - add non-hbase, persistent audit repository
> --
>
> Key: ATLAS-2013
> URL: https://issues.apache.org/jira/browse/ATLAS-2013
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-2013.patch
>
>
> As per mailing list post on 2017-07-24:
> I was just reading ATLAS-1870 which related to default audit repositories. I 
> see the default is HBaseBasedAuditRepository, and that there is also 
> NoopEntityAuditRepository, and InMemoryEntityAuditRepository.
> I'm thinking that when Atlas is used in a non-hadoop oriented environment it 
> would be useful to have a non-hbase, persistent (helps a little with 
> compliance ) audit respository. Perhaps another RDB, or indeed in 
> solr/elastic search alongside Ranger's audit events.
> I'll raise a JIRA on this if it's felt useful & my understanding is correct
> Nigel.



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


[jira] [Assigned] (ATLAS-2013) Audit - add non-hbase, persistent audit repository

2020-10-04 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj reassigned ATLAS-2013:
---

Assignee: Madhan Neethiraj

> Audit - add non-hbase, persistent audit repository
> --
>
> Key: ATLAS-2013
> URL: https://issues.apache.org/jira/browse/ATLAS-2013
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Madhan Neethiraj
>Priority: Major
>
> As per mailing list post on 2017-07-24:
> I was just reading ATLAS-1870 which related to default audit repositories. I 
> see the default is HBaseBasedAuditRepository, and that there is also 
> NoopEntityAuditRepository, and InMemoryEntityAuditRepository.
> I'm thinking that when Atlas is used in a non-hadoop oriented environment it 
> would be useful to have a non-hbase, persistent (helps a little with 
> compliance ) audit respository. Perhaps another RDB, or indeed in 
> solr/elastic search alongside Ranger's audit events.
> I'll raise a JIRA on this if it's felt useful & my understanding is correct
> Nigel.



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


[jira] [Commented] (ATLAS-3906) “NoSuchMethodErrors” due to multiple versions of org.apache.curator:curator-client:jar

2020-09-14 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-3906:
-

[~Bing-ok] - thanks for the detailed description and the suggestions to address 
the issue. Upgrading version of org.apache.hadoop:hadoop-common from 3.1.1 to 
3.3.0 seems like a good option. Can you please submit a review with this fix?

> “NoSuchMethodErrors” due to multiple versions of 
> org.apache.curator:curator-client:jar
> --
>
> Key: ATLAS-3906
> URL: https://issues.apache.org/jira/browse/ATLAS-3906
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Bing-ok
>Priority: Major
>
> h1. Issue description
> Hi, there are multiple versions of _*org.apache.curator:curator-client*_ in 
> _*atlas/server-api*_. As shown in the following dependency tree, library  
> _*org.apache.curator:curator-client:2.12.0*_  is transitively introduced by 
> *_org.apache.hadoop:hadoop-auth:3.1.1_*, but has been managed to be version 
> *_4.0.1_*. 
> However, one method defined in shadowed version 
> _*org.apache.curator:curator-client:2.12.0*_ is referenced by client project 
> via *_org.apache.hadoop:hadoop-auth:3.1.1_*, but missing in the actually 
> loaded version _*org.apache.curator:curator-client:4.0.1*_.
> For instance, the following missing method(defined in 
> _*org.apache.curator:curator-client:2.12.0*_) is actually referenced by 
> _*atlas/server-api*_, which will introduce a runtime error(i.e., 
> "NoSuchMethodError") into _*atlas/server-api*_.
>  _*Missing method: org.codelibs.core.lang.StringUtil: java.lang.String 
> newStringUnsafe(char[])*_ is invoked by _*atlas/server-api*_ via the 
> following path:
> {noformat}
> paths--
>  getEntity(java.lang.String)> atlas\server-api\target\classes
>  java.lang.Object get(java.lang.Object)> 
> Repositories\org\apache\curator\curator-client\4.0.1\curator-client-4.0.1.jar
>  apply(java.lang.Object)> 
> Repositories\org\apache\curator\curator-framework\4.0.1\curator-framework-4.0.1.jar
>  apply(org.apache.curator.framework.api.CuratorListener)> 
> Repositories\org\apache\curator\curator-framework\4.0.1\curator-framework-4.0.1.jar
>  checkInterrupted(java.lang.Throwable)>{noformat}
> h1. Suggested fixing solutions
>  1. Upgrade dependency *_org.apache.hadoop:hadoop-common_* from _*3.1.1*_ to 
> *_3.3.0_*. Because the newer version 
> *_org.apache.hadoop:hadoop-common:3.3.0_* does not invoke the above missing 
> method, such upgrading can solve the problem.
>  2. Declare a direct dependency _*org.apache.curator:curator-client:2.12.0*_ 
> in the pom file of _*atlas/server-api*_, to override 
> _*org.apache.curator:curator-client*_'s managed version.
> 3. Use configuration attribute  to unify the version of 
> library _*org.apache.curator:curator-client*_ to be _*2.12.0*_ in 
> _*atlas/server-api*_'s pom file.
> Please let me know which solution do you prefer? I can submit a PR to fix it.
> Thank you very much for your attention.
>  Best regards,
> h1. Dependency tree
> {noformat}
> [INFO] org.apache.atlas:atlas-server-api:jar:3.0.0-SNAPSHOT
> [INFO] - org.apache.hadoop:hadoop-common:jar:3.1.1:compile
> [INFO] +- org.apache.hadoop:hadoop-auth:jar:3.1.1:compile
> [INFO] | - org.apache.curator:curator-framework:jar:4.0.1:compile (version 
> managed from 2.12.0)
> [INFO] | - _*(org.apache.curator:curator-client:jar:4.0.1:compile - version 
> managed from 2.12.0; omitted for duplicate)*_
> [INFO] - _*org.apache.curator:curator-client:jar:4.0.1:compile*_{noformat}



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


[jira] [Created] (ATLAS-3939) Add build profile for berkeleydb-solr

2020-09-11 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3939:
---

 Summary: Add build profile for berkeleydb-solr
 Key: ATLAS-3939
 URL: https://issues.apache.org/jira/browse/ATLAS-3939
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Atlas supports a number of build profiles, like 
external-hbase-sol/embedded-hbase-solr/embedded-cassandra-solr/berkeley-elasticsearch,
 for various combinations of backend stores an index stores. This should be 
extended to support berkeley-solr as well; this profile can be useful for 
dev/testing of Atlas.



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


[jira] [Resolved] (ATLAS-3807) Release Atlas 2.1.0

2020-09-10 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-3807.
-
Fix Version/s: 2.1.0
   Resolution: Fixed

> Release Atlas 2.1.0
> ---
>
> Key: ATLAS-3807
> URL: https://issues.apache.org/jira/browse/ATLAS-3807
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 2.1.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 2.1.0
>
>
> parent task to capture release tasks for Apache Atlas 2.1.0



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


[jira] [Assigned] (ATLAS-3934) Dockerfile should build from local repository rather than pulling code from git

2020-08-31 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj reassigned ATLAS-3934:
---

Assignee: Madhan Neethiraj

> Dockerfile should build from local repository rather than pulling code from 
> git
> ---
>
> Key: ATLAS-3934
> URL: https://issues.apache.org/jira/browse/ATLAS-3934
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Syed Atif Akhtar
>Assignee: Madhan Neethiraj
>Priority: Trivial
>  Labels: atlas, build, development_environment, docker
>
> *Expected Behaviour:*
>  When a developer wants to test out their changes using the dockerfile in dev 
> support, they should be able to create the dockerfile with atlas built and 
> mount from a local directory with the changes they have done.
> *Current Behaviour:*
> The dockerfile currently defined in dev-support pulls the source code from 
> git instead of building the code that the user has defined
>  
> {code:java}
> RUN git clone https://github.com/apache/atlas.git -b master{code}
>  
> *Suggestion:*
>  Maintain separate dockerfiles for publishing an image of Atlas vs development



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


[jira] [Created] (ATLAS-3912) move classes to appropriate modules

2020-08-06 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3912:
---

 Summary: move classes to appropriate modules
 Key: ATLAS-3912
 URL: https://issues.apache.org/jira/browse/ATLAS-3912
 Project: Atlas
  Issue Type: Improvement
  Components: atlas-intg
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Classes that are unrelated to integration of Atlas clients should be moved out 
of intg module, for example:
 - org.apache.atlas.entitytransform
 - org.apache.atlas.pc
 - org.apache.atlas.listener
 - org.apache.atlas.store

Classes in these packages should be move to modules like repository or common.



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


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

2020-07-20 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-3875.
-
Fix Version/s: 2.2.0
   3.0.0
   Resolution: Fixed

> 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
> Fix For: 3.0.0, 2.2.0
>
> 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-3359) Relationships : Unique attribute in a relationship is not honored

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3359:

Fix Version/s: (was: 2.1.0)
   2.2.0

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



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


[jira] [Updated] (ATLAS-3839) import-hive.sh build target directory error

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3839:

Fix Version/s: (was: 2.1.0)
   2.2.0

> import-hive.sh build target directory error
> ---
>
> Key: ATLAS-3839
> URL: https://issues.apache.org/jira/browse/ATLAS-3839
> Project: Atlas
>  Issue Type: Bug
>  Components: hive-integration
>Affects Versions: 1.1.0, 2.0.0
>Reporter: limbo
>Priority: Minor
>  Labels: patch-available
> Fix For: 2.2.0
>
> Attachments: ATLAS-3839.patch
>
>
> import-hive.sh build to bin directory rather than in hook-bin



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


[jira] [Updated] (ATLAS-3468) Exclude JTS topology suite library from being packaged

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3468:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Exclude JTS topology suite library from being packaged
> --
>
> Key: ATLAS-3468
> URL: https://issues.apache.org/jira/browse/ATLAS-3468
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.2.0
>
> Attachments: ATLAS-3468.002.patch
>
>
> Exclude JTS topology suite library from being packaged



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


[jira] [Updated] (ATLAS-3646) Create new 'spark_ml_model_dataset' and 'spark_ml_pipeline_dataset' relationship definitions

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3646:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Create new 'spark_ml_model_dataset' and 'spark_ml_pipeline_dataset' 
> relationship definitions
> 
>
> Key: ATLAS-3646
> URL: https://issues.apache.org/jira/browse/ATLAS-3646
> Project: Atlas
>  Issue Type: Task
>Reporter: Vladislav Glinskiy
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Create new 'spark_ml_model_dataset' and 'spark_ml_pipeline_dataset' 
> relationship definitions. This is required in order to integrate Spark Atlas 
> Connector's ML event processor.
> Previously, Spark Atlas Connector used the 'spark_ml_directory' model for the 
> ML model directory and 'spark_ml_model_ml_directory', 
> 'spark_ml_pipeline_ml_directory' relationship definitions. Usage of the 
> 'spark_ml_directory'  was reverted in the scope of 
> [https://github.com/hortonworks-spark/spark-atlas-connector/issues/61], 
> [https://github.com/hortonworks-spark/spark-atlas-connector/pull/62] so ML 
> model directory is 'DataSet' entity(i.e. 'hdfs_path', 'fs_path').
> Thus, new relationship definitions must be created, since there is no 
> straightforward way to update existing ones to use 'DataSet' type instead of 
> it's child type 'spark_ml_directory'.
> See:
>  * ATLAS-3640
>  * [https://github.com/apache/atlas/pull/88#issuecomment-592699723]



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


[jira] [Updated] (ATLAS-3665) Add 'queryText' attribute to the 'spark_process' type

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3665:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Add 'queryText' attribute to the 'spark_process' type
> -
>
> Key: ATLAS-3665
> URL: https://issues.apache.org/jira/browse/ATLAS-3665
> Project: Atlas
>  Issue Type: Task
>Reporter: Vladislav Glinskiy
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Add 'queryText' attribute to the 'spark_process' type in order to make 
> `spark_process` more readable by the user. The `queryText` attribute stores 
> exact SQL query that are executed within the Spark session as a Spark process.



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


[jira] [Updated] (ATLAS-3353) HMS Hook does not capture the deleted column with alter table replace columns command.

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3353:

Fix Version/s: (was: 2.1.0)
   2.2.0

> HMS Hook does not capture the deleted column with alter table replace columns 
> command.
> --
>
> Key: ATLAS-3353
> URL: https://issues.apache.org/jira/browse/ATLAS-3353
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.2.0
>
>
> For the below commands, HMS Hook does not capture the replaced column as 
> deleted entity.
> {noformat}
> create table table_with_dropped_cols_1 (id int,name string,dob date)
> alter table table_with_dropped_cols_1 replace columns (id int,name 
> string,address string)
> {noformat}



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


[jira] [Updated] (ATLAS-3501) Update guava version to 28.0-jre

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3501:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Update guava version to 28.0-jre
> 
>
> Key: ATLAS-3501
> URL: https://issues.apache.org/jira/browse/ATLAS-3501
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Aadarsh Jajodia
>Assignee: Aadarsh Jajodia
>Priority: Major
> Fix For: 2.2.0
>
> Attachments: 0001-ATLAS-3501-Update-guava-version-to-28.0-jre.patch
>
>




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


[jira] [Updated] (ATLAS-3724) Qualified name pattern for Column cause ambiguity in Quickstart data.

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3724:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Qualified name pattern for Column cause ambiguity in Quickstart data.
> -
>
> Key: ATLAS-3724
> URL: https://issues.apache.org/jira/browse/ATLAS-3724
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0, 2.1.0, 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.0.0, 2.2.0
>
> Attachments: ATLAS-3724.patch
>
>
> 1) Create Entity of type Column name = app_id, qualified name = app_id@cl1
> assign Table - logging_fact_monthly_mv
> 2) Again Create same entity with same qualified name
> assign different Table - log_fact_daily_mv
> 3) Check Column Relationship, Only one Table relationship is seen
> 4) Check Table (logging_fact_monthly_mv,log_fact_daily_mv) In Both 
> Relationship, Column app_id is seen



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


[jira] [Updated] (ATLAS-3341) Atlas knox SSO doesnt work when using external load balancer for Atlas UI.

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3341:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Atlas knox SSO doesnt work when using external load balancer for Atlas UI.
> --
>
> Key: ATLAS-3341
> URL: https://issues.apache.org/jira/browse/ATLAS-3341
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.1.0, 2.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> If Atlas ports are not open to access, so leveraging SSL offloading and using 
> External loabalancer enabled with SSL to access Atlas UI.
> However with the above setup Knox SSO redirection is not working as expected. 
> As the redirectUrl/Forwarded url created is not set for proper redirection.



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


[jira] [Updated] (ATLAS-3410) Term assigned to historical entity is not visible in Details page.

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3410:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Term assigned to historical entity is not visible in Details page.
> --
>
> Key: ATLAS-3410
> URL: https://issues.apache.org/jira/browse/ATLAS-3410
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: chaitali borole
>Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3410-Server.patch, ATLAS-3410-dashboardv3.patch, 
> ATLAS-3410.patch
>
>
> This issue is related to an earlier one (ATLAS-3403). When a entity with a 
> term associated to it is deleted, and if you navigate to the Details page for 
> that entity, the classification is displayed but not the term.



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


[jira] [Updated] (ATLAS-3837) execute import-hive.sh raise exception: Failed to load application properties

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3837:

Fix Version/s: (was: 2.1.0)
   2.2.0

> execute import-hive.sh raise exception: Failed to load application properties
> -
>
> Key: ATLAS-3837
> URL: https://issues.apache.org/jira/browse/ATLAS-3837
> Project: Atlas
>  Issue Type: Bug
>  Components: hive-integration
>Affects Versions: 1.2.0, 2.0.0
>Reporter: limbo
>Priority: Major
> Fix For: 2.2.0
>
> Attachments: ATLAS-3837.patch
>
>
> when run import-hive.sh, the script raise as follow:
> {code:java}
> 2020-06-11 10:49:01,177 INFO - [main:] ~ Looking for 
> atlas-application.properties in classpath (ApplicationProperties:97)
> 2020-06-11 10:49:01,181 INFO - [main:] ~ Looking for 
> /atlas-application.properties in classpath (ApplicationProperties:102)
> 2020-06-11 10:49:01,182 INFO - [main:] ~ Loading atlas-application.properties 
> from null (ApplicationProperties:110)
> 2020-06-11 10:49:01,199 ERROR - [main:] ~ Import failed 
> (HiveMetaStoreBridge:176)
> org.apache.atlas.AtlasException: Failed to load application properties
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:121)
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:73)
>  at 
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:120)
> Caused by: org.apache.commons.configuration.ConfigurationException: Cannot 
> locate configuration source null
>  at 
> org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:259)
>  at 
> org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:238)
>  at 
> org.apache.commons.configuration.AbstractFileConfiguration.(AbstractFileConfiguration.java:197)
>  at 
> org.apache.commons.configuration.PropertiesConfiguration.(PropertiesConfiguration.java:284)
>  at 
> org.apache.atlas.ApplicationProperties.(ApplicationProperties.java:56)
>  at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:112)
>  ... 2 more
> {code}
> the script can not find the config file of atlas-application.properties 



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


[jira] [Updated] (ATLAS-3498) Update basic-search to enable search using labels

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3498:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Update basic-search to enable search using labels
> -
>
> Key: ATLAS-3498
> URL: https://issues.apache.org/jira/browse/ATLAS-3498
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.2.0
>
>
> Update basic-search to enable search using labels



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


[jira] [Updated] (ATLAS-3255) UI: IE 10 - Page Limit button gets displaced after clicking it.

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3255:

Fix Version/s: (was: 2.1.0)
   2.2.0

> UI: IE 10 - Page Limit button gets displaced after clicking it.
> ---
>
> Key: ATLAS-3255
> URL: https://issues.apache.org/jira/browse/ATLAS-3255
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Rahul Kurup
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 3.0.0, 1.3.0, 2.2.0
>
>
> In IE 10, the Page Limit button position gets displaced and moves to the 
> middle of the search results page after clicking it.



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


[jira] [Updated] (ATLAS-3852) Entity Bulk Create with unique reference

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3852:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.2.0
>
> Attachments: ATLAS-3852.patch, BulkPostCreate.json
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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


[jira] [Updated] (ATLAS-3683) Entity details > Business Metadata, multi-valued attribute spacing issue

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3683:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Entity details > Business Metadata, multi-valued attribute spacing issue
> 
>
> Key: ATLAS-3683
> URL: https://issues.apache.org/jira/browse/ATLAS-3683
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Umesh Padashetty
>Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Screenshot 2020-03-25 at 1.14.15 AM.png
>
>
> While applying Business metadata attribute to an entity, once the 
> multi-valued attribute is applied, the multi values are displayed without any 
> spacing. This is a bit unreadable. It would be good if we can add a space 
> between comma-separated values.
> CC: [~kevalbhatt]



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


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

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3824:

Fix Version/s: (was: 2.1.0)
   2.2.0

> 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.2.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-3407) Regression, Impala and Spark Hook : Rename table doesn't rename existing table , but creates new table with updated name.

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3407:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Regression, Impala and Spark Hook : Rename table doesn't rename existing 
> table , but creates new table with updated name.
> -
>
> Key: ATLAS-3407
> URL: https://issues.apache.org/jira/browse/ATLAS-3407
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.2.0
>
>
> with hive hook , rename table works as expected.
> With spark and impala hook (hms hook), rename table creates new table with 
> updated name and doesn't update the existing table entity.



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


[jira] [Updated] (ATLAS-3610) Enable logging to multiple targets (logdir, stdout)

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3610:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Enable logging to multiple targets (logdir, stdout)
> ---
>
> Key: ATLAS-3610
> URL: https://issues.apache.org/jira/browse/ATLAS-3610
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: Mariusz Górski
>Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3610-1.patch, ATLAS-3610-2.patch, 
> ATLAS-3610-3.patch, ATLAS-3610.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> *Problem description*
> When starting Atlas, Python scripts are invoked to spawn all necessary 
> processes. This is achieved with the use of _subprocess.Popen()_ in 
> _runProcess()_ function of _atlas_config.py_ script. While doing that, stdout 
> is being redirected to log files, which (for java processes) can override 
> log4j configuration (if configured with stdout handler). This creates 
> situation when log4j configuration cannot be relied upon and prevents logging 
> to stdout.
> *Proposed solution*
>  * Add possibility to log to stdout by using multiple stdout/stderr handlers
>  * Adjust _runProcess()_ function from _atlas_config.py_ script (and all 
> functions relying on it) to provide _logconsole_ kwarg which will add 
> additional handler to Popen stdout/stderr redirection
>  * Add _ENABLE_LOGGING_TO_CONSOLE_ env variable (defaulting to _False_) for 
> backwards compatibility.
>  * Adjust _atlas_start.py_ script to make use of _ENABLE_LOGGING_TO_CONSOLE_  
> and provide it in functions invoking atlas/solr/elasticsearch/zookeeper
> *Predicted Benefits*
> This improvement would bring the benefit of enabling logging to stdout (which 
> is supressed for now even if configured in spawned components), which could 
> be very useful when running Atlas in docker container or in Kubernetes/OC, 
> where some logging scraping is present.



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


[jira] [Updated] (ATLAS-3890) Enhancement for all BulkAPIs.

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3890:

Fix Version/s: (was: 2.1.0)
   2.2.0

> Enhancement for all BulkAPIs.
> -
>
> Key: ATLAS-3890
> URL: https://issues.apache.org/jira/browse/ATLAS-3890
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>  Labels: api-change
> Fix For: 2.2.0
>
>
> According to below linked Atlas Jira two Bulk Apis are enhanced to return 
> authorised entities or modify them when some of then entity types are blocked 
> by policies in Ranger for access to user.Hence we are improving the other 
> bulk Apis too.
> Previously user only used to get 403 error if he tries to access or modify 
> entities which comprised of both authorised as well as unauthorised typenames.
> DELETE /bulk - EntityREST.deleteByGuids()
> GET /bulk/uniqueAttribute/type/\{typeName} - 
> EntityREST.getEntitiesByUniqueAttributes()



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


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

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3855:

Fix Version/s: (was: 2.1.0)
   2.2.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
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
>  Labels: api-change
> Fix For: 2.2.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-3809) Publish release artifacts

2020-07-15 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-3809.
-
Fix Version/s: 2.1.0
 Assignee: Madhan Neethiraj
   Resolution: Done

> Publish release artifacts
> -
>
> Key: ATLAS-3809
> URL: https://issues.apache.org/jira/browse/ATLAS-3809
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 2.1.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 2.1.0
>
>




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


[jira] [Resolved] (ATLAS-3879) Ozone: ozone_key entity is directly created under ozone_bucket

2020-07-07 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-3879.
-
Fix Version/s: 3.0.0
   2.1.0
   Resolution: Fixed

> Ozone: ozone_key entity is directly created under ozone_bucket
> --
>
> Key: ATLAS-3879
> URL: https://issues.apache.org/jira/browse/ATLAS-3879
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> The support for Apache Ozone was added in ATLAS-3836. Currently, ozone_key 
> entity is getting created under ozone_bucket, but there is no support to 
> create a hierarchy of parent ozone_key and child ozone_key.
>  
> e.g.
> {code:java}
> -> CREATE EXTERNAL TABLE sales (id int) row format delimited fields 
> terminated by ' ' stored as textfile location 
> 'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
> This query will create only 1 ozone_key directly under bucket "bucket1".
> Created entities :
>  * o3fs://volume1@cm (ozone_key)
>  * o3fs://volume1.bucket1@cm (ozone_bucket)
>  * o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
>  
> This Jira will improve implementation to support creating the hierarchy of 
> ozone_keys.
> With this, above query will result into following entites
>  * o3fs://volume1@cm (ozone_key)
>  * o3fs://volume1.bucket1@cm (ozone_bucket)
>  * o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
>  * o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
>  * o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of 
> ozone_key*
>  
> This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2 
> models.



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


[jira] [Resolved] (ATLAS-3850) Regression, Terms are not getting displayed

2020-06-23 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-3850.
-
Fix Version/s: 3.0.0
   2.1.0
   Resolution: Fixed

> Regression, Terms are not getting displayed
> ---
>
> Key: ATLAS-3850
> URL: https://issues.apache.org/jira/browse/ATLAS-3850
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> For the entity E1 , if term T1@G1 is associated,
> then while searching entity E1, Term is not displayed in the column of the 
> basic search panel
> "meanings":  in the response is empty



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


[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference

2020-06-23 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-3852:
-

[~vasanthkumar] - can you please add more details, with necessary data to 
reproduce the issue?

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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


[jira] [Commented] (ATLAS-3851) UI: Remove hourglass icon from in progress entity

2020-06-21 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-3851:
-

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

> UI: Remove hourglass icon from in progress entity
> -
>
> Key: ATLAS-3851
> URL: https://issues.apache.org/jira/browse/ATLAS-3851
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3851.patch
>
>




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


[jira] [Commented] (ATLAS-3828) UI: Change 'Status' from Classification System Attributes to EntityStatus

2020-06-11 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-3828:
-

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

> UI: Change 'Status' from Classification System Attributes to EntityStatus
> -
>
> Key: ATLAS-3828
> URL: https://issues.apache.org/jira/browse/ATLAS-3828
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3828.patch
>
>




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


[jira] [Created] (ATLAS-3825) import business metadata - incorrect attribute value assignement

2020-06-03 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3825:
---

 Summary: import business metadata - incorrect attribute value 
assignement
 Key: ATLAS-3825
 URL: https://issues.apache.org/jira/browse/ATLAS-3825
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.1.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Business metadata import to assign an attribute to multiple entities results in 
the last specified value to be applied to all entities, instead of values 
specified for individual entities. For example, setting business attributes on 
entities created by quick_start, with the following import contents, results in 
all entities to have test_businessMetadata.attr1=17 and 
test_businessMetadata.attr2=27.

 
{noformat}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
Table,customer_dim@cl1,test_businessMetadata.attr1,10
Table,customer_dim@cl1,test_businessMetadata.attr2,20
Table,log_fact_daily_mv@cl1,test_businessMetadata.attr1,11
Table,log_fact_daily_mv@cl1,test_businessMetadata.attr2,21
Table,logging_fact_monthly_mv@cl1,test_businessMetadata.attr1,12
Table,logging_fact_monthly_mv@cl1,test_businessMetadata.attr2,22
Table,product_dim@cl1,test_businessMetadata.attr1,13
Table,product_dim@cl1,test_businessMetadata.attr2,23
Table,sales_fact@cl1,test_businessMetadata.attr1,14
Table,sales_fact@cl1,test_businessMetadata.attr2,24
Table,sales_fact_daily_mv@cl1,test_businessMetadata.attr1,15
Table,sales_fact_daily_mv@cl1,test_businessMetadata.attr2,25
Table,sales_fact_monthly_mv@cl1,test_businessMetadata.attr1,16
Table,sales_fact_monthly_mv@cl1,test_businessMetadata.attr2,26
Table,time_dim@cl1,test_businessMetadata.attr1,17
Table,time_dim@cl1,test_businessMetadata.attr2,27
 {noformat}
 



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


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

2020-06-03 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3824:
---

 Summary: 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


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-3761) UI: Show progress bar for migration page

2020-06-03 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3761:

Fix Version/s: 2.1.0

> UI: Show progress bar for migration page
> 
>
> Key: ATLAS-3761
> URL: https://issues.apache.org/jira/browse/ATLAS-3761
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3761.patch
>
>




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


[jira] [Updated] (ATLAS-3775) Migration Import Display: Incorrect Status Display

2020-06-03 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3775:

Fix Version/s: (was: trunk)
   3.0.0
   2.1.0

> Migration Import Display: Incorrect Status Display
> --
>
> Key: ATLAS-3775
> URL: https://issues.apache.org/jira/browse/ATLAS-3775
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3775-Migration-Import-Status-display-fix.patch
>
>
> *Background*
> Zip file based migration introduced _DataMigrationStatusService_. This class 
> is responsible for displaying the status.
> *Steps to Duplicate*
> Pre-requisites:
>  * Keep the REST http:///api/atlas/admin output open in a browser 
> window.
>  * Keep zip-file based migration import in progress.
>  * Ensure that you see the current status. Once migration progress, refresh 
> the REST API output to display the status. The status should be accurate.
>  * Refresh the REST API output after 5 mins. This will expire the status 
> cache and make a request to _DataMigrationService_ for status.
> _Expected results_
>  * Status returned by API should reflect the status logged.
>  
> _Actual results_
>  * There is a mismatch in the status.
>  * Additional information: The status is never updated for that session.
> Root cause:
> - _DataMigrationService_ maintains cached status object for each requestor. 
> This is not refreshed from the database status.
>  



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


[jira] [Updated] (ATLAS-3705) UI : Remove notification section from Server Statistics: migration page

2020-06-03 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3705:

Fix Version/s: 2.1.0

> UI : Remove notification section from Server Statistics: migration page
> ---
>
> Key: ATLAS-3705
> URL: https://issues.apache.org/jira/browse/ATLAS-3705
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3705.patch
>
>




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


[jira] [Updated] (ATLAS-3604) Data Migration: Redirect root URI to migration status page

2020-06-03 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3604:

Fix Version/s: 2.1.0

> Data Migration: Redirect root URI to migration status page
> --
>
> Key: ATLAS-3604
> URL: https://issues.apache.org/jira/browse/ATLAS-3604
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: 
> ATLAS-3604-Data-Migration-Metrics-Page-Display-with-UI.patch
>
>
>  
> Data migration service added under [ATLAS-2461|http://example.com/] do not 
> provide UI to show migration status.
> This feature includes server side changes to allow a html page to be shown in 
> migration mode.
> In migration mode request to root URI will be redirected to 
> migration-status.html.
> This page will render the response from API "api/atlas/admin/metrics".
>  



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


[jira] [Updated] (ATLAS-3532) Test case failure in GremlinQueryComposerTest

2020-06-01 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3532:

Fix Version/s: 3.0.0
   2.1.0

> Test case failure in GremlinQueryComposerTest
> -
>
> Key: ATLAS-3532
> URL: https://issues.apache.org/jira/browse/ATLAS-3532
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: 
> ATLAS-3532-DSL-Composer-update-to-address-_-test-cas.patch, 
> ATLAS-3532-Test-case-failure-in-GremlinQueryComposer.patch
>
>
> {code:java}
> Tests run: 39, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.464 sec 
> <<< FAILURE! - in 
> org.apache.atlas.query.GremlinQueryComposerTestwhereClauseTextContains(org.apache.atlas.query.GremlinQueryComposerTest)
>   Time elapsed: 0.697 sec  <<< FAILURE!java.lang.AssertionError: Table where 
> owner like "Tab*" expected [g.V().has('__typeName', 
> 'Table').has('Table.owner', 
> org.janusgraph.core.attribute.Text.textContainsRegex("Tab.*")).dedup().limit(25).toList()]
>  but found [g.V().has('__typeName', 'Table').has('Table.owner', 
> org.janusgraph.core.attribute.Text.textRegex("Tab.*")).dedup().limit(25).toList()]
>  at org.testng.Assert.fail(Assert.java:94)
>  at org.testng.Assert.failNotEquals(Assert.java:496)
>  at org.testng.Assert.assertEquals(Assert.java:125)
>  at org.testng.Assert.assertEquals(Assert.java:178)
>  at 
> org.apache.atlas.query.GremlinQueryComposerTest.verify(GremlinQueryComposerTest.java:362)
>  at 
> org.apache.atlas.query.GremlinQueryComposerTest.verify(GremlinQueryComposerTest.java:371)
>  at 
> org.apache.atlas.query.GremlinQueryComposerTest.whereClauseTextContains(GremlinQueryComposerTest.java:170)
> {code}



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


[jira] [Updated] (ATLAS-3520) Regression: DSL query with "like" clause with "_" and "AND" returns unexpected entities.

2020-06-01 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3520:

Fix Version/s: 3.0.0
   2.1.0

> Regression: DSL query with "like" clause with "_" and "AND" returns 
> unexpected entities.
> 
>
> Key: ATLAS-3520
> URL: https://issues.apache.org/jira/browse/ATLAS-3520
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nikhil Bonte
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3520-DSL-Query-special-processing-for-_.patch
>
>
> *Problem*
> Dataset:
> Created a hive_table with name "sample_01" under hive_db having name as 
> "default".
> Query: 
> {code:java}
> hive_table db.name="default" and qualifiedName like "*sample_01*"
> {code}
> It is expected that above query should return 1 hive_table entity having 
> qualifiedName = default.sample_01@cluster, but it doesn't return any entity.
>   
> Other queries like following work and return expected results:
> {code:java}
> hive_table where db.name = "default" (only first part of query)
> hive_table qualifiedName like "*sample_01*"  (only second part of query)
> hive_table where db.name = "default" and name like "sample_01" (updating only 
> second part of query)
> hive_table db.name="default" and qualifiedName = "default.sample_01@cluster" 
> (using "=" instead of "like" with full qualifiedName)
> {code}
>  
> *Additional Information*
> For the type of queries mentioned above, 
> _org.janusgraph.core.attribute.Text.textContainsRegex_ is used to perform 
> comparison. This method within _JanusGraph_ is done in 2 steps:
>  * Tokenize the incoming stream.
>  * Perform regex match on the tokens from the step above.
> The tokenization routine aggregates by treating '_' as a delimiter. Thereby 
> failing to match a string containing '_'.
> *Solution*
> Within _GreamlinQueryComposer_, detect presence of '_' within the value and 
> resort to using _textRegex_ to match.
>  



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


[jira] [Updated] (ATLAS-3712) Add 'isAppendOnPartialUpdate' option in ML model to append updates

2020-06-01 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3712:

Fix Version/s: 3.0.0
   2.1.0

> Add 'isAppendOnPartialUpdate' option in ML model to append updates
> --
>
> Key: ATLAS-3712
> URL: https://issues.apache.org/jira/browse/ATLAS-3712
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: Na Li
>Assignee: Na Li
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> Atlas adds a new feature to allow client to append attributes during 
> partial-update operation in ATLAS-3700.
> We need to add 'isAppendOnPartialUpdate' option in ML model at 
> [https://github.com/apache/atlas/blob/master/addons/models/4000-MachineLearning/4010-ml_model.json]
>  to append updates using this new feature.
> Example:
> {code:java}
> {
> "name":"metadata",
> "typeName":"map",
> "isIndexable": false,
> "isOptional":  true,
> "isUnique":false,
> "options": {
>   "isAppendOnPartialUpdate": "true"
> }
>   } {code}
> The value specified for this attribute in partial-update API calls will be 
> appended to existing value - if present.
> Full-update API calls will overwrite the value of the attribute, as it does 
> currently; there is no change in full-update behavior.



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


[jira] [Updated] (ATLAS-3464) Define Entities stored in Atlas for ML Governance

2020-06-01 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3464:

Fix Version/s: 3.0.0
   2.1.0

> Define Entities stored in Atlas for ML Governance
> -
>
> Key: ATLAS-3464
> URL: https://issues.apache.org/jira/browse/ATLAS-3464
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: Na Li
>Assignee: Na Li
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> Need to define the entities to store ML governance metadata. 
> The definitions include:
> Entities and their relationship
> * Project create process
> * Project
> * Model training process
> * Model build
> * Model deployment process
> * Model deployment
> * User



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


[jira] [Commented] (ATLAS-3758) Support sort params for FreeTextSearchProcessor

2020-06-01 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-3758:
-

 [^ATLAS-3758-2-branch-2.0.patch]  has the fix for test failures in branch-2.0.

> Support sort params for FreeTextSearchProcessor
> ---
>
> Key: ATLAS-3758
> URL: https://issues.apache.org/jira/browse/ATLAS-3758
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: Damian Warszawski
>Priority: Minor
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3758-2-branch-2.0.patch, ATLAS-3758.patch
>
>
> *Problem description*
> No way to sort results by specified attribute while freetext search is 
> enabled.
> *Goals*
> As a team we are working to use Atlas as a metadata storage for 
> [https://github.com/lyft/amundsen]. It is required to sort results by any 
> particular attribute e.g. custom attribute which represents popularity score 
> to provide basic search relevancy for end users.
> *Proposed solution*
>  * add required parameters in the indexed query if specified



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


[jira] [Updated] (ATLAS-3758) Support sort params for FreeTextSearchProcessor

2020-06-01 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3758:

Attachment: ATLAS-3758-2-branch-2.0.patch

> Support sort params for FreeTextSearchProcessor
> ---
>
> Key: ATLAS-3758
> URL: https://issues.apache.org/jira/browse/ATLAS-3758
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: Damian Warszawski
>Priority: Minor
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3758-2-branch-2.0.patch, ATLAS-3758.patch
>
>
> *Problem description*
> No way to sort results by specified attribute while freetext search is 
> enabled.
> *Goals*
> As a team we are working to use Atlas as a metadata storage for 
> [https://github.com/lyft/amundsen]. It is required to sort results by any 
> particular attribute e.g. custom attribute which represents popularity score 
> to provide basic search relevancy for end users.
> *Proposed solution*
>  * add required parameters in the indexed query if specified



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


[jira] [Updated] (ATLAS-3779) Inmemory JAASConfig issue in Atlas

2020-05-30 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3779:

Fix Version/s: (was: trunk)
   2.1.0

> Inmemory JAASConfig issue in Atlas
> --
>
> Key: ATLAS-3779
> URL: https://issues.apache.org/jira/browse/ATLAS-3779
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mayank Jain
>Assignee: Mayank Jain
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> Spark uses Kafka as source and sink in secure cluster. The test creates a 
> JAAS file like this:
> {code:java}
> KafkaClient {
>   com.sun.security.auth.module.Krb5LoginModule required
>   debug=true
>   useKeyTab=true
>   storeKey=true
>   keyTab="/xxx/keytabs/systest.keytab"
>   useTicketCache=false
>   serviceName="kafka"
>   principal="syst...@gce.example.com";
> };
> {code}
> As one can see serviceName is set properly.
> Then the test pass the JAAS file to Spark's driver + executor as well:
> {code:java}
> "--conf 
> \"spark.driver.extraJavaOptions=-Djava.security.auth.login.config=./kafka_source_jaas.conf..."
> "--conf 
> \"spark.executor.extraJavaOptions=-Djava.security.auth.login.config=./kafka_source_jaas.conf..."
> {code}
> Later on SAC + atlas makes some magic in the background with the Jvm JAAS 
> configuration. As a result Spark is not able to create consumer for 
> processing data:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: No serviceName defined in 
> either JAAS or Kafka config
> {code}
> When I've turned off SAC then all the problem gone away.
> Atlas replaces the JVM global JAAS configuration with 
> InMemoryJAASConfiguration once Atlas configuration is initialized. 
> InMemoryJAASConfiguration has an old JAAS config as "parent" but Atlas config 
> takes precedence which is unexpected.
> We never want to let Atlas to overwrite existing JAAS configuration if 
> there's a conflict. (I believe most endpoints using Atlas client as a library 
> would agree with this.) This may be achieved via swapping precedence for 
> "parent" vs "Atlas config" in InMemoryJAASConfiguration, but I have no idea 
> the change would be safe to Atlas side. In any way, Atlas should at least 
> provide a config to let "parent" take precedence for the conflict.
>  



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


[jira] [Commented] (ATLAS-3812) Add schema for Apache Flink

2020-05-25 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-3812:
-

[~mbalassi] - thank you for the initiative on Apache Flink and Apache Atlas 
integration.Apache Atlas community uses [review 
board|https://reviews.apache.org/] extensively, please consider posting patches 
here.

- entity-type {{flink_application}} has attributes {{inputs}} and {{outputs}}, 
which override/hide the same named attributes in its super-type {{Process}}. I 
suggest to rename these attributes
- it is common to add typedef along with hook/bridge that populate Atlas with 
entity-instances. Do you plan to add hook/bridge implementation later?


> Add schema for Apache Flink
> ---
>
> Key: ATLAS-3812
> URL: https://issues.apache.org/jira/browse/ATLAS-3812
> Project: Atlas
>  Issue Type: New Feature
>  Components: atlas-intg
>Reporter: Márton Balassi
>Priority: Major
>
> Hi Apache Atlas team,
> I am an Apache Flink PMC member pursuing to add a Flink bridge to Atlas. As a 
> first step of this I would like to contribute the following schema, ideally 
> to the upcoming 2.1 release.
> {code}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [],
> "entityDefs": [
> {
> "name": "flink_application",
> "superTypes": [
> "Process"
> ],
> "serviceType": "flink",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "id",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": true
> },
> {
> "name": "startTime",
> "typeName": "date",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> },
> {
> "name": "endTime",
> "typeName": "date",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> },
> {
> "name": "conf",
> "typeName": "map",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> },
> {
> "name": "inputs",
> "typeName": "array",
> "cardinality": "LIST",
> "isIndexable": false,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "outputs",
> "typeName": "array",
> "cardinality": "LIST",
> "isIndexable": false,
> "isOptional": false,
> "isUnique": false
> }
> ]
> }
> ],
> "relationshipDefs": []
> }
> {code}
> Also please add an icon based on the white outline from the Flink material 
> page similarly to the existing Kafka icon.
> https://flink.apache.org/material.html



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


[jira] [Resolved] (ATLAS-3654) Support solr in standalone (http) mode

2020-05-25 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-3654.
-
Fix Version/s: 3.0.0
   2.1.0
   Resolution: Fixed

Thanks [~dwarszawski] for the patch!

> Support solr in standalone (http) mode
> --
>
> Key: ATLAS-3654
> URL: https://issues.apache.org/jira/browse/ATLAS-3654
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 3.0.0
>Reporter: Damian Warszawski
>Priority: Minor
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3654.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> *Problem description*
> Atlas does not support running Solr in standalone(http) mode.
> *Goals*
>  It is especially useful for testing purposes to make setup as simple as 
> possible without  Zookeeper. It also enables full integration with JanusGraph 
> as it support both mode of running Solr `cloud` and `http` 
> [https://docs.janusgraph.org/index-backend/solr/]. Additional benefit is to 
> decouple hbase and solr while running embedded mode so that solr can be run 
> in embbeded mode with external hbase.
> *Proposed solution*
>  * call solr V1 API  while creating/updating request handlers in standalone 
> solr
>  * update atlas start script to enable standalone embedded solr
>  



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


[jira] [Created] (ATLAS-3811) Update version in branch-2.0 to 2.2.0-SNAPSHOT

2020-05-24 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3811:
---

 Summary: Update version in branch-2.0 to 2.2.0-SNAPSHOT
 Key: ATLAS-3811
 URL: https://issues.apache.org/jira/browse/ATLAS-3811
 Project: Atlas
  Issue Type: Sub-task
Affects Versions: 2.1.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj






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


[jira] [Created] (ATLAS-3810) Update Atlas website for 2.1.0 release

2020-05-24 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3810:
---

 Summary: Update Atlas website for 2.1.0 release
 Key: ATLAS-3810
 URL: https://issues.apache.org/jira/browse/ATLAS-3810
 Project: Atlas
  Issue Type: Sub-task
Affects Versions: 2.1.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj






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


[jira] [Created] (ATLAS-3809) Publish release artifacts

2020-05-24 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3809:
---

 Summary: Publish release artifacts
 Key: ATLAS-3809
 URL: https://issues.apache.org/jira/browse/ATLAS-3809
 Project: Atlas
  Issue Type: Sub-task
Affects Versions: 2.1.0
Reporter: Madhan Neethiraj






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


[jira] [Updated] (ATLAS-3808) Change pom version from 2.1.0-SNAPSHOT to 2.1.0

2020-05-24 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated ATLAS-3808:

Affects Version/s: 2.1.0

> Change pom version from 2.1.0-SNAPSHOT to 2.1.0
> ---
>
> Key: ATLAS-3808
> URL: https://issues.apache.org/jira/browse/ATLAS-3808
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 2.1.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
>
> Update pom.xml files to replace version 2.0.0-SNAPSHOT to 2.0.0



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


[jira] [Created] (ATLAS-3808) Change pom version from 2.1.0-SNAPSHOT to 2.1.0

2020-05-24 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3808:
---

 Summary: Change pom version from 2.1.0-SNAPSHOT to 2.1.0
 Key: ATLAS-3808
 URL: https://issues.apache.org/jira/browse/ATLAS-3808
 Project: Atlas
  Issue Type: Sub-task
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Update pom.xml files to replace version 2.0.0-SNAPSHOT to 2.0.0



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


[jira] [Created] (ATLAS-3807) Release Atlas 2.1.0

2020-05-24 Thread Madhan Neethiraj (Jira)
Madhan Neethiraj created ATLAS-3807:
---

 Summary: Release Atlas 2.1.0
 Key: ATLAS-3807
 URL: https://issues.apache.org/jira/browse/ATLAS-3807
 Project: Atlas
  Issue Type: Task
Affects Versions: 2.1.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


parent task to capture release tasks for Apache Atlas 2.1.0



--
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 Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-3803:
-

+1 for the patch. Thanks [~sarath]!

> 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] [Commented] (ATLAS-3803) Update tag propagation to NONE between aws_s3_v2_container and aws_s3_v2_contained type

2020-05-20 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj commented on ATLAS-3803:
-

+1 for this update.

This update is inline with other relationships in existing models, like: 
hive_table_db, hive_table_columns, hbase_table_namespace, 
hbase_table_column_families, hbase_column_family_columns.

I suggest updating following relationship types as well: 
adls_gen2_account_containers, adls_gen2_parent_children.

> 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] [Resolved] (ATLAS-2618) Implement OMRSMetadataCollection for IGC

2020-05-18 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-2618.
-
Resolution: Abandoned

> Implement OMRSMetadataCollection for IGC
> 
>
> Key: ATLAS-2618
> URL: https://issues.apache.org/jira/browse/ATLAS-2618
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jerry He
>Priority: Major
>
> This is a metadata repository connector for IGC.



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


[jira] [Resolved] (ATLAS-2665) Add OMAG API and OMAS APIs in Atlas

2020-05-18 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-2665.
-
Resolution: Abandoned

> Add OMAG API and OMAS APIs in Atlas
> ---
>
> Key: ATLAS-2665
> URL: https://issues.apache.org/jira/browse/ATLAS-2665
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bogdan Sava
>Assignee: Bogdan Sava
>Priority: Major
> Attachments: 0001-ATLAS-2665-Add-OMAG-API-in-Atlas.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v3.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v4.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v5.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch
>
>
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> Change base URL for the API to "/open-metadata" 
>  
> Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
> resources annotated with.
> Spring mvc has contextConfigLocation init param pointing to 
> /WEB-INF/openMetadataContext.xml which scans the packages:
> {code:java}
> 
> {code}
>  The base URIs will be:
>  - for OMAS: /open-metadata/access-services/
>  - for OMAG: /open-metadata/admin/
>  The omag server spring boot application will have /open-metadata as context 
> path also
>  
> As result:
> /api/* paths will be handled bu jersey-servlet ( 
> com.sun.jersey.spi.spring.container.servlet.SpringServlet )
> /openmetadata/* will be handled by openmetadata-servlet ( 
> org.springframework.web.servlet.DispatcherServlet )
>  
> {code:java}
> 
>  jersey-servlet
>  
>  com.sun.jersey.spi.spring.container.servlet.SpringServlet
>  
>  
>  com.sun.jersey.api.json.POJOMappingFeature
>  true
>  
>  1
> 
> 
>  jersey-servlet
>  /api/atlas/*
> 
> 
>  open-metadata
>  
>  org.springframework.web.servlet.DispatcherServlet
>  
>  
>  contextConfigLocation
>  /WEB-INF/openMetadataContext.xml
>  
>  2
> 
> 
>  open-metadata
>  /open-metadata/*
> 
> {code}
>  
> The review board is: [https://reviews.apache.org/r/67083/]
>  



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


[jira] [Resolved] (ATLAS-2537) when running the omag server, by default it create files that interfere with a build

2020-05-18 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-2537.
-
Resolution: Abandoned

> when running the omag server, by default it create files that interfere with 
> a build 
> -
>
> Key: ATLAS-2537
> URL: https://issues.apache.org/jira/browse/ATLAS-2537
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
>
> when running the omagapplication in a development environment, by default a 
> config file is created in the root of the workspace. This file causes build 
> failures due to the licence checker and could also be inadvertently checked 
> into git.
> This Jira is raised to exclude this file in the license checker and to put it 
> into .gitignore.



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


[jira] [Resolved] (ATLAS-2601) OMAG server Swagger

2020-05-18 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-2601.
-
Resolution: Abandoned

> OMAG server Swagger 
> 
>
> Key: ATLAS-2601
> URL: https://issues.apache.org/jira/browse/ATLAS-2601
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Maryna Strelchuk
>Assignee: Maryna Strelchuk
>Priority: Major
> Attachments: 0001-Atlas-2601-OMAG-server-Swagger.patch
>
>
> This Jira addresses the addition of the Swagger for the OMAG server. 
> Currently Swagger was added as a dependency for
>  * omag-server
>  * omag-api
>  * omas-connectedasset



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


[jira] [Resolved] (ATLAS-2595) Improve version consistency in POMs (omas, omrs...)

2020-05-18 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-2595.
-
Resolution: Abandoned

> Improve version consistency in POMs (omas, omrs...)
> ---
>
> Key: ATLAS-2595
> URL: https://issues.apache.org/jira/browse/ATLAS-2595
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> In maven projects generally, the  or  
> tags can be used to provide some generic attributes for plugins, versions of 
> dependencies etc in a top level pom, and then child poms no longer need to 
> specify, unless they wish to override.
> Some components in atlas take a different approach, by setting an explicit 
> version in a property in the top level pom, and then using this variable in 
> the child pom.
> The current omrs, omas poms tend to explicitly refer to version, which can 
> lead to more inconsistency by mistake (they can override if essential for 
> function), so this Jira is being opened to consolidate



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


[jira] [Resolved] (ATLAS-2519) OMRS Kafka Topic Connector Consumer not being initialized

2020-05-18 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-2519.
-
Resolution: Abandoned

> OMRS Kafka Topic Connector Consumer not being initialized
> -
>
> Key: ATLAS-2519
> URL: https://issues.apache.org/jira/browse/ATLAS-2519
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Mark Ottesen
>Priority: Minor
>
> Adding two OMRS Repository Proxy Servers to a cohort using patch attached to 
> ATLAS-2122, the producer side of the KafkaOMRSTopicConnector is initalized 
> but not the consumer side. 



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


[jira] [Resolved] (ATLAS-2464) Information View OMAS Listener

2020-05-18 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-2464.
-
Resolution: Abandoned

> Information View OMAS Listener
> --
>
> Key: ATLAS-2464
> URL: https://issues.apache.org/jira/browse/ATLAS-2464
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Maryna Strelchuk
>Assignee: Ruxandra Rosu
>Priority: Major
> Attachments: 0001-IV-OMAS-initial-patch-08.05.patch, 
> ATLAS-2464_24_05.patch, initial_patch_iv.patch
>
>




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


[jira] [Resolved] (ATLAS-2518) Add Producer to OMRS Kafka Topic Connector

2020-05-18 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-2518.
-
Resolution: Abandoned

> Add Producer to OMRS Kafka Topic Connector
> --
>
> Key: ATLAS-2518
> URL: https://issues.apache.org/jira/browse/ATLAS-2518
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Reporter: Mark Ottesen
>Priority: Minor
>
> Need to implement the producer side of the OMRS Kafka Topic Connector 
> described in ATLAS-2465



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


[jira] [Resolved] (ATLAS-1580) Fix Catalog project to use GremlinExpressionFactory to avoid direct dependecy on titan0 and hard coded gremlin2.

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1580.
-
Resolution: Abandoned

Atlas does not use Titan any more.

> Fix Catalog project to use GremlinExpressionFactory to avoid direct dependecy 
> on titan0 and hard coded gremlin2.
> 
>
> Key: ATLAS-1580
> URL: https://issues.apache.org/jira/browse/ATLAS-1580
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Priority: Major
>
> Catalog project is hard-coded to generate Gremlin that is specific to Tinker 
> Pop 2.  It needs to be updated to use GremlinExpressionFactory to generate 
> Gremlin that is appropriate for the version of Titan being used.  In 
> addition, it has direct dependencies on titan 0 / Tinker Pop 2 classes.



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


[jira] [Resolved] (ATLAS-1581) Fix Atlas start up with titan1 as backend.

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1581.
-
Resolution: Abandoned

Atlas does not use Titan any more.

> Fix Atlas start up with titan1 as backend.
> --
>
> Key: ATLAS-1581
> URL: https://issues.apache.org/jira/browse/ATLAS-1581
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Priority: Major
>
> The Atlas war file startup is currently failing when Titan1 is being used.  
> Due to the titan 0 dependencies in catalog, the catalog jar is currently 
> being excluded from webapp when titan1 is being used.  However, Atlas appears 
> to have runtime dependencies on the stuff in Catalog.  The war startup 
> currently fails with the following exception:
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.atlas.catalog.exception.CatalogException
> at 
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at 
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)



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


[jira] [Resolved] (ATLAS-1582) Fix Webapp test failures with titan1 as graph backend

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1582.
-
Resolution: Abandoned

Atlas does not use Titan any more.

> Fix Webapp test failures with titan1 as graph backend
> -
>
> Key: ATLAS-1582
> URL: https://issues.apache.org/jira/browse/ATLAS-1582
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Priority: Major
>
> Some of the webapp tests fail because of dependency on catalog project. It is 
> unable to start the jetty server, as it can't find the Catalog classes. 
> Catalog project is hard-coded to generate Gremlin that is specific to Tinker 
> Pop 2.  It needs to be updated to use GremlinExpressionFactory to generate 
> Gremlin that is appropriate for the version of Titan being used.  In 
> addition, it has direct dependencies on titan 0 / Tinker Pop 2 classes. 
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.atlas.catalog.exception.CatalogRuntimeException
> at 
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at 
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at 
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at 
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> at 
> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)
> at 
> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)



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


[jira] [Resolved] (ATLAS-1591) Repository test failures with Titan1 profile

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1591.
-
Resolution: Abandoned

Atlas does not use Titan any more.

> Repository test failures with Titan1 profile
> 
>
> Key: ATLAS-1591
> URL: https://issues.apache.org/jira/browse/ATLAS-1591
> Project: Atlas
>  Issue Type: Bug
>Reporter: Neeru Gupta
>Priority: Major
>
> HBaseAuditrepostiryTests are failing with titan1 profile. It is unable to 
> instantiate the hbase. It looks like current version of hbase/hadoop is not 
> compatible with JDK8. 
> Tests run: 6, Failures: 4, Errors: 0, Skipped: 2, Time elapsed: 4.06 sec <<< 
> FAILURE! - in org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
> setup(org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest)  Time 
> elapsed: 3.313 sec  <<< FAILURE!
> java.lang.RuntimeException: Failed construction of Master: class 
> org.apache.hadoop.hbase.master.HMaster
> at 
> org.apache.hadoop.hbase.master.MasterRpcServices.getServices(MasterRpcServices.java:262)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.(RSRpcServices.java:863)
> at 
> org.apache.hadoop.hbase.master.MasterRpcServices.(MasterRpcServices.java:210)
> at 
> org.apache.hadoop.hbase.master.HMaster.createRpcServices(HMaster.java:532)
> at 
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:532)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:364)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)



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


[jira] [Resolved] (ATLAS-1695) Governance Definitions and Rules Management UI

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1695.
-
Resolution: Abandoned

> Governance Definitions and Rules Management UI
> --
>
> Key: ATLAS-1695
> URL: https://issues.apache.org/jira/browse/ATLAS-1695
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Christopher Flora
>Priority: Major
>  Labels: BusinessUserUI, OpenMetadata
>
> This Jira covers the business user interface for the governance team to 
> define the governance program.



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


[jira] [Resolved] (ATLAS-1703) amend Atlas simple security to add glossary

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1703.
-
Fix Version/s: 1.1.0
   2.0.0
   Resolution: Implemented

> amend Atlas simple security to add glossary  
> -
>
> Key: ATLAS-1703
> URL: https://issues.apache.org/jira/browse/ATLAS-1703
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>Priority: Major
> Fix For: 2.0.0, 1.1.0
>
>




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


[jira] [Resolved] (ATLAS-1706) Investigate HATEOAS for Atlas

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1706.
-
Resolution: Abandoned

> Investigate HATEOAS for Atlas
> -
>
> Key: ATLAS-1706
> URL: https://issues.apache.org/jira/browse/ATLAS-1706
> Project: Atlas
>  Issue Type: Wish
>Reporter: Apoorv Naik
>Priority: Major
>
> Currently the evolution of server is restricted because of the client side 
> library's tight coupling.
> HATEOAS allows independent evolution of the server side APIs and client can 
> dynamically maintain pace with the server side changes
> https://en.wikipedia.org/wiki/HATEOAS
> https://spring.io/understanding/HATEOAS



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


[jira] [Resolved] (ATLAS-1705) Update Atlas UI to use V2 Glossary

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1705.
-
Resolution: Done

> Update Atlas UI to use V2 Glossary 
> ---
>
> Key: ATLAS-1705
> URL: https://issues.apache.org/jira/browse/ATLAS-1705
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>Priority: Major
>




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


[jira] [Resolved] (ATLAS-1720) Add titan storage.lock.wait-time for Berkley DB to fix intermittent IT failures

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1720.
-
Resolution: Abandoned

Atlas doesn't use Titan any more.

> Add titan storage.lock.wait-time for Berkley DB to fix intermittent IT 
> failures 
> 
>
> Key: ATLAS-1720
> URL: https://issues.apache.org/jira/browse/ATLAS-1720
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, trunk
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>
> Some of the ITs in Atlas fail intermittently with exception - "Could not 
> execute operation due to backend exception"
> Upon investigation it's found this is due to Berkley LockTimeoutException 
> (https://github.com/thinkaurelius/titan/issues/1113)
> The default LockTimeout for berkley db is 500 ms and if a thread (some IT) is 
> waiting on titan storage resource which is locked by another thread and it 
> doesn't releases the lock within 500ms - fails with above exception. (see 
> error log below)
> The fix for this is to increase the storage.lock.wait-time for berkley dbor 
> increase the lock retry property - atlas.graph.storage.lock.retries=10.
> {code}
> Caused by: com.sleepycat.je.LockTimeoutException: (JE 5.0.73) Lock expired. 
> Locker 1516581475 7535_NotificationHookConsumer thread-0_Txn: waited for lock 
> on database=edgestore LockAddr:284896285 LSN=0x0/0x21d55f type=WRITE 
> grant=WAIT_PROMOTION timeoutMillis=500 startTime=1491261268442 
> endTime=1491261268942
> Owners: [,  locker="1516581475 7535_NotificationHookConsumer thread-0_Txn" type="READ"/>]
> Waiters: []
> Transaction 1445928922 7537_qtp184901207-1038 - 
> e015a355-d6c5-4424-b7a7-833a289aea9d_Txn waits for  LockAddr:471572402 
> Owners: Waiters:[ type="READ"/>]
> Transaction 1516581475 7535_NotificationHookConsumer thread-0_Txn owns 
> LockAddr:471572402 
> Transaction 1516581475 7535_NotificationHookConsumer thread-0_Txn waits for 
> LockAddr:284896285
> {code}



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


[jira] [Resolved] (ATLAS-1773) Create the OMRS Connector for Atlas

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1773.
-
Resolution: Abandoned

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-2018-12-21.patch, 
> ATLAS-2810-2019-01-10.patch, ATLAS-2939-2018-12-21.patch, 
> ATLAS-2985-2019-01-10.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



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


[jira] [Resolved] (ATLAS-1365) Use proper Contructors for Hive Entity objects in HiveHook

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1365.
-
Resolution: Abandoned

> Use proper Contructors for Hive Entity objects in HiveHook
> --
>
> Key: ATLAS-1365
> URL: https://issues.apache.org/jira/browse/ATLAS-1365
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
>Priority: Major
>
> Currently, default constructor for Entity is used and attributes like 
> Table/Path/Database and EntityType are set through explicit calls to setter 
> methods. This should be modified to use appropriate constructor for the data 
> type.



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


[jira] [Resolved] (ATLAS-1494) Data models of types inheriting Process have Inputs,Outputs which are of very generic type.

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1494.
-
Resolution: Abandoned

> Data models of types inheriting Process have Inputs,Outputs which are of very 
> generic type. 
> 
>
> Key: ATLAS-1494
> URL: https://issues.apache.org/jira/browse/ATLAS-1494
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Sharmadha S
>Priority: Major
> Fix For: trunk
>
>
> Types which are inheriting from Process have Inputs,Outputs as attributes of 
> datatype array which is very generic. For example, falcon_process' 
> input and output should be falcon_feed. In case of generic DataSet , input 
> and output can be any DataSet like hive_table, hbase_column_family , 
> jms_topic etc., which is faulty when associated to the falcon_process. 



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


[jira] [Resolved] (ATLAS-1438) Unable to generate the bridge model json

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1438.
-
Resolution: Information Provided

Sqoop model is available at 
{{addons/models/1000-Hadoop/1040-sqoop_model.json}}. Reference class 
{{SqoopDataModelGenerator}} doesn't exist anymore in Atlas. Documentation was 
fixed in ATLAS-2428.

> Unable to generate the bridge model json
> 
>
> Key: ATLAS-1438
> URL: https://issues.apache.org/jira/browse/ATLAS-1438
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>Priority: Major
>
> The documentation for the Squoop bridge says :
> "The default Sqoop modelling is available in 
> org.apache.atlas.sqoop.model.SqoopDataModelGenerator"
> This file does not exist in the source tree. The generators are mentioned in 
> the docs but are not there for Hive or Falcon. 
> I notice that the json model files are generated files. The docs implies that 
> SqoopDataModelGenerator and the like should be used to generate these json 
> model files. Unless I am missing something - it appears that either the docs 
> are incorrect or the source files are missing.  



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


[jira] [Resolved] (ATLAS-1318) Atlas Type System does not have DELETE API

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1318.
-
Fix Version/s: 0.8.1
   1.0.0
   Resolution: Done

Ability to delete a typedef (like classification/trait) was implemented in 
ATLAS-1737.

> Atlas Type System does not have DELETE API
> --
>
> Key: ATLAS-1318
> URL: https://issues.apache.org/jira/browse/ATLAS-1318
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Zineng Yuan
>Priority: Major
> Fix For: 1.0.0, 0.8.1
>
>
> I am trying to extend Atlas Type System by adding custom data type. However, 
> when I found a type name was misspecified and needed to be recreated, I can't 
> find a Restful Delete API.
> Question is does Atlas expose a Delete API for custom data types/attributes? 
> Without this delete API, it's difficult to rely on Atlas as a meta store to 
> extend custom data.  
> Please do suggest how to recreate a data type in this case. Thank you! 
>  



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


[jira] [Resolved] (ATLAS-1294) Return Titan-id in Entity retrieval for faster gremlin queries

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1294.
-
Resolution: Abandoned

The referenced API was deprecated in ATLAS-2062, and removed in ATLAS-2229.


> Return Titan-id in Entity retrieval for faster gremlin queries
> --
>
> Key: ATLAS-1294
> URL: https://issues.apache.org/jira/browse/ATLAS-1294
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Christian R
>Priority: Major
>  Labels: gremlin, search
>
> When I do a discovery/search/gremlin?query I can either specify my starting 
> node with the titan id , query=g.v(id) or if I don't have it I can use 
> g.V.has('Referenceable.qualifiedName','id') The first takes about 200ms 
> and the second takes roughly two seconds (timed in chrome dev tools) . As 
> such, I would like to get the titan id when I fetch an entity so that later 
> queries takes a reasonable amount of time. 
> Alternatively, the search documentation must be updated with loop-query 
> examples so I can use the DSL instead. The technical user guide doesn't even 
> mention Gremlin, so I am not sure if it is supposed to be used or not. Since 
> the web has many good Gremlin tutorials and no Atlas DSL tutorials I would 
> prefer to use Gremlin. 
> As a use case, I have one time series entity that is updated daily with new 
> values from csv-files. The lineage shows n CSV files, n import_job entities 
> and one timeseries, and i would like to know which CSV-file is the source of 
> a range of my timeseries. 



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


[jira] [Resolved] (ATLAS-1264) can't disable authentication

2020-05-17 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj resolved ATLAS-1264.
-
Resolution: Not A Bug

> can't disable authentication
> 
>
> Key: ATLAS-1264
> URL: https://issues.apache.org/jira/browse/ATLAS-1264
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jonathan Halliday
>Priority: Major
>
> When running a default install, the atlas-application.properties file 
> contains:
> atlas.http.authentication.enabled=false
> but the server requires authentication:
> curl -v http://localhost:21000/api/atlas/admin/version
> *   Trying 127.0.0.1...
> * Connected to localhost (127.0.0.1) port 21000 (#0)
> ...
> < HTTP/1.1 401 Full authentication is required to access this resource



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


  1   2   3   4   5   6   7   8   9   10   >