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

2020-10-27 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-4009:
---
Description: 
* 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] Apache Atlas classification updater  SKIPPED
[INFO] Apache Atlas index repair tool . SKIPPED
[INFO] Apache Atlas Impala Hook API ... SKIPPED
[INFO] Apache Atlas Impala Bridge Shim  SKIPPED
[INFO] Apache Atlas Impala Bridge . SKIPPED
[INFO] Apache Atlas Distribution .. SKIPPED
[INFO] atlas-examples . SKIPPED
[INFO] sample-app 3.0.0-SNAPSHOT .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 08:52 min
[INFO] Finished at: 2020-10-27T13:27:10+05:30
[INFO] 
[ERROR] 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 for parameter 
exclusions: Cannot find 'exclusions' in class 
org.apache.maven.plugins.dependency.fromConfiguration.ArtifactItem -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: 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 

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

2020-10-27 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-4009:
---
Summary: Atlas Build with -Pdist,embedded-hbase-solr  option fails on 
master.   (was: Atlas Build with -Pdist,embedded-hbase-solr  options fail on 
master )

> 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
>Priority: Major
> Attachments: Screenshot from 2020-10-27 19-24-54.png
>
>
> Atlas Build with -Pdist,embedded-hbase-solr options fail 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] Apache Atlas classification updater  SKIPPED
> [INFO] Apache Atlas index repair tool . SKIPPED
> [INFO] Apache Atlas Impala Hook API ... SKIPPED
> [INFO] Apache Atlas Impala Bridge Shim  SKIPPED
> [INFO] Apache Atlas Impala Bridge . SKIPPED
> [INFO] Apache Atlas Distribution .. SKIPPED
> [INFO] atlas-examples . SKIPPED
> [INFO] sample-app 3.0.0-SNAPSHOT .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 

[jira] [Updated] (ATLAS-4009) Atlas Build with -Pdist,embedded-hbase-solr options fail on master

2020-10-27 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-4009:
---
Attachment: Screenshot from 2020-10-27 19-24-54.png

> Atlas Build with -Pdist,embedded-hbase-solr  options fail on master 
> 
>
> Key: ATLAS-4009
> URL: https://issues.apache.org/jira/browse/ATLAS-4009
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
> Attachments: Screenshot from 2020-10-27 19-24-54.png
>
>
> Atlas Build with -Pdist,embedded-hbase-solr options fail 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] Apache Atlas classification updater  SKIPPED
> [INFO] Apache Atlas index repair tool . SKIPPED
> [INFO] Apache Atlas Impala Hook API ... SKIPPED
> [INFO] Apache Atlas Impala Bridge Shim  SKIPPED
> [INFO] Apache Atlas Impala Bridge . SKIPPED
> [INFO] Apache Atlas Distribution .. SKIPPED
> [INFO] atlas-examples . SKIPPED
> [INFO] sample-app 3.0.0-SNAPSHOT .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 08:52 min
> [INFO] Finished at: 2020-10-27T13:27:10+05:30
> [INFO] 
> 

[jira] [Created] (ATLAS-4009) Atlas Build with -Pdist,embedded-hbase-solr options fail on master

2020-10-27 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-4009:
--

 Summary: Atlas Build with -Pdist,embedded-hbase-solr  options fail 
on master 
 Key: ATLAS-4009
 URL: https://issues.apache.org/jira/browse/ATLAS-4009
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues
 Attachments: Screenshot from 2020-10-27 19-24-54.png

Atlas Build with -Pdist,embedded-hbase-solr options fail 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] Apache Atlas classification updater  SKIPPED
[INFO] Apache Atlas index repair tool . SKIPPED
[INFO] Apache Atlas Impala Hook API ... SKIPPED
[INFO] Apache Atlas Impala Bridge Shim  SKIPPED
[INFO] Apache Atlas Impala Bridge . SKIPPED
[INFO] Apache Atlas Distribution .. SKIPPED
[INFO] atlas-examples . SKIPPED
[INFO] sample-app 3.0.0-SNAPSHOT .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 08:52 min
[INFO] Finished at: 2020-10-27T13:27:10+05:30
[INFO] 
[ERROR] 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 for parameter 
exclusions: Cannot find 'exclusions' in class 
org.apache.maven.plugins.dependency.fromConfiguration.ArtifactItem -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 

[jira] [Commented] (ATLAS-4006) Support for Business Metadata in Atlas Export API

2020-10-26 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-4006:


+1 for the patch. Thanks [~amestry]

> Support for Business Metadata in Atlas Export API
> -
>
> Key: ATLAS-4006
> URL: https://issues.apache.org/jira/browse/ATLAS-4006
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Umesh Padashetty
>Assignee: Ashutosh Mestry
>Priority: Critical
> Attachments: 
> ATLAS-4006-ATLAS-4007-Export-Import-Added-support-for-Business-.patch
>
>
> Business metadata definition and Entity's Business metadata details are not 
> exported currently via Atlas Export API, we need to build support for this.



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


[jira] [Resolved] (ATLAS-3995) Atlas should support additional keystore/truststores types besides JKS

2020-10-22 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues resolved ATLAS-3995.

Fix Version/s: 2.2.0
   3.0.0
   Resolution: Fixed

> Atlas should support additional keystore/truststores types besides JKS
> --
>
> Key: ATLAS-3995
> URL: https://issues.apache.org/jira/browse/ATLAS-3995
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Currently Atlas server (through Jetty) only supports JKS keystore/truststore 
> types. There are additional keystore/truststore types used for different 
> applications like for FIPS crypto algorithms.
> Atlas server should support the default keystore type specified for the JDK 
> and have option to configure other keystore/truststore  types.



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


[jira] [Commented] (ATLAS-3990) UI: When user clicks to view hive-table details, shown some wrong tabs

2020-10-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3990:


+1 for the patch. Thanks [~kevalbhatt]

> UI: When user clicks to view hive-table details, shown some wrong tabs
> --
>
> Key: ATLAS-3990
> URL: https://issues.apache.org/jira/browse/ATLAS-3990
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3990.patch, wrong_tabs_showing_on_clicks.mkv
>
>
> Steps to reproduce::
>  # Have a hive_db with at least one table
>  # Click on 'Tables' tab
>  # Click on one of the tables listed in the tab
>  # The page renders the table details, including addition of 'Schema' tab
>  # However, 'Tables' tab is still visible; this tab needs to be hidden
>  # Also, on clicking the db link in Properties page of hive_table, 'Schema' 
> tab is still visible. This should be hidden
> PFA evidence file attached - wrong_tabs_showing_on_clicks.mkv



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


[jira] [Assigned] (ATLAS-3995) Atlas should support additional keystore/truststores types besides JKS

2020-10-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues reassigned ATLAS-3995:
--

Assignee: Nixon Rodrigues

> Atlas should support additional keystore/truststores types besides JKS
> --
>
> Key: ATLAS-3995
> URL: https://issues.apache.org/jira/browse/ATLAS-3995
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Currently Atlas server (through Jetty) only supports JKS keystore/truststore 
> types. There are additional keystore/truststore types used for different 
> applications like for FIPS crypto algorithms.
> Atlas server should support the default keystore type specified for the JDK 
> and have option to configure other keystore/truststore  types.



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


[jira] [Created] (ATLAS-3995) Atlas should support additional keystore/truststores types besides JKS

2020-10-14 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3995:
--

 Summary: Atlas should support additional keystore/truststores 
types besides JKS
 Key: ATLAS-3995
 URL: https://issues.apache.org/jira/browse/ATLAS-3995
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


Currently Atlas server (through Jetty) only supports JKS keystore/truststore 
types. There are additional keystore/truststore types used for different 
applications like for FIPS crypto algorithms.

Atlas server should support the default keystore type specified for the JDK and 
have option to configure other keystore/truststore  types.



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


[jira] [Resolved] (ATLAS-3971) Move authorization check for Business Metadata before type exist check

2020-10-08 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues resolved ATLAS-3971.

Fix Version/s: 2.2.0
   3.0.0
   Resolution: Fixed

> Move authorization check for Business Metadata before type exist check
> --
>
> Key: ATLAS-3971
> URL: https://issues.apache.org/jira/browse/ATLAS-3971
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3971.patch
>
>
> Refactor authorization check for Business Metadata before type exist check, 
> so that enduser is aware that a duplicate type creation is being attempted 
> which exist he is authorized to.



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


[jira] [Commented] (ATLAS-3977) Migration Script: Deleted entities in Atlas1.0 miss few attributes after migrated to Atlas2.0

2020-10-07 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3977:


+1 for the patch, thanks [~amestry] for the patch

> Migration Script: Deleted entities in Atlas1.0 miss few attributes after 
> migrated to Atlas2.0
> -
>
> Key: ATLAS-3977
> URL: https://issues.apache.org/jira/browse/ATLAS-3977
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha S
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3977-Addressed-patch-processing-for.patch, 
> am2cm_deleted_active_entity.png
>
>
> table6 is DELETED in Atlas1.0 and it is migrated to Atals2.0
> Attributes like name , db , owner are missing in DELETED entities whereas 
> they are populated correctly in ACTIVE entities.
> Attaching the screenshot.



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


[jira] [Updated] (ATLAS-3971) Move authorization check for Business Metadata before type exist check

2020-10-05 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3971:
---
Attachment: ATLAS-3971.patch

> Move authorization check for Business Metadata before type exist check
> --
>
> Key: ATLAS-3971
> URL: https://issues.apache.org/jira/browse/ATLAS-3971
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3971.patch
>
>
> Refactor authorization check for Business Metadata before type exist check, 
> so that enduser is aware that a duplicate type creation is being attempted 
> which exist he is authorized to.



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


[jira] [Updated] (ATLAS-3971) Move authorization check for Business Metadata before type exist check

2020-10-05 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3971:
---
Summary: Move authorization check for Business Metadata before type exist 
check  (was: Refactor authorization check for Business Metadata before type 
exist check)

> Move authorization check for Business Metadata before type exist check
> --
>
> Key: ATLAS-3971
> URL: https://issues.apache.org/jira/browse/ATLAS-3971
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Refactor authorization check for Business Metadata before type exist check, 
> so that enduser is aware that a duplicate type creation is being attempted 
> which exist he is authorized to.



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


[jira] [Created] (ATLAS-3971) Refactor authorization check for Business Metadata before type exist check

2020-10-05 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3971:
--

 Summary: Refactor authorization check for Business Metadata before 
type exist check
 Key: ATLAS-3971
 URL: https://issues.apache.org/jira/browse/ATLAS-3971
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


Refactor authorization check for Business Metadata before type exist check, so 
that enduser is aware that a duplicate type creation is being attempted which 
exist he is authorized to.



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


[jira] [Assigned] (ATLAS-3971) Refactor authorization check for Business Metadata before type exist check

2020-10-05 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues reassigned ATLAS-3971:
--

Assignee: Nixon Rodrigues

> Refactor authorization check for Business Metadata before type exist check
> --
>
> Key: ATLAS-3971
> URL: https://issues.apache.org/jira/browse/ATLAS-3971
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Refactor authorization check for Business Metadata before type exist check, 
> so that enduser is aware that a duplicate type creation is being attempted 
> which exist he is authorized to.



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


[jira] [Resolved] (ATLAS-3968) When un-authorised reader reads a type using the guid, the error message mentions about the type name instead of the guid

2020-10-05 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues resolved ATLAS-3968.

Fix Version/s: 2.2.0
   3.0.0
   Resolution: Fixed

> When un-authorised reader reads a type using the guid, the error message 
> mentions about the type name instead of the guid
> -
>
> Key: ATLAS-3968
> URL: https://issues.apache.org/jira/browse/ATLAS-3968
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> On firing a request for /api/atlas/v2/types/businessmetadatadef/guid/ 
> as an unauthorised user, the following error message is displayed
> {code:java}
> {
> u'errorCode': u'ATLAS-403-00-001',
> u'errorMessage': u'hrt_20 is not authorized to perform read type bm_123'
> }
> {code}
> Since we are firing the request using guid, it will be better to mention the 
> guid instead of the type name



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


[jira] [Assigned] (ATLAS-3968) When un-authorised reader reads a type using the guid, the error message mentions about the type name instead of the guid

2020-10-01 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues reassigned ATLAS-3968:
--

Assignee: Nixon Rodrigues

> When un-authorised reader reads a type using the guid, the error message 
> mentions about the type name instead of the guid
> -
>
> Key: ATLAS-3968
> URL: https://issues.apache.org/jira/browse/ATLAS-3968
> Project: Atlas
>  Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Nixon Rodrigues
>Priority: Major
>
> On firing a request for /api/atlas/v2/types/businessmetadatadef/guid/ 
> as an unauthorised user, the following error message is displayed
> {code:java}
> {
> u'errorCode': u'ATLAS-403-00-001',
> u'errorMessage': u'hrt_20 is not authorized to perform read type bm_123'
> }
> {code}
> Since we are firing the request using guid, it will be better to mention the 
> guid instead of the type name



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


[jira] [Assigned] (ATLAS-3952) Authorize Super And SubTypes and depend entityType for type-read access while creating Classificationdef

2020-09-29 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues reassigned ATLAS-3952:
--

Fix Version/s: 2.2.0
   3.0.0
 Assignee: Nixon Rodrigues
   Resolution: Fixed

> Authorize Super And SubTypes and depend entityType for type-read access while 
> creating Classificationdef
> 
>
> Key: ATLAS-3952
> URL: https://issues.apache.org/jira/browse/ATLAS-3952
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3952.patch
>
>
> User is able to create a type with a super type though he doesn't have read 
> permission on super type , subtype



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


[jira] [Resolved] (ATLAS-3963) Atlas api 'atlas/v2/types/typedefs/headers' does not give information about business metadata

2020-09-29 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues resolved ATLAS-3963.

Resolution: Duplicate

> Atlas api 'atlas/v2/types/typedefs/headers' does not give information about 
> business metadata
> -
>
> Key: ATLAS-3963
> URL: https://issues.apache.org/jira/browse/ATLAS-3963
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Nixon Rodrigues
>Priority: Major
>
> While trying to fetch headers of all types, data about business metadata is 
> not fetched via "*atlas/v2/types/typedefs/headers*"
> We could verify is there is business metadata in 
> "api/atlas/v2/types/typedefs?type=business_metadata" though
>  
> This holds true for 
> '[api/atlas/v2/types/typedefs/headers?type=business_metadata'|https://quasar-oczlgo-1.quasar-oczlgo.root.hwx.site:31443/api/atlas/v2/types/typedefs/headers?type=business_metadata%27]
>  as well
>  * [|https://jira.cloudera.com/secure/AddComment!default.jspa?id=917333]



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


[jira] [Resolved] (ATLAS-3962) Include business metadata def header in typdefs headers API

2020-09-29 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues resolved ATLAS-3962.

Fix Version/s: 2.2.0
   3.0.0
   Resolution: Fixed

> Include business metadata def header in typdefs headers API
> ---
>
> Key: ATLAS-3962
> URL: https://issues.apache.org/jira/browse/ATLAS-3962
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> While trying to fetch headers of all types, data about business metadata is 
> not fetched via "*atlas/v2/types/typedefs/headers*"
> We could verify is there is business metadata in 
> "api/atlas/v2/types/typedefs?type=business_metadata" though



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


[jira] [Created] (ATLAS-3962) Include business metadata def header in typdefs headers API

2020-09-28 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3962:
--

 Summary: Include business metadata def header in typdefs headers 
API
 Key: ATLAS-3962
 URL: https://issues.apache.org/jira/browse/ATLAS-3962
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues


While trying to fetch headers of all types, data about business metadata is not 
fetched via "*atlas/v2/types/typedefs/headers*"

We could verify is there is business metadata in 
"api/atlas/v2/types/typedefs?type=business_metadata" though



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


[jira] [Created] (ATLAS-3960) Testcase failing [testGetDefinition(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)]

2020-09-28 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3960:
--

 Summary: Testcase failing 
[testGetDefinition(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)] 
 Key: ATLAS-3960
 URL: https://issues.apache.org/jira/browse/ATLAS-3960
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.8.4
Reporter: Nixon Rodrigues


Testcase failing with mvn clean install

 
{noformat}
testGetDefinition(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  
Time elapsed: 0.004 sec  <<< FAILURE!
java.lang.AssertionError: Get byName should've succeeded
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:420)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:350)
at org.apache.atlas.AtlasBaseClient.callAPI(AtlasBaseClient.java:254)
at 
org.apache.atlas.AtlasClientV2.getTypeDefByName(AtlasClientV2.java:428)
at 
org.apache.atlas.AtlasClientV2.getClassificationDefByName(AtlasClientV2.java:159)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.verifyByNameAndGUID(TypedefsJerseyResourceIT.java:339)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testGetDefinition(TypedefsJerseyResourceIT.java:185)
{noformat}



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


[jira] [Commented] (ATLAS-3959) Upgrade Atlas to Spring Framework version 4.3.16.release

2020-09-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3959:


+1 for the patch, Thanks [~chaitali]

> Upgrade Atlas to Spring Framework version 4.3.16.release
> 
>
> Key: ATLAS-3959
> URL: https://issues.apache.org/jira/browse/ATLAS-3959
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8.1
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 0.8.1
>
> Attachments: ATLAS-3959.patch
>
>
> Existing Spring version 4.3.8.release is vulnerable to CVE-2018-1270



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


[jira] [Commented] (ATLAS-3958) When updating a type with non-existing super type as an un-authorized user gives in-correct message in response

2020-09-25 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3958:


ATLAS-3952 will be fix this issue which under review 
https://reviews.apache.org/r/72894/

> When updating a type with non-existing super type as an un-authorized user 
> gives in-correct message in response
> ---
>
> Key: ATLAS-3958
> URL: https://issues.apache.org/jira/browse/ATLAS-3958
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Minor
>
> When an unauthorised  user updates a type, by adding a non-existing 
> super-type, incorret error message is thrown
> *Repro steps:*
> Create a classification (as authorised user)
> Update the classification  as un-authorised user(*hrt_1*), by adding a 
> non-existing super type *qqq*
> *Observed error message:*
> {code}
> {
> "errorCode": "ATLAS-400-00-029",
> "errorMessage": "Given typename qqq was invalid"
> }
> {code}
> *Expected error message:*
> {code}
> {
> "errorCode": "ATLAS-403-00-001",
> "errorMessage": "hrt_1 is not authorized to perform update classification-def 
> child"
> }
> {code}



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


[jira] [Commented] (ATLAS-3955) Read Type Auth, UI : detailsPage doesn't load for user who has read permission for entity but no read auth for entity's type

2020-09-24 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3955:


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

> Read Type Auth, UI : detailsPage doesn't load for user who has read 
> permission for entity but no read auth for entity's type
> 
>
> Key: ATLAS-3955
> URL: https://issues.apache.org/jira/browse/ATLAS-3955
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3955.patch
>
>
> -
> Simple scenario
> -
> 1 . hive_table employee is created.
> 2. USER has permissions to read the employee table entity
> 3. USER doesn't have permissions to read type hive_table
> 4. USER logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists 
> the hive_table entity "employee"
> 5. Clicking on it, UI throws following error in Console tab and UI keeps 
> loading.
> {code:java}
> DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot 
> read property 'toJSON' of undefined
> at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1)
> at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
> at N.d.reset (backbone-min.js?bust=1600212682027:1)
> at Object. (backbone.paginator.min.js?bust=1600212682027:1)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1) {code}



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


[jira] [Updated] (ATLAS-3952) Authorize Super And SubTypes and depend entityType for type-read access while creating Classificationdef

2020-09-22 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3952:
---
Attachment: ATLAS-3952.patch

> Authorize Super And SubTypes and depend entityType for type-read access while 
> creating Classificationdef
> 
>
> Key: ATLAS-3952
> URL: https://issues.apache.org/jira/browse/ATLAS-3952
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3952.patch
>
>
> User is able to create a type with a super type though he doesn't have read 
> permission on super type , subtype



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


[jira] [Created] (ATLAS-3952) Authorize Super And SubTypes and depend entityType for type-read access while creating Classificationdef

2020-09-22 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3952:
--

 Summary: Authorize Super And SubTypes and depend entityType for 
type-read access while creating Classificationdef
 Key: ATLAS-3952
 URL: https://issues.apache.org/jira/browse/ATLAS-3952
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


User is able to create a type with a super type though he doesn't have read 
permission on super type , subtype



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


[jira] [Commented] (ATLAS-3911) UI: Type system management

2020-09-22 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3911:


+1 for the patch, [~kevalbhatt] thanks

> UI: Type system management
> --
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3911-1.patch, ATLAS-3911-2.patch, 
> ATLAS-3911.patch, Type_System_Tree.png, Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



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


[jira] [Updated] (ATLAS-3951) Authorize entity-type for type-read permission before creating entity of that type.

2020-09-21 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3951:
---
Attachment: ATLAS-3951.patch

> Authorize entity-type for type-read permission before creating entity of that 
> type.
> ---
>
> Key: ATLAS-3951
> URL: https://issues.apache.org/jira/browse/ATLAS-3951
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3951.patch
>
>
> User is able to create entities of type though he doesn't have read 
> permissions on the type



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


[jira] [Assigned] (ATLAS-3951) Authorize entity-type for type-read permission before creating entity of that type.

2020-09-21 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues reassigned ATLAS-3951:
--

Assignee: Nixon Rodrigues

> Authorize entity-type for type-read permission before creating entity of that 
> type.
> ---
>
> Key: ATLAS-3951
> URL: https://issues.apache.org/jira/browse/ATLAS-3951
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3951.patch
>
>
> User is able to create entities of type though he doesn't have read 
> permissions on the type



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


[jira] [Created] (ATLAS-3951) Authorize entity-type for type-read permission before creating entity of that type.

2020-09-21 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3951:
--

 Summary: Authorize entity-type for type-read permission before 
creating entity of that type.
 Key: ATLAS-3951
 URL: https://issues.apache.org/jira/browse/ATLAS-3951
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


User is able to create entities of type though he doesn't have read permissions 
on the type



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


[jira] [Updated] (ATLAS-3947) Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES types

2020-09-17 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3947:
---
Attachment: ATLAS-3947.patch

> Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES 
> types
> -
>
> Key: ATLAS-3947
> URL: https://issues.apache.org/jira/browse/ATLAS-3947
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3947.patch
>
>
> Skip authorization for read of _ALL_ENTITY_TYPES type of entity type  and 
> _ALL_CLASSIFICATION_TYPES type of classification type.
>  This are internally required by for system attributes search. 



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


[jira] [Created] (ATLAS-3947) Skip authorization for read _ALL_ENTITY_TYPES and _ALL_CLASSIFICATION_TYPES types

2020-09-17 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3947:
--

 Summary: Skip authorization for read _ALL_ENTITY_TYPES and 
_ALL_CLASSIFICATION_TYPES types
 Key: ATLAS-3947
 URL: https://issues.apache.org/jira/browse/ATLAS-3947
 Project: Atlas
  Issue Type: Improvement
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues


Skip authorization for read of _ALL_ENTITY_TYPES type of entity type  and 
_ALL_CLASSIFICATION_TYPES type of classification type.
 This are internally required by for system attributes search. 



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


[jira] [Created] (ATLAS-3946) Filter TypeDefs in Metrics API and show data accordingly

2020-09-17 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3946:
--

 Summary: Filter TypeDefs in Metrics API and show data accordingly
 Key: ATLAS-3946
 URL: https://issues.apache.org/jira/browse/ATLAS-3946
 Project: Atlas
  Issue Type: Improvement
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues


Filter TypeDefs in Metrics API and show data accordingly, currently data is 
shown for all types even if user do not have access to those types.



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


[jira] [Updated] (ATLAS-3942) Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef while delete-type

2020-09-15 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3942:
---
Affects Version/s: 2.2.0

> Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef 
> while delete-type
> ---
>
> Key: ATLAS-3942
> URL: https://issues.apache.org/jira/browse/ATLAS-3942
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3942.patch
>
>
> delete-type is triggering read-type authz access internally called by method 
> {{getByName}}.
> Considering refactoring {{AtlasTypeDefGraphStore}} code to remove authz check 
> reading typedef internally.



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


[jira] [Updated] (ATLAS-3942) Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef while delete-type

2020-09-15 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3942:
---
Attachment: ATLAS-3942.patch

> Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef 
> while delete-type
> ---
>
> Key: ATLAS-3942
> URL: https://issues.apache.org/jira/browse/ATLAS-3942
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3942.patch
>
>
> delete-type is triggering read-type authz access internally called by method 
> {{getByName}}.
> Considering refactoring {{AtlasTypeDefGraphStore}} code to remove authz check 
> reading typedef internally.



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


[jira] [Updated] (ATLAS-3942) Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef while delete-type

2020-09-15 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3942:
---
Summary: Refactoring AtlasTypeDefGraphStore code to remove authz check 
reading typedef while delete-type  (was: Refactoring AtlasTypeDefGraphStore 
code to remove authz check reading typedef)

> Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef 
> while delete-type
> ---
>
> Key: ATLAS-3942
> URL: https://issues.apache.org/jira/browse/ATLAS-3942
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> delete-type is triggering read-type authz access internally called by method 
> {{getByName}}.
> Considering refactoring {{AtlasTypeDefGraphStore}} code to remove authz check 
> reading typedef internally.



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


[jira] [Updated] (ATLAS-3942) Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef

2020-09-15 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3942:
---
Description: 
delete-type is triggering read-type authz access internally called by method 
{{getByName}}.
Considering refactoring {{AtlasTypeDefGraphStore}} code to remove authz check 
reading typedef internally.

  was:
delete-type is triggering read-type authz access internally calls getByName.
Considering refactoring AtlasTypeDefGraphStore code to remove authz check 
reading typedef internally.


> Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef
> -
>
> Key: ATLAS-3942
> URL: https://issues.apache.org/jira/browse/ATLAS-3942
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> delete-type is triggering read-type authz access internally called by method 
> {{getByName}}.
> Considering refactoring {{AtlasTypeDefGraphStore}} code to remove authz check 
> reading typedef internally.



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


[jira] [Created] (ATLAS-3942) Refactoring AtlasTypeDefGraphStore code to remove authz check reading typedef

2020-09-15 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3942:
--

 Summary: Refactoring AtlasTypeDefGraphStore code to remove authz 
check reading typedef
 Key: ATLAS-3942
 URL: https://issues.apache.org/jira/browse/ATLAS-3942
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues


delete-type is triggering read-type authz access internally calls getByName.
Considering refactoring AtlasTypeDefGraphStore code to remove authz check 
reading typedef internally.



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


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

2020-09-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3941:


+1 for the patch, Thanks [~amestry]

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



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


[jira] [Updated] (ATLAS-3940) Upgrade snakeyaml to a version without CVE-2017-18640

2020-09-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3940:
---
Issue Type: Bug  (was: Improvement)

> Upgrade snakeyaml to a version without CVE-2017-18640 
> --
>
> Key: ATLAS-3940
> URL: https://issues.apache.org/jira/browse/ATLAS-3940
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
>
> Maven package cassandra-all has transitive dependency on 
> org.yaml:snakeyaml:1.11 which has 
> CVE-2017-18640:https://nvd.nist.gov/vuln/detail/CVE-2017-18640



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


[jira] [Created] (ATLAS-3940) Upgrade snakeyaml to a version without CVE-2017-18640

2020-09-14 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3940:
--

 Summary: Upgrade snakeyaml to a version without CVE-2017-18640 
 Key: ATLAS-3940
 URL: https://issues.apache.org/jira/browse/ATLAS-3940
 Project: Atlas
  Issue Type: Improvement
Reporter: Nixon Rodrigues


Maven package cassandra-all has transitive dependency on 
org.yaml:snakeyaml:1.11 which has 
CVE-2017-18640:https://nvd.nist.gov/vuln/detail/CVE-2017-18640



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


[jira] [Commented] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-09-03 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3925:


+1 for ATLAS-3925-1.patch, thanks [~kevalbhatt]

> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3925-1.patch, ATLAS-3925.patch, 
> image-2020-08-25-12-53-09-294.png, image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



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


[jira] [Reopened] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-09-03 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues reopened ATLAS-3925:


> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3925-1.patch, ATLAS-3925.patch, 
> image-2020-08-25-12-53-09-294.png, image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



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


[jira] [Updated] (ATLAS-3932) Upgrade Spring security , libpam4j and jna lib version

2020-08-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3932:
---
Attachment: 0001-ATLAS-3932-Upgrade-jna-spring.security-and-libpam4j-.patch

> Upgrade Spring security , libpam4j and jna lib version
> --
>
> Key: ATLAS-3932
> URL: https://issues.apache.org/jira/browse/ATLAS-3932
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-3932-Upgrade-jna-spring.security-and-libpam4j-.patch
>
>
> Upgrade jna lib version from 4.1.0 to 5.2.0
> Upgrade libpam4j lib version from 1.8 to 1.11
> and Upgrade Spring security  version from 4.2.16.RELEASE to  4.2.17.RELEASE



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


[jira] [Updated] (ATLAS-3932) Upgrade Spring security , libpam4j and jna lib version

2020-08-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3932:
---
Description: 
Upgrade jna lib version from 4.1.0 to 5.2.0
Upgrade libpam4j lib version from 1.8 to 1.11
and Upgrade Spring security  version from 4.2.16.RELEASE to  4.2.17.RELEASE

  was:
Upgrade jna lib version from 4.1.0 to 5.2.0
and Upgrade Spring security  version to  4.2.17.RELEASE


> Upgrade Spring security , libpam4j and jna lib version
> --
>
> Key: ATLAS-3932
> URL: https://issues.apache.org/jira/browse/ATLAS-3932
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-3932-Upgrade-jna-spring.security-and-libpam4j-.patch
>
>
> Upgrade jna lib version from 4.1.0 to 5.2.0
> Upgrade libpam4j lib version from 1.8 to 1.11
> and Upgrade Spring security  version from 4.2.16.RELEASE to  4.2.17.RELEASE



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


[jira] [Updated] (ATLAS-3932) Upgrade Spring security , libpam4j and jna lib version

2020-08-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3932:
---
Summary: Upgrade Spring security , libpam4j and jna lib version  (was: 
Upgrade Spring security and jna lib version)

> Upgrade Spring security , libpam4j and jna lib version
> --
>
> Key: ATLAS-3932
> URL: https://issues.apache.org/jira/browse/ATLAS-3932
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Upgrade jna lib version from 4.1.0 to 5.2.0
> and Upgrade Spring security  version to  4.2.17.RELEASE



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


[jira] [Updated] (ATLAS-3932) Upgrade Spring security and jna lib version

2020-08-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3932:
---
Summary: Upgrade Spring security and jna lib version  (was: Upgrade jna lib 
version to 5.2.0)

> Upgrade Spring security and jna lib version
> ---
>
> Key: ATLAS-3932
> URL: https://issues.apache.org/jira/browse/ATLAS-3932
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Upgrade jna lib version from 4.1.0 to 5.2.0 for PAM authentication



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


[jira] [Updated] (ATLAS-3932) Upgrade Spring security and jna lib version

2020-08-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3932:
---
Description: 
Upgrade jna lib version from 4.1.0 to 5.2.0
and Upgrade Spring security  version to  4.2.17.RELEASE

  was:Upgrade jna lib version from 4.1.0 to 5.2.0 for PAM authentication


> Upgrade Spring security and jna lib version
> ---
>
> Key: ATLAS-3932
> URL: https://issues.apache.org/jira/browse/ATLAS-3932
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Upgrade jna lib version from 4.1.0 to 5.2.0
> and Upgrade Spring security  version to  4.2.17.RELEASE



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


[jira] [Created] (ATLAS-3932) Upgrade jna lib version to 5.2.0

2020-08-28 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3932:
--

 Summary: Upgrade jna lib version to 5.2.0
 Key: ATLAS-3932
 URL: https://issues.apache.org/jira/browse/ATLAS-3932
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 2.1.0
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: 3.0.0, 2.2.0


Upgrade jna lib version from 4.1.0 to 5.2.0 for PAM authentication



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


[jira] [Commented] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-08-26 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3925:


+1 for the patch , Thanks [~kevalbhatt]

> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3925.patch, image-2020-08-25-12-53-09-294.png, 
> image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



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


[jira] [Comment Edited] (ATLAS-3926) Atlas1.2 with Kerberos problem

2020-08-25 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues edited comment on ATLAS-3926 at 8/25/20, 1:31 PM:
--

For kerberos authentication properties with prefix 
"atlas.authentication.method.kerberos" are used for configuring the kerberos 
filter. I see them as some commented. please ensure following properties are 
set and kinit is done before running import-hive.sh

atlas.authentication.method.kerberos=true
atlas.authentication.method.kerberos.keytab=/keytab/atlas.keytab
atlas.authentication.method.kerberos.principal=atlas/_h...@example.com
atlas.authentication.method.kerberos.name.rules=
atlas.authentication.keytab=/keytab/atlas.keytab
atlas.authentication.principal=atlas/_h...@example.com




was (Author: nixonrodrigues):
For kerberos authentication properties with prefix 
"atlas.authentication.method.kerberos" are used for configuring the kerberos 
filter. I see them as some commented. please ensure following properties are 
set and kinit is done before running import-hive.sh

atlas.authentication.method.kerberos=true
atlas.authentication.method.kerberos.keytab=/keytab/atlas.keytab
atlas.authentication.method.kerberos.principal=atlas/_h...@example.com
atlas.authentication.method.kerberos.name.rules=
atlas.authentication.keytab=/keytab/atlas.keytab
atlas.authentication.principal=atlas/_h...@root.hwx.site



> Atlas1.2 with Kerberos problem
> --
>
> Key: ATLAS-3926
> URL: https://issues.apache.org/jira/browse/ATLAS-3926
> Project: Atlas
>  Issue Type: Bug
>  Components: falcon-integration, hive-integration
>Affects Versions: 1.2.0
>Reporter: yuyu
>Priority: Major
> Fix For: 1.2.0
>
> Attachments: image-2020-08-25-16-29-12-906.png, 
> image-2020-08-25-16-29-29-667.png, image-2020-08-25-16-30-34-221.png, 
> image-2020-08-25-16-31-23-439.png, image-2020-08-25-16-31-28-330.png, 
> image-2020-08-25-16-34-41-642.png, image-2020-08-25-16-35-09-836.png, 
> image-2020-08-25-16-38-45-645.png
>
>
> Hello, everyone. Recently, I encountered a problem with Kerberos when 
> deploying atlas.I tried to deploy atlas service on my CDH cluster with CDH 
> version 5.16 and Kerberos service deployed.My installation method is Atlas 
> 1.2 integrated CDH HBase and external 5.5.1 Solr
> When I start the atlas service, I can successfully access the atlas web page 
> through my computer:
> !image-2020-08-25-16-29-29-667.png!
> But when I tried to import hive metadata information, something went wrong,as 
> shown in the figure below:
> !image-2020-08-25-16-30-34-221.png!
> !image-2020-08-25-16-38-45-645.png!
> !image-2020-08-25-16-31-28-330.png!
> It seems to indicate that I don't have a valid Kerberos principal?
> Here is part of my atlas configuration file  atlas-application.properties:
> !image-2020-08-25-16-34-41-642.png!
> !image-2020-08-25-16-35-09-836.png!
> Can anyone tell me what the problem is,thanks.
>  



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


[jira] [Commented] (ATLAS-3926) Atlas1.2 with Kerberos problem

2020-08-25 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3926:


For kerberos authentication properties with prefix 
"atlas.authentication.method.kerberos" are used for configuring the kerberos 
filter. I see them as some commented. please ensure following properties are 
set and kinit is done before running import-hive.sh

atlas.authentication.method.kerberos=true
atlas.authentication.method.kerberos.keytab=/keytab/atlas.keytab
atlas.authentication.method.kerberos.principal=atlas/_h...@example.com
atlas.authentication.method.kerberos.name.rules=
atlas.authentication.keytab=/keytab/atlas.keytab
atlas.authentication.principal=atlas/_h...@root.hwx.site



> Atlas1.2 with Kerberos problem
> --
>
> Key: ATLAS-3926
> URL: https://issues.apache.org/jira/browse/ATLAS-3926
> Project: Atlas
>  Issue Type: Bug
>  Components: falcon-integration, hive-integration
>Affects Versions: 1.2.0
>Reporter: yuyu
>Priority: Major
> Fix For: 1.2.0
>
> Attachments: image-2020-08-25-16-29-12-906.png, 
> image-2020-08-25-16-29-29-667.png, image-2020-08-25-16-30-34-221.png, 
> image-2020-08-25-16-31-23-439.png, image-2020-08-25-16-31-28-330.png, 
> image-2020-08-25-16-34-41-642.png, image-2020-08-25-16-35-09-836.png, 
> image-2020-08-25-16-38-45-645.png
>
>
> Hello, everyone. Recently, I encountered a problem with Kerberos when 
> deploying atlas.I tried to deploy atlas service on my CDH cluster with CDH 
> version 5.16 and Kerberos service deployed.My installation method is Atlas 
> 1.2 integrated CDH HBase and external 5.5.1 Solr
> When I start the atlas service, I can successfully access the atlas web page 
> through my computer:
> !image-2020-08-25-16-29-29-667.png!
> But when I tried to import hive metadata information, something went wrong,as 
> shown in the figure below:
> !image-2020-08-25-16-30-34-221.png!
> !image-2020-08-25-16-38-45-645.png!
> !image-2020-08-25-16-31-28-330.png!
> It seems to indicate that I don't have a valid Kerberos principal?
> Here is part of my atlas configuration file  atlas-application.properties:
> !image-2020-08-25-16-34-41-642.png!
> !image-2020-08-25-16-35-09-836.png!
> Can anyone tell me what the problem is,thanks.
>  



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


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

2020-08-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues resolved ATLAS-3898.

Resolution: Fixed

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



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


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

2020-08-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Description: 
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This patch authorize read for all typedefs. It implicitly add read permission 
if create,update or delete permission is assigned to user.

  was:
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This jira propose to authorize read of classifications def to user with create 
permission.




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



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


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

2020-08-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Attachment: ATLAS-3898.1.patch

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



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


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

2020-08-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Attachment: (was: ATLAS-3898.2.patch)

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



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


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

2020-08-14 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Summary: Authorize read of typedefs  (was: Authorize read of 
Classifications def to user with create permission.)

> Authorize read of typedefs
> --
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3898.2.patch
>
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This jira propose to authorize read of classifications def to user with 
> create permission.



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


[jira] [Updated] (ATLAS-3915) impala_process startTime and endTime epoch is being set to 0

2020-08-10 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3915:
---
Affects Version/s: (was: 3.0.0)
   2.1.0

> impala_process startTime and endTime epoch is being set to 0
> 
>
> Key: ATLAS-3915
> URL: https://issues.apache.org/jira/browse/ATLAS-3915
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.1.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screenshot from 2020-08-10 12-42-45.png
>
>
> This patch fix following issue : impala process enitity start time and end 
> time was set 0 in the backend due to which the UI wasn't showing up timings.



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


[jira] [Updated] (ATLAS-3915) impala_process startTime and endTime epoch is being set to 0

2020-08-10 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3915:
---
Component/s: impala-integration

> impala_process startTime and endTime epoch is being set to 0
> 
>
> Key: ATLAS-3915
> URL: https://issues.apache.org/jira/browse/ATLAS-3915
> Project: Atlas
>  Issue Type: Improvement
>  Components: impala-integration
>Affects Versions: 2.1.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screenshot from 2020-08-10 12-42-45.png
>
>
> This patch fix following issue : impala process enitity start time and end 
> time was set 0 in the backend due to which the UI wasn't showing up timings.



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


[jira] [Updated] (ATLAS-3876) Relationship Search API not showing correct approximateCount

2020-08-05 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3876:
---
Fix Version/s: 3.0.0

> Relationship Search API not showing correct approximateCount
> 
>
> Key: ATLAS-3876
> URL: https://issues.apache.org/jira/browse/ATLAS-3876
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
> Fix For: 3.0.0
>
>
> Relationship Search API for hive columns showing *approximateCount* as -1 in 
> response.
>  E.g.
> {code:java}
> v2/search/relationship?limit=10=0=3e424245-0676-4d47-96a1-e17228b38367=__hive_table.columns=name=ASCENDING=true{code}



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


[jira] [Updated] (ATLAS-3898) Authorize read of Classifications def to user with create permission.

2020-07-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Attachment: ATLAS-3898.2.patch

> Authorize read of Classifications def to user with create permission.
> -
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3898.2.patch
>
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This jira propose to authorize read of classifications def to user with 
> create permission.



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


[jira] [Updated] (ATLAS-3898) Authorize read of Classifications def to user with create permission.

2020-07-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Description: 
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This jira propose to Currently in the Atlas-Ranger plugin for types resource 
READ permission is not available and read access is available by default to all 
types of any category.



  was:
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This jira propose to Currently in the Atlas-Ranger plugin for types resource 
READ permission is not available and read access is available by default to all 
types of any category.



> Authorize read of Classifications def to user with create permission.
> -
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This jira propose to Currently in the Atlas-Ranger plugin for types resource 
> READ permission is not available and read access is available by default to 
> all types of any category.



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


[jira] [Updated] (ATLAS-3898) Authorize read of Classifications def to user with create permission.

2020-07-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Description: 
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This jira propose to authorize read of classifications def to user with create 
permission.



  was:
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This jira propose to Currently in the Atlas-Ranger plugin for types resource 
READ permission is not available and read access is available by default to all 
types of any category.




> Authorize read of Classifications def to user with create permission.
> -
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This jira propose to authorize read of classifications def to user with 
> create permission.



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


[jira] [Updated] (ATLAS-3898) Authorize read of Classifications def to user with create permission.

2020-07-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Description: 
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This jira propose to Currently in the Atlas-Ranger plugin for types resource 
READ permission is not available and read access is available by default to all 
types of any category.


  was:
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This jira propose to 


> Authorize read of Classifications def to user with create permission.
> -
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This jira propose to Currently in the Atlas-Ranger plugin for types resource 
> READ permission is not available and read access is available by default to 
> all types of any category.



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


[jira] [Updated] (ATLAS-3898) Authorize read of Classifications def to user with create permission.

2020-07-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Description: 
Currently in the Atlas-Ranger plugin for types resource READ permission is not 
available and read access is available by default to all types of any category.

This jira propose to 

  was:Add Authorization for classification read so that classifications created 
by one user should not be visible to other users.


> Authorize read of Classifications def to user with create permission.
> -
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Currently in the Atlas-Ranger plugin for types resource READ permission is 
> not available and read access is available by default to all types of any 
> category.
> This jira propose to 



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


[jira] [Updated] (ATLAS-3898) Authorize read of Classifications def to user with create permission.

2020-07-28 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3898:
---
Summary: Authorize read of Classifications def to user with create 
permission.  (was: Authorization :- Classifications created by one user should 
not be visible to other users.)

> Authorize read of Classifications def to user with create permission.
> -
>
> Key: ATLAS-3898
> URL: https://issues.apache.org/jira/browse/ATLAS-3898
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> Add Authorization for classification read so that classifications created by 
> one user should not be visible to other users.



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


[jira] [Commented] (ATLAS-3901) AD user default role

2020-07-22 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3901:


[~theo11],

Atlas lookup for user group from local os linux  user group or from 
hadoopUserGroup mapping.
Please sync/map your AD users to os users / hadoop usergroup, so that groups 
are read correctly.

> AD user default role
> 
>
> Key: ATLAS-3901
> URL: https://issues.apache.org/jira/browse/ATLAS-3901
> Project: Atlas
>  Issue Type: Bug
>Reporter: theo11
>Priority: Major
>
> Hello,
> I'm having trouble to set up AD users to be correctly binded to DATA_STEWARD 
> role. Login works correctly, but user has no permissions like relationships 
> etc.
> Needed property in atlas-application.properties is set as follows:
> atlas.authentication.method.ldap.ad.default.role=DATA_STEWARD
> All roles are defaults from atlas-simple-authz-policy.json. There are no 
> related error entries in Atlas log.
> Could you advice?



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


[jira] [Comment Edited] (ATLAS-3833) Packaging for atlas index repair tool

2020-07-21 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues edited comment on ATLAS-3833 at 7/21/20, 7:10 AM:
--

The patch [^ATLAS-3833-1.patch] adds copying and assembling artifacts such jar, 
log4j xml , README and py file into tools/atlas-index-repair directory inside 
atlas-server distro package.  


was (Author: nixonrodrigues):
The patch [^ATLAS-3833-1.patch] adds copying and assembling artefacts such jar, 
log4j xml , README and py file into tools/atlas-index-repair directory inside 
atlas-server distro package.  

> Packaging for atlas index repair tool 
> --
>
> Key: ATLAS-3833
> URL: https://issues.apache.org/jira/browse/ATLAS-3833
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-3833-1.patch
>
>
> Packaging for atlas repair index was missing in Apache master build:
> Added descriptor in pom.xml for atlas-repair-index-package.xml
> Added readme
> Added atlas-repair-index-package.xml



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


[jira] [Reopened] (ATLAS-3833) Packaging for atlas index repair tool

2020-07-21 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues reopened ATLAS-3833:


> Packaging for atlas index repair tool 
> --
>
> Key: ATLAS-3833
> URL: https://issues.apache.org/jira/browse/ATLAS-3833
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-3833-1.patch
>
>
> Packaging for atlas repair index was missing in Apache master build:
> Added descriptor in pom.xml for atlas-repair-index-package.xml
> Added readme
> Added atlas-repair-index-package.xml



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


[jira] [Updated] (ATLAS-3833) Packaging for atlas index repair tool

2020-07-21 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3833:
---
Fix Version/s: (was: 2.0.0)

> Packaging for atlas index repair tool 
> --
>
> Key: ATLAS-3833
> URL: https://issues.apache.org/jira/browse/ATLAS-3833
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Attachments: ATLAS-3833-1.patch
>
>
> Packaging for atlas repair index was missing in Apache master build:
> Added descriptor in pom.xml for atlas-repair-index-package.xml
> Added readme
> Added atlas-repair-index-package.xml



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


[jira] [Commented] (ATLAS-3833) Packaging for atlas index repair tool

2020-07-21 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3833:


The patch [^ATLAS-3833-1.patch] adds copying and assembling artefacts such jar, 
log4j xml , README and py file into tools/atlas-index-repair directory inside 
atlas-server distro package.  

> Packaging for atlas index repair tool 
> --
>
> Key: ATLAS-3833
> URL: https://issues.apache.org/jira/browse/ATLAS-3833
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-3833-1.patch
>
>
> Packaging for atlas repair index was missing in Apache master build:
> Added descriptor in pom.xml for atlas-repair-index-package.xml
> Added readme
> Added atlas-repair-index-package.xml



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


[jira] [Updated] (ATLAS-3833) Packaging for atlas index repair tool

2020-07-21 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3833:
---
Attachment: ATLAS-3833-1.patch

> Packaging for atlas index repair tool 
> --
>
> Key: ATLAS-3833
> URL: https://issues.apache.org/jira/browse/ATLAS-3833
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-3833-1.patch
>
>
> Packaging for atlas repair index was missing in Apache master build:
> Added descriptor in pom.xml for atlas-repair-index-package.xml
> Added readme
> Added atlas-repair-index-package.xml



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


[jira] [Created] (ATLAS-3898) Authorization :- Classifications created by one user should not be visible to other users.

2020-07-20 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3898:
--

 Summary: Authorization :- Classifications created by one user 
should not be visible to other users.
 Key: ATLAS-3898
 URL: https://issues.apache.org/jira/browse/ATLAS-3898
 Project: Atlas
  Issue Type: New Feature
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues


Add Authorization for classification read so that classifications created by 
one user should not be visible to other users.



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


[jira] [Commented] (ATLAS-3894) UI: User is able to add and remove business metadata from deleted entities

2020-07-20 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3894:


+1 for the patch. thanks [~kevalbhatt]

> UI: User is able to add and remove business metadata from deleted entities
> --
>
> Key: ATLAS-3894
> URL: https://issues.apache.org/jira/browse/ATLAS-3894
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3894.patch
>
>
> User should not allow to add and remove the business metadata from the 
> deleted entity.



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


[jira] [Created] (ATLAS-3893) Update jackson lib version to 2.10.3

2020-07-15 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3893:
--

 Summary: Update jackson lib version to 2.10.3
 Key: ATLAS-3893
 URL: https://issues.apache.org/jira/browse/ATLAS-3893
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


In Atlas we have jackson 2.10.0, which is old. please update it to 2.10.3 to be 
sync with Ranger RANGER-2908 



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


[jira] [Assigned] (ATLAS-3893) Update jackson lib version to 2.10.3

2020-07-15 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues reassigned ATLAS-3893:
--

Assignee: Nixon Rodrigues

> Update jackson lib version to 2.10.3
> 
>
> Key: ATLAS-3893
> URL: https://issues.apache.org/jira/browse/ATLAS-3893
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> In Atlas we have jackson 2.10.0, which is old. please update it to 2.10.3 to 
> be sync with Ranger RANGER-2908 



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


[jira] [Commented] (ATLAS-3886) Import hive metastore failed for ConversionException error

2020-07-10 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3886:


[~yeleeo],

Can you provide steps you followed to step the atlas hive hooks libs ?
Which hive version are you using ?

Looks like there are multiple commons-configuration jar which execution, can 
you confirm this too.

> Import hive metastore failed for ConversionException error
> --
>
> Key: ATLAS-3886
> URL: https://issues.apache.org/jira/browse/ATLAS-3886
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, hive-integration
>Affects Versions: 2.1.0
> Environment: os: CentOS Linux release 7.6.1810 (Core)
> jdk:  java version "1.8.0_221"
> Java(TM) SE Runtime Environment (build 1.8.0_221-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 25.221-b11, mixed mode)
> hive: 2.3.2
> atlas: 2.1.0-rc2
>Reporter: Lijun Ye
>Priority: Major
>
> When I import hive metastore, it occur this exception:
> {code:java}
> // code placeholder
> org.apache.atlas.AtlasException: Failed to load application 
> propertiesorg.apache.atlas.AtlasException: Failed to load application 
> properties at 
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:147) 
> ~[atlas-intg-2.1.0.jar:2.1.0] at 
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:100) 
> ~[atlas-intg-2.1.0.jar:2.1.0] at 
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:123)
>  [hive-bridge-2.1.0.jar:2.1.0]Caused by: 
> org.apache.commons.configuration.ConversionException: 
> 'atlas.graph.index.search.solr.wait-searcher' doesn't map to a List object: 
> true, a java.lang.Boolean at 
> org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1144)
>  ~[commons-configuration-1.6.jar:1.6] at 
> org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1109)
>  ~[commons-configuration-1.6.jar:1.6] at 
> org.apache.commons.configuration.AbstractConfiguration.interpolatedConfiguration(AbstractConfiguration.java:1274)
>  ~[commons-configuration-1.6.jar:1.6] at 
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:142) 
> ~[atlas-intg-2.1.0.jar:2.1.0] ... 2 moreFailed to import Hive Meta Data!!!
> {code}



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


[jira] [Commented] (ATLAS-3886) Import hive metastore failed for ConversionException error

2020-07-10 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3886:


[~yeleeo], 

Is your atlas-application.properties file present path in /etc/hive/conf. Can 
you check this ?
Also can you share the atlas-application.properties file you are using.

LMK
Nixon

> Import hive metastore failed for ConversionException error
> --
>
> Key: ATLAS-3886
> URL: https://issues.apache.org/jira/browse/ATLAS-3886
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, hive-integration
>Affects Versions: 2.1.0
> Environment: os: CentOS Linux release 7.6.1810 (Core)
> jdk:  java version "1.8.0_221"
> Java(TM) SE Runtime Environment (build 1.8.0_221-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 25.221-b11, mixed mode)
> hive: 2.3.2
> atlas: 2.1.0-rc2
>Reporter: Lijun Ye
>Priority: Major
>
> When I import hive metastore, it occur this exception:
> {code:java}
> // code placeholder
> org.apache.atlas.AtlasException: Failed to load application 
> propertiesorg.apache.atlas.AtlasException: Failed to load application 
> properties at 
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:147) 
> ~[atlas-intg-2.1.0.jar:2.1.0] at 
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:100) 
> ~[atlas-intg-2.1.0.jar:2.1.0] at 
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:123)
>  [hive-bridge-2.1.0.jar:2.1.0]Caused by: 
> org.apache.commons.configuration.ConversionException: 
> 'atlas.graph.index.search.solr.wait-searcher' doesn't map to a List object: 
> true, a java.lang.Boolean at 
> org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1144)
>  ~[commons-configuration-1.6.jar:1.6] at 
> org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1109)
>  ~[commons-configuration-1.6.jar:1.6] at 
> org.apache.commons.configuration.AbstractConfiguration.interpolatedConfiguration(AbstractConfiguration.java:1274)
>  ~[commons-configuration-1.6.jar:1.6] at 
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:142) 
> ~[atlas-intg-2.1.0.jar:2.1.0] ... 2 moreFailed to import Hive Meta Data!!!
> {code}



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


[jira] [Commented] (ATLAS-3844) Ignore relationship attributes while fetching entities in Import Hive bridge.

2020-07-08 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3844:


patch for testcase failure in hive-brigde

[^ATLAS-3844-Testcase-Fix-Ignore-relationship-attributes-while-fetc.patch] 

> Ignore relationship attributes while fetching entities in Import Hive bridge.
> -
>
> Key: ATLAS-3844
> URL: https://issues.apache.org/jira/browse/ATLAS-3844
> Project: Atlas
>  Issue Type: Improvement
>  Components: hive-integration
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-ATLAS-3844-Ignore-relationship-attributes-while-fetc.patch, 
> ATLAS-3844-Testcase-Fix-Ignore-relationship-attributes-while-fetc.patch
>
>
> Currently in Import Hive bridge, the hive_db and hive_table entities are 
> fetched along relationshipAttributes and related Attributes and this 
> attributes are cleared thereafter.
> Instead fetching relationshipAttributes and related Attributes in response, 
> it is will good to ignoreRelationship to reduce the size of response payload.



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


[jira] [Updated] (ATLAS-3844) Ignore relationship attributes while fetching entities in Import Hive bridge.

2020-07-08 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3844:
---
Attachment: 
ATLAS-3844-Testcase-Fix-Ignore-relationship-attributes-while-fetc.patch

> Ignore relationship attributes while fetching entities in Import Hive bridge.
> -
>
> Key: ATLAS-3844
> URL: https://issues.apache.org/jira/browse/ATLAS-3844
> Project: Atlas
>  Issue Type: Improvement
>  Components: hive-integration
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-ATLAS-3844-Ignore-relationship-attributes-while-fetc.patch, 
> ATLAS-3844-Testcase-Fix-Ignore-relationship-attributes-while-fetc.patch
>
>
> Currently in Import Hive bridge, the hive_db and hive_table entities are 
> fetched along relationshipAttributes and related Attributes and this 
> attributes are cleared thereafter.
> Instead fetching relationshipAttributes and related Attributes in response, 
> it is will good to ignoreRelationship to reduce the size of response payload.



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


[jira] [Commented] (ATLAS-3882) Classic UI: Loader not disappearing while assigning category to term

2020-07-08 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3882:


+1 for the patch, thanks [~kevalbhatt]

> Classic UI: Loader not disappearing while assigning category to term 
> -
>
> Key: ATLAS-3882
> URL: https://issues.apache.org/jira/browse/ATLAS-3882
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3882.patch, Screen Shot 2020-07-07 at 3.18.20 
> PM.png
>
>
> Steps to reproduce this issue.
>  
>  # Go to classic UI
>  # Click on Glossary tab
>  # Create term if not exist and click on it
>  # Click on + button of Categories: from the righthand side view of the term 
> detail page.
>  # The popup will be visible with loader.
>  
> !Screen Shot 2020-07-07 at 3.18.20 PM.png|width=579,height=248!



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


[jira] [Resolved] (ATLAS-3883) Upgrade jackson-databind to version 2.10.0

2020-07-08 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues resolved ATLAS-3883.

Resolution: Duplicate

> Upgrade jackson-databind to version 2.10.0
> --
>
> Key: ATLAS-3883
> URL: https://issues.apache.org/jira/browse/ATLAS-3883
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
>
> Upgrade to jackson-databind to version 2.10.0 
> 
> com.fasterxml.jackson.core
> jackson-databind
> 2.10.0
> 



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


[jira] [Commented] (ATLAS-3883) Upgrade jackson-databind to version 2.10.0

2020-07-08 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3883:


Fix handled in ATLAS-3452 Update jackson.databind.version to 2.10.0



> Upgrade jackson-databind to version 2.10.0
> --
>
> Key: ATLAS-3883
> URL: https://issues.apache.org/jira/browse/ATLAS-3883
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
>
> Upgrade to jackson-databind to version 2.10.0 
> 
> com.fasterxml.jackson.core
> jackson-databind
> 2.10.0
> 



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


[jira] [Created] (ATLAS-3883) Upgrade jackson-databind to version 2.10.0

2020-07-08 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3883:
--

 Summary: Upgrade jackson-databind to version 2.10.0
 Key: ATLAS-3883
 URL: https://issues.apache.org/jira/browse/ATLAS-3883
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


Upgrade to jackson-databind to version 2.10.0 


com.fasterxml.jackson.core
jackson-databind
2.10.0




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


[jira] [Resolved] (ATLAS-3844) Ignore relationship attributes while fetching entities in Import Hive bridge.

2020-07-06 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues resolved ATLAS-3844.

Resolution: Fixed

> Ignore relationship attributes while fetching entities in Import Hive bridge.
> -
>
> Key: ATLAS-3844
> URL: https://issues.apache.org/jira/browse/ATLAS-3844
> Project: Atlas
>  Issue Type: Improvement
>  Components: hive-integration
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-ATLAS-3844-Ignore-relationship-attributes-while-fetc.patch
>
>
> Currently in Import Hive bridge, the hive_db and hive_table entities are 
> fetched along relationshipAttributes and related Attributes and this 
> attributes are cleared thereafter.
> Instead fetching relationshipAttributes and related Attributes in response, 
> it is will good to ignoreRelationship to reduce the size of response payload.



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


[jira] [Updated] (ATLAS-3873) branch-0.8 - Optimisation for findByTypeAndPropertyName method and isNotEmpty check for entityType.getAllSubTypes()

2020-07-01 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3873:
---
Attachment: ATLAS-3873-branch-0.8.patch

> branch-0.8 - Optimisation for findByTypeAndPropertyName method and isNotEmpty 
> check for entityType.getAllSubTypes()
> ---
>
> Key: ATLAS-3873
> URL: https://issues.apache.org/jira/browse/ATLAS-3873
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.3
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 0.8.4
>
> Attachments: ATLAS-3873-branch-0.8.patch
>
>
> Optimisation for findByTypeAndPropertyName method and isNotEmpty check for 
> entityType.getAllSubTypes() on branch-0.8.



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


[jira] [Created] (ATLAS-3873) branch-0.8 - Optimisation for findByTypeAndPropertyName method and isNotEmpty check for entityType.getAllSubTypes()

2020-07-01 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3873:
--

 Summary: branch-0.8 - Optimisation for findByTypeAndPropertyName 
method and isNotEmpty check for entityType.getAllSubTypes()
 Key: ATLAS-3873
 URL: https://issues.apache.org/jira/browse/ATLAS-3873
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.8.3
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: 0.8.4


Optimisation for findByTypeAndPropertyName method and isNotEmpty check for 
entityType.getAllSubTypes() on branch-0.8.



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


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

2020-07-01 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3870:


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

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



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


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

2020-07-01 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3869:
---
Fix Version/s: 3.0.0

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

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

2020-06-30 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3869:
---
Attachment: ATLAS-3869-Upgrade-httpclient-from-4.5.3-to-4.5.4.patch

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

[jira] [Commented] (ATLAS-3488) Update with Filebased auth password with ShaPasswordEncoder with salt.

2020-06-30 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3488:


[~18810276...@163.com]

"org.apache.hadoop.hive.metastore.api.Database.getCatalogName()"ERROR?

 This is issue is due to mismatch in hive version, Atlas expects hive with 
version 3.1.0.

 

from the logs from provided. 
{noformat}
17:47:41.269 [main] DEBUG org.apache.atlas.AtlasBaseClient - Call : GET 
api/atlas/v2/entity/uniqueAttribute/type/
17:47:41.269 [main] DEBUG org.apache.atlas.AtlasBaseClient - Content-type : 
application/json; charset=UTF-8
17:47:41.269 [main] DEBUG org.apache.atlas.AtlasBaseClient - Accept : 
application/json
17:47:41.283 [main] DEBUG org.apache.atlas.AtlasBaseClient - HTTP Status : 404
{noformat}
 its giving 404 since database do not exist in Atlas and authentication has 
passed. if there was authentication issue then it will give 401.

  

> Update with Filebased auth password with ShaPasswordEncoder with salt.
> --
>
> Key: ATLAS-3488
> URL: https://issues.apache.org/jira/browse/ATLAS-3488
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3488.07.patch, ATLAS-3488.6.patch
>
>
> Current password is encoded with {{sha256 method for filebased 
> authentication.}}
>  
> {{Update the password with }}{{sha256}}{{ with salt encoding which is more 
> secured.}}
>  



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


[jira] [Commented] (ATLAS-3488) Update with Filebased auth password with ShaPasswordEncoder with salt.

2020-06-30 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3488:


[~18810276...@163.com],

I verified quick-start.py which is using same authentication route and its 
working correctly with admin/admin.

can you verify if you are using same users-credentials.properties file provided 
in 2.1.0-rc1  bits.

admin=ADMIN::a4a88c0872bf652bb9ed803ece5fd6e82354838a9bf59ab4babb1dab322154e1

> Update with Filebased auth password with ShaPasswordEncoder with salt.
> --
>
> Key: ATLAS-3488
> URL: https://issues.apache.org/jira/browse/ATLAS-3488
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3488.07.patch, ATLAS-3488.6.patch
>
>
> Current password is encoded with {{sha256 method for filebased 
> authentication.}}
>  
> {{Update the password with }}{{sha256}}{{ with salt encoding which is more 
> secured.}}
>  



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


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

2020-06-30 Thread Nixon Rodrigues (Jira)
Nixon Rodrigues created ATLAS-3869:
--

 Summary: Upgrade httpclient from 4.5.3 to 4.5.4
 Key: ATLAS-3869
 URL: https://issues.apache.org/jira/browse/ATLAS-3869
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues


Found below exception where data was not getting added in SOLR from janusgraph.

 
{noformat}
Caused by: java.lang.ClassCastException: [B cannot be cast to java.lang.String
at 
org.apache.http.conn.ssl.DefaultHostnameVerifier.getSubjectAltNames(DefaultHostnameVerifier.java:309)
at 
org.apache.http.conn.ssl.DefaultHostnameVerifier.verify(DefaultHostnameVerifier.java:112)
at 
org.apache.http.conn.ssl.DefaultHostnameVerifier.verify(DefaultHostnameVerifier.java:99)
at 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:463)
at 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:397)
at 
org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355)
at 
org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
at 
org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:359)
at 
org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
at 
org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
at 
org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at 
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
at 
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at 
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at 
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:526)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:253)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:242)
at 
org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:483)
... 7 more
2020-06-29 07:31:25,893 WARN  - [SIGTERM handler:] ~ Unable to close 
transaction standardjanusgraphtx[0x18d7a16a] (StandardJanusGraph:230)
java.lang.IllegalArgumentException: The transaction has already been closed
at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:142)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.rollback(StandardJanusGraphTx.java:1401)
at 
org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction$1.doRollback(JanusGraphBlueprintsTransaction.java:190)
at 
org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.rollback(AbstractTransaction.java:114)
at 
org.apache.tinkerpop.gremlin.structure.Transaction$CLOSE_BEHAVIOR$2.accept(Transaction.java:182)
at 
org.apache.tinkerpop.gremlin.structure.Transaction$CLOSE_BEHAVIOR$2.accept(Transaction.java:179)
at 
org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.close(JanusGraphBlueprintsGraph.java:327)
at 
org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction$1.doClose(JanusGraphBlueprintsTransaction.java:205)
at 
org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.close(AbstractTransaction.java:139)
at 
org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction.close(JanusGraphBlueprintsTransaction.java:215)
at 
org.janusgraph.graphdb.database.StandardJanusGraph.closeInternal(StandardJanusGraph.java:226)
at 
org.janusgraph.graphdb.database.StandardJanusGraph.access$500(StandardJanusGraph.java:91)
at 
org.janusgraph.graphdb.database.StandardJanusGraph$ShutdownThread.start(StandardJanusGraph.java:818)
at 
java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:102)
at 
java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
at java.lang.Shutdown.runHooks(Shutdown.java:123)
at java.lang.Shutdown.sequence(Shutdown.java:167)
at java.lang.Shutdown.exit(Shutdown.java:212)
at java.lang.Terminator$1.handle(Terminator.java:52)
at sun.misc.Signal$1.run(Signal.java:212)
at java.lang.Thread.run(Thread.java:745)
{noformat}
its due to HTTPCLIENT-1836 

To fix above issue:- Upgrade httpclient from 4.5.3 to 4.5.4.

 



--
This message was sent by Atlassian Jira

[jira] [Commented] (ATLAS-3859) [UI] In edit entity window shows calender with 'Invalid date'

2020-06-25 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3859:


+1 for the patch. thanks [~kevalbhatt]

> [UI] In edit entity window shows calender with 'Invalid date'
> -
>
> Key: ATLAS-3859
> URL: https://issues.apache.org/jira/browse/ATLAS-3859
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: ATLAS-3859.patch, shows Invalid date with 'NaN'.webm
>
>
> Steps to reproduce::
>  # {color:#00}Open entity in edit mode{color}
>  # {color:#00}Click on toggle 'Required' set to ALL {color}
>  # {color:#00}For 'Created Time' shows 'Invalid Date' {color}
>  # {color:#00}When Opened calender shows 'NaN' for all the dates{color}
> {color:#00}Expected: Calender should be available with dates to select 
> the required date
> {color}
> {color:#00}Actual: Shows NaN all over the calender{color}



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


[jira] [Commented] (ATLAS-3848) Quick Search : Incorrect aggregation metrics

2020-06-25 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues commented on ATLAS-3848:


+1 for the patch, thanks [~pinal.shah] for the patch

> Quick Search : Incorrect aggregation metrics
> 
>
> Key: ATLAS-3848
> URL: https://issues.apache.org/jira/browse/ATLAS-3848
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: quicksearch
> Fix For: 2.1.0, 3.0.0
>
>
> Below scenarios doesn't result correct aggregation metrics in quick search
>  * when filtered with System Attributes
>  * when filtered with more than one filters
>  * when filtered with negation operators
>  * need to support _customAttributes 



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


[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.

2020-06-23 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3853:
---
Description: 
 

*_The issue :_* 

The enumValue which we assigned  ">"  has double quotes in it.the 
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]{'

{', '}

', '"', '\u001e'}; into it.

*_How to reproduce it ? Steps to reproduce :_*

Step 1 : Create an enum e.g enumXSS.

Step 2 : create a classification with some attribute of type enumXSS.

Step 3 : Assign a value for this attribute with  ">"Now this will result into an error with 
500 saying "Something went wrong"

*Approach for resolving this :* 

As the janusgraph has this check for special characters and our enumValue has 
that double quotes in it it throws an illelagalArgumentException.

Now at Atlas end we are not handling the unexpected exception so we just have 
to catch the Exception and throw it with proper error code and error-message 
which helps user to  understand the issue properly.And for that i have provided 
the patch on RR.

 

 *Stack-trace:-*
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 
__type.edge.classitest.">
at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at 
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at 
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.makeEdgeLabel(StandardJanusGraphTx.java:1052)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getOrCreateEdgeLabel(StandardJanusGraphTx.java:1038)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:167)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:37)
at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.addEdge(AtlasJanusGraph.java:147)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.addEdge(AtlasTypeDefGraphStoreV2.java:395)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.getOrCreateEdge(AtlasTypeDefGraphStoreV2.java:387)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.addReferencesForAttribute(AtlasStructDefStoreV2.java:523)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.updateVertexAddReferences(AtlasStructDefStoreV2.java:471)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateVertexAddReferences(AtlasClassificationDefStoreV2.java:338)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateByGuid(AtlasClassificationDefStoreV2.java:254)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:183)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:48)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateGraphStore(AtlasTypeDefGraphStore.java:1029)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateTypesDef(AtlasTypeDefGraphStore.java:481)
{noformat}
 

  was:
 

_The issue :_ 

The enumValue which we assigned  ">"  has double quotes in it.the 
janusgraph's class SystemTypeManager.java has RESERVED_CHARS = new char[]{'

{', '}

', '"', '\u001e'}; into it.

_How to reproduce it ? Steps to reproduce :_

Step 1 : Create an enum e.g enumXSS.

Step 2 : create a classification with some attribute of type enumXSS.

Step 3 : Assign a value for this attribute with  ">"Now this will result into an error with 
500 saying "Something went wrong"

_Approach for resolving this :_ 

As the janusgraph has this check for special characters and our enumValue has 
that double quotes in it it throws an illelagalArgumentException.

Now at Atlas end we are not handling the unexpected exception so we just have 
to catch the Exception and throw it with proper error code and error-message 
which helps user to  understand the issue properly.And for that i have provided 
the patch on RR.

 

 Stack-trace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 

[jira] [Updated] (ATLAS-3853) Error while creating enum Attribute with special characters.

2020-06-22 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3853:
---
Description: 
I had created an enum with some value in it, and a classification 
ClassificationTest1, now while i was adding an attribute to my 
ClassificationTest1 the value i assigne the enumValue was  

">

and instead of throwing some kind of error message the application threw 
"Something went wrong"  with 500 error code.

The end user in such scenario won't be able to identify what exactly went wrong.

 Stacktrace:-
{noformat}
2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
37492d4b-63b4-4189-89c3-329b0566ae74:]
 ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
java.lang.IllegalArgumentException: Name contains reserved character ": 
__type.edge.classitest.">
at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
at 
org.janusgraph.graphdb.types.system.SystemTypeManager.throwIfSystemName(SystemTypeManager.java:74)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.name(StandardRelationTypeMaker.java:181)
at 
org.janusgraph.graphdb.types.StandardRelationTypeMaker.(StandardRelationTypeMaker.java:53)
at 
org.janusgraph.graphdb.types.StandardEdgeLabelMaker.(StandardEdgeLabelMaker.java:41)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.makeEdgeLabel(StandardJanusGraphTx.java:1052)
at 
org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getOrCreateEdgeLabel(StandardJanusGraphTx.java:1038)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:167)
at 
org.janusgraph.graphdb.vertices.AbstractVertex.addEdge(AbstractVertex.java:37)
at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.addEdge(AtlasJanusGraph.java:147)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.addEdge(AtlasTypeDefGraphStoreV2.java:395)
at 
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2.getOrCreateEdge(AtlasTypeDefGraphStoreV2.java:387)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.addReferencesForAttribute(AtlasStructDefStoreV2.java:523)
at 
org.apache.atlas.repository.store.graph.v2.AtlasStructDefStoreV2.updateVertexAddReferences(AtlasStructDefStoreV2.java:471)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateVertexAddReferences(AtlasClassificationDefStoreV2.java:338)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.updateByGuid(AtlasClassificationDefStoreV2.java:254)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:183)
at 
org.apache.atlas.repository.store.graph.v2.AtlasClassificationDefStoreV2.update(AtlasClassificationDefStoreV2.java:48)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateGraphStore(AtlasTypeDefGraphStore.java:1029)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateTypesDef(AtlasTypeDefGraphStore.java:481)
{noformat}
 

  was:
I had created an enum with some value in it, and a classification 
ClassificationTest1, now while i was adding an attribute to my 
ClassificationTest1 the value i assigne the enumValue was  

">

and instead of throwing some kind of error message the application threw 
"Something went wrong"  with 500 error code.

The end user in such scenario won't be able to identify what exactly went wrong.

 


> Error while creating enum Attribute with special characters.
> 
>
> Key: ATLAS-3853
> URL: https://issues.apache.org/jira/browse/ATLAS-3853
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mayank Jain
>Assignee: Mayank Jain
>Priority: Major
> Attachments: errorStackTrace.txt
>
>
> I had created an enum with some value in it, and a classification 
> ClassificationTest1, now while i was adding an attribute to my 
> ClassificationTest1 the value i assigne the enumValue was  
> ">
> and instead of throwing some kind of error message the application threw 
> "Something went wrong"  with 500 error code.
> The end user in such scenario won't be able to identify what exactly went 
> wrong.
>  Stacktrace:-
> {noformat}
> 2020-06-19 17:05:32,390 ERROR - [pool-2-thread-7 - 
> 37492d4b-63b4-4189-89c3-329b0566ae74:]
>  ~ graph rollback due to exception  (GraphTransactionInterceptor:167)
> java.lang.IllegalArgumentException: Name contains reserved character ": 
> __type.edge.classitest.">
>   at 
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:163)
>   at 
> 

[jira] [Updated] (ATLAS-3844) Ignore relationship attributes while fetching entities in Import Hive bridge.

2020-06-17 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3844:
---
Attachment: 0001-ATLAS-3844-Ignore-relationship-attributes-while-fetc.patch

> Ignore relationship attributes while fetching entities in Import Hive bridge.
> -
>
> Key: ATLAS-3844
> URL: https://issues.apache.org/jira/browse/ATLAS-3844
> Project: Atlas
>  Issue Type: Improvement
>  Components: hive-integration
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-ATLAS-3844-Ignore-relationship-attributes-while-fetc.patch
>
>
> Currently in Import Hive bridge, the hive_db and hive_table entities are 
> fetched along relationshipAttributes and related Attributes and this 
> attributes are cleared thereafter.
> Instead fetching relationshipAttributes and related Attributes in response, 
> it is will good to ignoreRelationship to reduce the size of response payload.



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


[jira] [Updated] (ATLAS-3844) Ignore relationship attributea while fetching entities in Import Hive bridge.

2020-06-17 Thread Nixon Rodrigues (Jira)


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

Nixon Rodrigues updated ATLAS-3844:
---
Summary: Ignore relationship attributea while fetching entities in Import 
Hive bridge.  (was: Ignore relationship attribute while fetching entities in 
Import Hive bridge.)

> Ignore relationship attributea while fetching entities in Import Hive bridge.
> -
>
> Key: ATLAS-3844
> URL: https://issues.apache.org/jira/browse/ATLAS-3844
> Project: Atlas
>  Issue Type: Improvement
>  Components: hive-integration
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
>
> Currently in Import Hive bridge, the hive_db and hive_table entities are 
> fetched along relationshipAttributes and related Attributes and this 
> attributes are cleared thereafter.
> Instead fetching relationshipAttributes and related Attributes in response, 
> it is will good to ignoreRelationship to reduce the size of response payload.



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


  1   2   3   4   5   6   7   8   >