[jira] [Resolved] (ATLAS-1946) LDAPS(LDAP over SSL) support in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1946. Resolution: Information Provided > LDAPS(LDAP over SSL) support in Atlas > - > > Key: ATLAS-1946 > URL: https://issues.apache.org/jira/browse/ATLAS-1946 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Ayub Pathan >Priority: Major > > Add support for LDAPS in Atlas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-1946) LDAPS(LDAP over SSL) support in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736359#comment-17736359 ] Nixon Rodrigues commented on ATLAS-1946: yes. can close h3. [Steps to setup Atlas with Ldaps (SSL)|https://community.cloudera.com/t5/Community-Articles/Steps-to-setup-Atlas-with-Ldaps-SSL/ta-p/247365] > LDAPS(LDAP over SSL) support in Atlas > - > > Key: ATLAS-1946 > URL: https://issues.apache.org/jira/browse/ATLAS-1946 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Ayub Pathan >Priority: Major > > Add support for LDAPS in Atlas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4760) Unable to build Atlas project due to various dependency issues
[
https://issues.apache.org/jira/browse/ATLAS-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735524#comment-17735524
]
Nixon Rodrigues commented on ATLAS-4760:
{quote}What exactly is Apache atlas server expecting at
`/etc/alternatives/jre/bin/jar` is it java or any other ? I don't see any
specific instructions on this. Is this not part of installation or should I do
anything more to get Apache Atlas up and running ?
{quote}
I feel there is issue with your instance PATH and JAVA_HOME path, please check
{quote}Also should I create a PR for the above issue (repository fix at
pom.xml) as many other might be facing the same issue ?
{quote}
This is fixed on master, should be released in coming minor release.
> Unable to build Atlas project due to various dependency issues
> --
>
> Key: ATLAS-4760
> URL: https://issues.apache.org/jira/browse/ATLAS-4760
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.3.0
> Environment: -- cat /etc/os-release
> NAME="Amazon Linux"
> VERSION="2"
> ID="amzn"
> ID_LIKE="centos rhel fedora"
> VERSION_ID="2"
> PRETTY_NAME="Amazon Linux 2"
> ANSI_COLOR="0;33"
> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
> HOME_URL="https://amazonlinux.com/;
> -- uname -r
> 4.14.313-235.533.amzn2.x86_64
>Reporter: Udaykiran Reddy
>Priority: Blocker
> Labels: build-failure, deployment
>
> Unable to build Atlas project due to various dependency issues
> Java - 1.8
> Maven - 3.9.2
> Atlas version - 2.3.0 –
> [https://atlas.apache.org/2.3.0/index.html#/Downloads]
> Error
> {code:java}
> [INFO]
>
> [INFO] Reactor Summary for apache-atlas 2.3.0:
> [INFO]
> [INFO] Apache Atlas Server Build Tools SUCCESS [ 3.395
> s]
> [INFO] apache-atlas ... SUCCESS [ 10.087
> s]
> [INFO] Apache Atlas Integration ... SUCCESS [ 15.802
> s]
> [INFO] Apache Atlas Test Utility Tools FAILURE [ 4.474
> s]
> [INFO] Apache Atlas Common SKIPPED
> [INFO] Apache Atlas Client SKIPPED
> [INFO] atlas-client-common SKIPPED
> [INFO] atlas-client-v1 SKIPPED
> [INFO] Apache Atlas Server API SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] atlas-client-v2 SKIPPED
> [INFO] Apache Atlas Graph Database Projects ... SKIPPED
> [INFO] Apache Atlas Graph Database API SKIPPED
> [INFO] Graph Database Common Code . SKIPPED
> [INFO] Apache Atlas JanusGraph-HBase2 Module .. SKIPPED
> [INFO] Apache Atlas JanusGraph DB Impl SKIPPED
> [INFO] Apache Atlas Graph DB Dependencies . SKIPPED
> [INFO] Apache Atlas Authorization . SKIPPED
> [INFO] Apache Atlas Repository SKIPPED
> [INFO] Apache Atlas UI SKIPPED
> [INFO] Apache Atlas New UI SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas FileSystem Model .. SKIPPED
> [INFO] Apache Atlas Plugin Classloader SKIPPED
> [INFO] Apache Atlas Hive Bridge Shim .. SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO] Apache Atlas Falcon Bridge Shim SKIPPED
> [INFO] Apache Atlas Falcon Bridge . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge Shim . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge .. SKIPPED
> [INFO] Apache Atlas Storm Bridge Shim . SKIPPED
> [INFO] Apache Atlas Storm Bridge .. SKIPPED
> [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
[jira] [Comment Edited] (ATLAS-4760) Unable to build Atlas project due to various dependency issues
[
https://issues.apache.org/jira/browse/ATLAS-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733480#comment-17733480
]
Nixon Rodrigues edited comment on ATLAS-4760 at 6/16/23 12:20 PM:
--
{code:java}
maven-restlet
Public online Restlet repository
https://maven.restlet.talend.com/
{code}
[~udaykiranciq] , check if above repository is added in
[pom.xml|https://github.com/apache/atlas/blob/master/pom.xml#LL902C9-L906C22],
else add and try the build
was (Author: nixonrodrigues):
maven-restlet
Public online Restlet repository
https://maven.restlet.talend.com/
[~udaykiranciq] , check if above repository is added in
[pom.xml|https://github.com/apache/atlas/blob/master/pom.xml#LL902C9-L906C22],
else add and try the build
> Unable to build Atlas project due to various dependency issues
> --
>
> Key: ATLAS-4760
> URL: https://issues.apache.org/jira/browse/ATLAS-4760
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.3.0
> Environment: -- cat /etc/os-release
> NAME="Amazon Linux"
> VERSION="2"
> ID="amzn"
> ID_LIKE="centos rhel fedora"
> VERSION_ID="2"
> PRETTY_NAME="Amazon Linux 2"
> ANSI_COLOR="0;33"
> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
> HOME_URL="https://amazonlinux.com/;
> -- uname -r
> 4.14.313-235.533.amzn2.x86_64
>Reporter: Udaykiran Reddy
>Priority: Blocker
> Labels: build-failure, deployment
>
> Unable to build Atlas project due to various dependency issues
> Java - 1.8
> Maven - 3.9.2
> Atlas version - 2.3.0 –
> [https://atlas.apache.org/2.3.0/index.html#/Downloads]
> Error
> {code:java}
> [INFO]
>
> [INFO] Reactor Summary for apache-atlas 2.3.0:
> [INFO]
> [INFO] Apache Atlas Server Build Tools SUCCESS [ 3.395
> s]
> [INFO] apache-atlas ... SUCCESS [ 10.087
> s]
> [INFO] Apache Atlas Integration ... SUCCESS [ 15.802
> s]
> [INFO] Apache Atlas Test Utility Tools FAILURE [ 4.474
> s]
> [INFO] Apache Atlas Common SKIPPED
> [INFO] Apache Atlas Client SKIPPED
> [INFO] atlas-client-common SKIPPED
> [INFO] atlas-client-v1 SKIPPED
> [INFO] Apache Atlas Server API SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] atlas-client-v2 SKIPPED
> [INFO] Apache Atlas Graph Database Projects ... SKIPPED
> [INFO] Apache Atlas Graph Database API SKIPPED
> [INFO] Graph Database Common Code . SKIPPED
> [INFO] Apache Atlas JanusGraph-HBase2 Module .. SKIPPED
> [INFO] Apache Atlas JanusGraph DB Impl SKIPPED
> [INFO] Apache Atlas Graph DB Dependencies . SKIPPED
> [INFO] Apache Atlas Authorization . SKIPPED
> [INFO] Apache Atlas Repository SKIPPED
> [INFO] Apache Atlas UI SKIPPED
> [INFO] Apache Atlas New UI SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas FileSystem Model .. SKIPPED
> [INFO] Apache Atlas Plugin Classloader SKIPPED
> [INFO] Apache Atlas Hive Bridge Shim .. SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO] Apache Atlas Falcon Bridge Shim SKIPPED
> [INFO] Apache Atlas Falcon Bridge . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge Shim . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge .. SKIPPED
> [INFO] Apache Atlas Storm Bridge Shim . SKIPPED
> [INFO] Apache Atlas Storm Bridge .. SKIPPED
> [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
[jira] [Commented] (ATLAS-4760) Unable to build Atlas project due to various dependency issues
[
https://issues.apache.org/jira/browse/ATLAS-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17733480#comment-17733480
]
Nixon Rodrigues commented on ATLAS-4760:
maven-restlet
Public online Restlet repository
https://maven.restlet.talend.com/
[~udaykiranciq] , check if above repository is added in
[pom.xml|https://github.com/apache/atlas/blob/master/pom.xml#LL902C9-L906C22],
else add and try the build
> Unable to build Atlas project due to various dependency issues
> --
>
> Key: ATLAS-4760
> URL: https://issues.apache.org/jira/browse/ATLAS-4760
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.3.0
> Environment: -- cat /etc/os-release
> NAME="Amazon Linux"
> VERSION="2"
> ID="amzn"
> ID_LIKE="centos rhel fedora"
> VERSION_ID="2"
> PRETTY_NAME="Amazon Linux 2"
> ANSI_COLOR="0;33"
> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
> HOME_URL="https://amazonlinux.com/;
> -- uname -r
> 4.14.313-235.533.amzn2.x86_64
>Reporter: Udaykiran Reddy
>Priority: Blocker
> Labels: build-failure, deployment
>
> Unable to build Atlas project due to various dependency issues
> Java - 1.8
> Maven - 3.9.2
> Atlas version - 2.3.0 –
> [https://atlas.apache.org/2.3.0/index.html#/Downloads]
> Error
> {code:java}
> [INFO]
>
> [INFO] Reactor Summary for apache-atlas 2.3.0:
> [INFO]
> [INFO] Apache Atlas Server Build Tools SUCCESS [ 3.395
> s]
> [INFO] apache-atlas ... SUCCESS [ 10.087
> s]
> [INFO] Apache Atlas Integration ... SUCCESS [ 15.802
> s]
> [INFO] Apache Atlas Test Utility Tools FAILURE [ 4.474
> s]
> [INFO] Apache Atlas Common SKIPPED
> [INFO] Apache Atlas Client SKIPPED
> [INFO] atlas-client-common SKIPPED
> [INFO] atlas-client-v1 SKIPPED
> [INFO] Apache Atlas Server API SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] atlas-client-v2 SKIPPED
> [INFO] Apache Atlas Graph Database Projects ... SKIPPED
> [INFO] Apache Atlas Graph Database API SKIPPED
> [INFO] Graph Database Common Code . SKIPPED
> [INFO] Apache Atlas JanusGraph-HBase2 Module .. SKIPPED
> [INFO] Apache Atlas JanusGraph DB Impl SKIPPED
> [INFO] Apache Atlas Graph DB Dependencies . SKIPPED
> [INFO] Apache Atlas Authorization . SKIPPED
> [INFO] Apache Atlas Repository SKIPPED
> [INFO] Apache Atlas UI SKIPPED
> [INFO] Apache Atlas New UI SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas FileSystem Model .. SKIPPED
> [INFO] Apache Atlas Plugin Classloader SKIPPED
> [INFO] Apache Atlas Hive Bridge Shim .. SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO] Apache Atlas Falcon Bridge Shim SKIPPED
> [INFO] Apache Atlas Falcon Bridge . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge Shim . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge .. SKIPPED
> [INFO] Apache Atlas Storm Bridge Shim . SKIPPED
> [INFO] Apache Atlas Storm Bridge .. SKIPPED
> [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 . SKIPPED
> [INFO]
>
>
[jira] [Commented] (ATLAS-4742) Everytime changeover happens ,Atlas is taking almost an hour to switch over from PASSIVE to ACTIVE in HA mode.
[ https://issues.apache.org/jira/browse/ATLAS-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709320#comment-17709320 ] Nixon Rodrigues commented on ATLAS-4742: may be hitting this issue - https://issues.apache.org/jira/browse/ATLAS-4358 > Everytime changeover happens ,Atlas is taking almost an hour to switch over > from PASSIVE to ACTIVE in HA mode. > -- > > Key: ATLAS-4742 > URL: https://issues.apache.org/jira/browse/ATLAS-4742 > Project: Atlas > Issue Type: Bug >Reporter: Jagadesh Kiran N >Priority: Major > Attachments: application.log, image001.png > > > We have tried setting up Apache atlas(2.2.0) in High availability mode in > Kubernetes with separate pods for two instance. > > When we simulate a failure on active instance, the failover from passive > instance from active instance is taking over an hour to complete the > transition. This happens when we have created around 300 entities whereas > when we simulated the same failover on fresh install of Atlas, it completed > the transition in 15 minutes. > > This is the log before the failover for the passive instance: > The logs after the failover is in the attached file. This is the failover > during a fresh install. It is doing the similar process but taking more time > when there are more entities created in Atlas. > Warning : [main:] ~ Query requires iterating over all vertices [(__patch.id = > JAVA_PATCH__006)]. For better performance, use indexes > (StandardJanusGraphTx$3:1357) > > Observation : Everytime switchover happens its recreating repetitively > every-time internal typedef's because of which switchover time is more than 1 > hr > Please suggest how to go about the same , -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3671) Maven Package Failure
[
https://issues.apache.org/jira/browse/ATLAS-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690364#comment-17690364
]
Nixon Rodrigues commented on ATLAS-3671:
{code:java}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 04:33 min (Wall Clock)
[INFO] Finished at: 2023-02-17T11:01:53Z
[INFO]
Error: Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(process-resource-bundles) on project storm-bridge-shim: Error resolving
project artifact: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
from/to hortonworks.repo
(https://repo.hortonworks.com/content/repositories/releases): transfer failed
for
https://repo.hortonworks.com/content/repositories/releases/com/twitter/carbonite/1.5.0/carbonite-1.5.0.pom,
status: 504 Gateway Time-out for project com.twitter:carbonite:jar:1.5.0 ->
[Help 1]
Error:
Error: To see the full stack trace of the errors, re-run Maven with the -e
switch.
Error: Re-run Maven using the -X switch to enable full debug logging.
Error:
Error: For more information about the errors and possible solutions, please
read the following articles:
Error: [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error:
Error: After correcting the problems, you can resume the build with the command
Error: mvn -rf :storm-bridge-shim{code}
> Maven Package Failure
> -
>
> Key: ATLAS-3671
> URL: https://issues.apache.org/jira/browse/ATLAS-3671
> Project: Atlas
> Issue Type: Bug
>Reporter: ygo
>Priority: Blocker
> Attachments: image-2020-03-20-12-23-10-166.png,
> image-2020-03-20-12-23-26-760.png, image-2020-03-20-12-25-19-822.png,
> image-2020-03-20-12-26-08-408.png
>
>
> mvn clean -DskipTests package -Pdist,embedded-hbase-solr
>
> i try mvn package, but failed.
> mvn version : 3.6.1
>
>
> *first*. JanusGraph DB Impl 2.0.0 build failure.
> "com.sleepycat:je:pom:7.4.5" in "http://repo1.maven.org/maven2;
> !image-2020-03-20-12-23-10-166.png|width=833,height=68!
> !image-2020-03-20-12-23-26-760.png|width=1344,height=45!
> * i modified the pom.xml file
> **
> oracleReleases
> Oracle Released Java Packages
> [http://download.oracle.com/maven]
> default
>
>
> *second.* Storm bridge shim 2.0.0 build failure.
> !image-2020-03-20-12-25-19-822.png|width=589,height=236!
> !image-2020-03-20-12-26-08-408.png|width=1217,height=40!
>
> * i modified the pom.xml file
> **
> atlassian-public
> https://maven.atlassian.com/repository/public
>
> true
> never
> warn
>
>
> true
> warn
>
>
>
> *result. build succeed*
>
> Did I do something wrong? Otherwise, please modify the source.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4729: --- Attachment: image-2023-02-14-17-05-15-213.png > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png, > image-2023-02-14-17-05-15-213.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688467#comment-17688467 ] Nixon Rodrigues commented on ATLAS-4729: !image-2023-02-14-17-05-15-213.png! > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png, > image-2023-02-14-17-05-15-213.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4729: --- Attachment: image-2023-02-14-17-04-26-576.png > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729 ] Nixon Rodrigues deleted comment on ATLAS-4729: was (Author: nixonrodrigues): !image-2023-02-14-17-04-26-576.png! > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688466#comment-17688466 ] Nixon Rodrigues commented on ATLAS-4729: !image-2023-02-14-17-04-26-576.png! > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4729: --- Attachment: image (31).png > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4729: --- Attachment: (was: image (31).png) > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
Nixon Rodrigues created ATLAS-4729: -- Summary: create entity fails if enum with name "date" or "int" is created. Key: ATLAS-4729 URL: https://issues.apache.org/jira/browse/ATLAS-4729 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Nixon Rodrigues create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4504) AtlasSchemaViolationException while EntityStateChecker checkState
Nixon Rodrigues created ATLAS-4504: -- Summary: AtlasSchemaViolationException while EntityStateChecker checkState Key: ATLAS-4504 URL: https://issues.apache.org/jira/browse/ATLAS-4504 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues org.apache.atlas.repository.graphdb.AtlasSchemaViolationException: org.janusgraph.core.SchemaViolationException: Key is defined for LIST cardinality which conflicts with specified: set at org.apache.atlas.repository.graphdb.janus.AtlasJanusVertex.addProperty(AtlasJanusVertex.java:53) at org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.addProperty(AtlasGraphUtilsV2.java:199) at org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.addEncodedProperty(AtlasGraphUtilsV2.java:187) at org.apache.atlas.repository.store.graph.v2.EntityStateChecker.checkEntityState_Classifications(EntityStateChecker.java:295) at org.apache.atlas.repository.store.graph.v2.EntityStateChecker.checkEntityState(EntityStateChecker.java:173) at org.apache.atlas.repository.store.graph.v2.EntityStateChecker.checkState(EntityStateChecker.java:108) at org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.checkState(AtlasEntityStoreV2.java:420) at org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke() -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4487) User having import and export privilege is failing with status 403
[
https://issues.apache.org/jira/browse/ATLAS-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17447196#comment-17447196
]
Nixon Rodrigues commented on ATLAS-4487:
[~sidharthkmishra]
make sense to skip authz check for internal or system type entities. let me
know your thoughts ?
{code:java}
AtlasEntityType entityType =
typeRegistry.getEntityTypeByName(entity.getTypeName());
if(!entityType.isInternalType()) {
AtlasAuthorizationUtils.verifyAccess(new AtlasEntityAccessRequest(typeRegistry,
AtlasPrivilege.ENTITY_CREATE, new AtlasEntityHeader(entity)),
"create entity: type=", entity.getTypeName());
}
{code}
> User having import and export privilege is failing with status 403
> --
>
> Key: ATLAS-4487
> URL: https://issues.apache.org/jira/browse/ATLAS-4487
> Project: Atlas
> Issue Type: Bug
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
> org.apache.atlas.AtlasServiceException: Metadata service API
> org.apache.atlas.AtlasBaseClient$API@3fb9a67f failed with status 403
> (Forbidden) Response Body
> (\{"errorCode":"ATLAS-403-00-001","errorMessage":"hive is not authorized to
> perform create entity: type=__AtlasAuditEntry"})
> at
> org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:448)
> at
> org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:366)
> at
> org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:352)
> at org.apache.atlas.AtlasBaseClient.callAPI(AtlasBaseClient.java:228)
> at
> org.apache.atlas.AtlasBaseClient.performImportData(AtlasBaseClient.java:551)
> at
> org.apache.atlas.AtlasBaseClient.importData(AtlasBaseClient.java:537)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridgeV2.runAtlasImport(HiveMetaStoreBridgeV2.java:558)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridgeV2.exportDataToZipAndRunAtlasImport(HiveMetaStoreBridgeV2.java:200)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:180)
>
>
> Exception details from Application.log:
> {code:java}
> 2021-11-19 20:43:09,128 ERROR - [etp221634215-236 -
> a445a639-7068-4f80-ad08-541e7be3dd4d:hive:POST/api/atlas/admin/import] ~
> graph rollback due to exception (GraphTransactionInterceptor:200)
> org.apache.atlas.exception.AtlasBaseException: hive is not authorized to
> perform create entity: type=__AtlasAuditEntry
> at
> org.apache.atlas.authorize.AtlasAuthorizationUtils.verifyAccess(AtlasAuthorizationUtils.java:64)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:1150)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:366)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:779)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:111)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:692)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$34d64e85.createOrUpdate()
> at
> org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(DataAccess.java:73)
> at
> org.apache.atlas.repository.audit.AtlasAuditService.save(AtlasAuditService.java:65)
> at
> org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:106)
> at
> org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:86)
> at
> org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:71)
> at
> org.apache.atlas.repository.audit.AtlasAuditService$$FastClassBySpringCGLIB$$2eddda47.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
>
[jira] [Commented] (ATLAS-4446) Atlas - Upgrade elasticsearch to 7.14.0
[ https://issues.apache.org/jira/browse/ATLAS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432446#comment-17432446 ] Nixon Rodrigues commented on ATLAS-4446: Can you think upgrading it to 7.6.0 since [ranger |https://github.com/apache/ranger/blob/master/pom.xml#L114]use elastic search 7.6.0 libs. ranger plugins use elastic client lib to send audits to ranger-audits elastic search index when ES is configured instead SOLR [https://github.com/apache/ranger/blob/master/pom.xml#L114] > Atlas - Upgrade elasticsearch to 7.14.0 > --- > > Key: ATLAS-4446 > URL: https://issues.apache.org/jira/browse/ATLAS-4446 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Currently Elastic search is at 6.8.17 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4448) NPE while create bulk entity.
Nixon Rodrigues created ATLAS-4448: -- Summary: NPE while create bulk entity. Key: ATLAS-4448 URL: https://issues.apache.org/jira/browse/ATLAS-4448 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues This is product regression caused by *ATLAS-4348* , a new feature added in Atlas 2.2 release. Getting NPE on this line, when entityTypeName is of category STRUCT. 2021-09-27 09:47:41,202 ERROR - [etp561480862-228 - e3a8175a-692c-4d0e-976b-883d7026614d:] ~ Error handling a request: 2d67e70e541c57aa (ExceptionMapperUtil:32) java.lang.NullPointerException at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.getAppendOptionForRelationship(EntityGraphMapper.java:1487) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapArrayValue(EntityGraphMapper.java:1448) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapToVertexByTypeCategory(EntityGraphMapper.java:858) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttribute(EntityGraphMapper.java:751) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttributes(EntityGraphMapper.java:660) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttributes(EntityGraphMapper.java:645) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.createVertex(EntityGraphMapper.java:1500) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapStructValue(EntityGraphMapper.java:1123) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapCollectionElementsToVertex(EntityGraphMapper.java:1559) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapArrayValue(EntityGraphMapper.java:1433) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapToVertexByTypeCategory(EntityGraphMapper.java:858) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttribute(EntityGraphMapper.java:751) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttributes(EntityGraphMapper.java:660) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttributes(EntityGraphMapper.java:645) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.createVertex(EntityGraphMapper.java:1500) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapStructValue(EntityGraphMapper.java:1123) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapToVertexByTypeCategory(EntityGraphMapper.java:772) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttribute(EntityGraphMapper.java:751) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttributes(EntityGraphMapper.java:660) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper.mapAttributesAndClassifications(EntityGraphMapper.java:309) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper$$FastClassBySpringCGLIB$$8e3f1c72.invoke() at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:688) at org.apache.atlas.repository.store.graph.v2.EntityGraphMapper$$EnhancerBySpringCGLIB$$bb340994.mapAttributesAndClassifications() at org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:1210) at org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:366) at org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke() at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:779) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750) at org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:111) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:750) at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:692) at org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$8bbea499.createOrUpdate() at org.apache.atlas.web.rest.EntityREST.createOrUpdate(EntityREST.java:761) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4437) Atlas Not able create __AtlasAuditEntry type entities when user has types permission and no entity permission when new typedef is created.
[
https://issues.apache.org/jira/browse/ATLAS-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-4437:
---
Summary: Atlas Not able create __AtlasAuditEntry type entities when user
has types permission and no entity permission when new typedef is created.
(was: Atlas Not able create __AtlasAuditEntry type entities when types user has
types permission and no entity permission when new typedef is created.)
> Atlas Not able create __AtlasAuditEntry type entities when user has types
> permission and no entity permission when new typedef is created.
> --
>
> Key: ATLAS-4437
> URL: https://issues.apache.org/jira/browse/ATLAS-4437
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Priority: Major
>
> Should Skip authz check for internal type of entities.
> {code:java}
> 2021-09-22 18:28:26,127 ERROR - [etp94748968-233 -
> 55fa25f7-d35f-4ac3-8307-1be260e12ddc:] ~ OnChange failed for listener
> org.apache.atlas.repository.audit.TypeDefAuditListener
> (AtlasTypeDefGraphStore$TypeRegistryUpdateHook:1151)2021-09-22 18:28:26,127
> ERROR - [etp94748968-233 - 55fa25f7-d35f-4ac3-8307-1be260e12ddc:] ~ OnChange
> failed for listener org.apache.atlas.repository.audit.TypeDefAuditListener
> (AtlasTypeDefGraphStore$TypeRegistryUpdateHook:1151)org.apache.atlas.exception.AtlasBaseException:
> is not authorized to perform create entity: type=__AtlasAuditEntry at
> org.apache.atlas.authorize.AtlasAuthorizationUtils.verifyAccess(AtlasAuthorizationUtils.java:64)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:1268)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:437)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:737)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:111)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$d3638c28.createOrUpdate()
> at org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(DataAccess.java:75)
> at
> org.apache.atlas.repository.audit.AtlasAuditService.save(AtlasAuditService.java:65)
> at
> org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:106)
> at
> org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:86)
> at
> org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:71)
> at
> org.apache.atlas.repository.audit.AtlasAuditService$$FastClassBySpringCGLIB$$2eddda47.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
> at
> org.apache.atlas.repository.audit.AtlasAuditService$$EnhancerBySpringCGLIB$$5bbbf7c2.add()
> at
> org.apache.atlas.repository.audit.TypeDefAuditListener.createAuditEntry(TypeDefAuditListener.java:105)
> at
> org.apache.atlas.repository.audit.TypeDefAuditListener.createAuditEntry(TypeDefAuditListener.java:70)
> at
> org.apache.atlas.repository.audit.TypeDefAuditListener.onChange(TypeDefAuditListener.java:56)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.notifyListeners(AtlasTypeDefGraphStore.java:1149)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.onComplete(AtlasTypeDefGraphStore.java:1133)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:162)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2$$EnhancerBySpringCGLIB$$576e0528.createTypesDef()
> at
> org.apache.atlas.web.rest.TypesREST.createAtlasTypeDefs(TypesREST.java:399)
> at
>
[jira] [Created] (ATLAS-4437) Atlas Not able create __AtlasAuditEntry type entities when types user has types permission and no entity permission when new typedef is created.
Nixon Rodrigues created ATLAS-4437:
--
Summary: Atlas Not able create __AtlasAuditEntry type entities
when types user has types permission and no entity permission when new typedef
is created.
Key: ATLAS-4437
URL: https://issues.apache.org/jira/browse/ATLAS-4437
Project: Atlas
Issue Type: Bug
Reporter: Nixon Rodrigues
Should Skip authz check for internal type of entities.
{code:java}
2021-09-22 18:28:26,127 ERROR - [etp94748968-233 -
55fa25f7-d35f-4ac3-8307-1be260e12ddc:] ~ OnChange failed for listener
org.apache.atlas.repository.audit.TypeDefAuditListener
(AtlasTypeDefGraphStore$TypeRegistryUpdateHook:1151)2021-09-22 18:28:26,127
ERROR - [etp94748968-233 - 55fa25f7-d35f-4ac3-8307-1be260e12ddc:] ~ OnChange
failed for listener org.apache.atlas.repository.audit.TypeDefAuditListener
(AtlasTypeDefGraphStore$TypeRegistryUpdateHook:1151)org.apache.atlas.exception.AtlasBaseException:
is not authorized to perform create entity: type=__AtlasAuditEntry at
org.apache.atlas.authorize.AtlasAuthorizationUtils.verifyAccess(AtlasAuthorizationUtils.java:64)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:1268)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:437)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:737)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:111)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$d3638c28.createOrUpdate()
at org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(DataAccess.java:75)
at
org.apache.atlas.repository.audit.AtlasAuditService.save(AtlasAuditService.java:65)
at
org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:106)
at
org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:86)
at
org.apache.atlas.repository.audit.AtlasAuditService.add(AtlasAuditService.java:71)
at
org.apache.atlas.repository.audit.AtlasAuditService$$FastClassBySpringCGLIB$$2eddda47.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:668)
at
org.apache.atlas.repository.audit.AtlasAuditService$$EnhancerBySpringCGLIB$$5bbbf7c2.add()
at
org.apache.atlas.repository.audit.TypeDefAuditListener.createAuditEntry(TypeDefAuditListener.java:105)
at
org.apache.atlas.repository.audit.TypeDefAuditListener.createAuditEntry(TypeDefAuditListener.java:70)
at
org.apache.atlas.repository.audit.TypeDefAuditListener.onChange(TypeDefAuditListener.java:56)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.notifyListeners(AtlasTypeDefGraphStore.java:1149)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.onComplete(AtlasTypeDefGraphStore.java:1133)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:162)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:672)
at
org.apache.atlas.repository.store.graph.v2.AtlasTypeDefGraphStoreV2$$EnhancerBySpringCGLIB$$576e0528.createTypesDef()
at org.apache.atlas.web.rest.TypesREST.createAtlasTypeDefs(TypesREST.java:399)
at
org.apache.atlas.web.rest.TypesREST$$FastClassBySpringCGLIB$$1c2e37c6.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:737)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:84)
at
org.apache.atlas.web.service.TimedAspectInterceptor.timerAdvice(TimedAspectInterceptor.java:46)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4233) [Atlas: Audits] When a term is added or removed, v1 api displays action as null instead of TERM_ADD or TERM_DELETE
[
https://issues.apache.org/jira/browse/ATLAS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues resolved ATLAS-4233.
Fix Version/s: 3.0.0
Resolution: Fixed
> [Atlas: Audits] When a term is added or removed, v1 api displays action as
> null instead of TERM_ADD or TERM_DELETE
> --
>
> Key: ATLAS-4233
> URL: https://issues.apache.org/jira/browse/ATLAS-4233
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screenshot 2021-04-01 at 7.58.12 PM.png, Screenshot
> 2021-04-01 at 8.04.11 PM.png
>
>
> *Scenario:*
> * Add a term to an entity.
> * Remove the term from the entity
> Audits will be generated. Here the action should appear as *TERM_ADD or
> TERM_DELETE*
> But the value is null instead. Please check the reference below
> {code:java}
> {
> "entityId": "d83d7d10-c137-4a16-8018-70692cd555b2",
> "timestamp": 1617286735612,
> "user": "hrt_qa",
> "action": null,
> "details": "Added term:
> {\"guid\":\"700bafef-ac2b-489b-a54b-0dc5741e2a6f\",\"qualifiedName\":\"hdcpg_term@hdcpg_glossary\",\"name\":\"hdcpg_term\"}",
> "eventKey":
> "d83d7d10-c137-4a16-8018-70692cd555b2:1617286735612:0:1617286735676"
> } {code}
> *v1: https://:31443/api/atlas/entities//audit*
> *TERM_ADD*
> !Screenshot 2021-04-01 at 7.58.12 PM.png|width=584,height=179!
> *TERM_DELETE*
> !Screenshot 2021-04-01 at 8.04.11 PM.png|width=581,height=174!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-894) Load multiple instances in one GET call
[ https://issues.apache.org/jira/browse/ATLAS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-894. --- Resolution: Fixed > Load multiple instances in one GET call > --- > > Key: ATLAS-894 > URL: https://issues.apache.org/jira/browse/ATLAS-894 > Project: Atlas > Issue Type: Improvement >Reporter: Prasad S Madugundu >Assignee: Dave Kantor >Priority: Major > > At present, the entities GET method can take one GUID and returns one > instance. It would be better from the performance to accept multiple GUIDs in > the GET call, similar to DELETE method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-894) Load multiple instances in one GET call
[
https://issues.apache.org/jira/browse/ATLAS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17403787#comment-17403787
]
Nixon Rodrigues commented on ATLAS-894:
---
Atlas bulk entities API is available, closing the jira
* {{/v2/entity/bulk}}
> Load multiple instances in one GET call
> ---
>
> Key: ATLAS-894
> URL: https://issues.apache.org/jira/browse/ATLAS-894
> Project: Atlas
> Issue Type: Improvement
>Reporter: Prasad S Madugundu
>Assignee: Dave Kantor
>Priority: Major
>
> At present, the entities GET method can take one GUID and returns one
> instance. It would be better from the performance to accept multiple GUIDs in
> the GET call, similar to DELETE method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4379) Atlas Filter changes for user inactivity on Atlas UI
[ https://issues.apache.org/jira/browse/ATLAS-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reassigned ATLAS-4379: -- Assignee: Nixon Rodrigues > Atlas Filter changes for user inactivity on Atlas UI > > > Key: ATLAS-4379 > URL: https://issues.apache.org/jira/browse/ATLAS-4379 > Project: Atlas > Issue Type: Sub-task >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4378) UI - Implement session timeout on Atlas UI
[ https://issues.apache.org/jira/browse/ATLAS-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reassigned ATLAS-4378: -- Assignee: Prasad P. Pawar (was: Nixon Rodrigues) > UI - Implement session timeout on Atlas UI > -- > > Key: ATLAS-4378 > URL: https://issues.apache.org/jira/browse/ATLAS-4378 > Project: Atlas > Issue Type: New Feature >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4378-1-UI-Implement-session-timeout-on-Atlas-U.patch > > > If Atlas UI is inactive for N minutes, alert the user about the inactivity, > ask user if he wants to stay on page or logout the user session UI for after > X seconds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3958) When updating a type with non-existing super type as an un-authorized user gives in-correct message in response
[
https://issues.apache.org/jira/browse/ATLAS-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues resolved ATLAS-3958.
Resolution: Duplicate
> 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
>Assignee: Nixon Rodrigues
>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] [Resolved] (ATLAS-4388) Atlas UI : Fix count on Propagated classification on lineage page.
[ https://issues.apache.org/jira/browse/ATLAS-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-4388. Resolution: Duplicate > Atlas UI : Fix count on Propagated classification on lineage page. > -- > > Key: ATLAS-4388 > URL: https://issues.apache.org/jira/browse/ATLAS-4388 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Major > > There is issue wrt to count on propagated classification on lineage page UI > which needs to be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4388) Atlas UI : Fix count on Propagated classification on lineage page.
Nixon Rodrigues created ATLAS-4388: -- Summary: Atlas UI : Fix count on Propagated classification on lineage page. Key: ATLAS-4388 URL: https://issues.apache.org/jira/browse/ATLAS-4388 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues There is issue wrt to count on propagated classification on lineage page UI which needs to be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4379) Atlas Filter changes for user inactivity on Atlas UI
Nixon Rodrigues created ATLAS-4379: -- Summary: Atlas Filter changes for user inactivity on Atlas UI Key: ATLAS-4379 URL: https://issues.apache.org/jira/browse/ATLAS-4379 Project: Atlas Issue Type: Sub-task Reporter: Nixon Rodrigues -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4378) UI - Implement session timeout on Atlas UI
Nixon Rodrigues created ATLAS-4378: -- Summary: UI - Implement session timeout on Atlas UI Key: ATLAS-4378 URL: https://issues.apache.org/jira/browse/ATLAS-4378 Project: Atlas Issue Type: New Feature Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues If Atlas UI is inactive for N minutes, alert the user about the inactivity, ask user if he wants to stay on page or logout the user session UI for after X seconds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4363) Integration tests for Apache Atlas Client in Python
Nixon Rodrigues created ATLAS-4363: -- Summary: Integration tests for Apache Atlas Client in Python Key: ATLAS-4363 URL: https://issues.apache.org/jira/browse/ATLAS-4363 Project: Atlas Issue Type: Improvement Reporter: Nixon Rodrigues Add test coverage for Apache Atlas Client in Python. This tests can be integrated in build process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4357) it can't get group with ldap
[
https://issues.apache.org/jira/browse/ATLAS-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381214#comment-17381214
]
Nixon Rodrigues commented on ATLAS-4357:
[~ighack], from exception trace it looks like call is made to lookup for hadoop
groups but looks like LDAP/AD is not configured correctly in hadoop
core-site.xml.
Can you check if configuration are correct
https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.0/installing-ranger/content/set_up_hadoop_group_mapping_for_ldap_ad.html
> it can't get group with ldap
>
>
> Key: ATLAS-4357
> URL: https://issues.apache.org/jira/browse/ATLAS-4357
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: ighack
>Priority: Major
>
> atlas.authentication.method.ldap.url=ldap://hoostdd:389
> atlas.authentication.method.ldap.userDNpattern=uid=\{0},ou=people,dc=join,dc=com
> atlas.authentication.method.ldap.groupSearchBase=ou=group,dc=join,dc=com
> atlas.authentication.method.ldap.groupSearchFilter=(memberUid=uid=\{0},ou=peopel,dc=join,dc=com)
> atlas.authentication.method.ldap.groupRoleAttribute=cn
> atlas.authentication.method.ldap.base.dn=dc=join,dc=com
> atlas.authentication.method.ldap.bind.dn=uid=ldapadmin,ou=people,dc=join,dc=com
> atlas.authentication.method.ldap.bind.password= 00
> atlas.authentication.method.ldap.referral=ignore
> atlas.authentication.method.ldap.user.searchfilter=(uid=\{0})
> atlas.authentication.method.ldap.default.role=ROLE_USER
>
> but I get error
> 2021-07-13 13:02:45,523 WARN - [pool-2-thread-4:] ~ Failed to get groups for
> user jztwk (retry=0) by javax.naming.OperationNotSupportedException: [LDAP:
> error code 53 - unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,523 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=0) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,524 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=1) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,526 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=2) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,533 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=0) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,535 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=1) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,536 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=2) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,538 ERROR - [pool-2-thread-4:] ~
> Exception while fetching groups
> (AtlasAbstractAuthenticationProvider:137)java.io.IOException: No groups found
> for user jztwk at
> org.apache.hadoop.security.Groups.noGroupsForUser(Groups.java:200) at
> org.apache.hadoop.security.Groups.access$400(Groups.java:75) at
> org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:334) at
> org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:270) at
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3527)
> at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2276)
> at
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2154)
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2044) at
> com.google.common.cache.LocalCache.get(LocalCache.java:3951) at
> com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3973) at
> com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4957)
> at org.apache.hadoop.security.Groups.getGroups(Groups.java:228) at
> org.apache.atlas.web.security.AtlasAbstractAuthenticationProvider.getAuthoritiesFromUGI(AtlasAbstractAuthenticationProvider.java:125)
> at
> org.apache.atlas.web.security.AtlasAbstractAuthenticationProvider.getAuthenticationWithGrantedAuthorityFromUGI(AtlasAbstractAuthenticationProvider.java:89)
> at
>
[jira] [Commented] (ATLAS-4357) it can't get group with ldap
[
https://issues.apache.org/jira/browse/ATLAS-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17380377#comment-17380377
]
Nixon Rodrigues commented on ATLAS-4357:
[~ighack],
It is observed that spring ldap API is not returning groups for the user after
authentication. making a follow up call after authentication to fetch groups in
time consuming.
Sync up the ldap user group in to linux user group or hadoop UGI so that
groups can be fetched after authentication.
{quote}org.apache.hadoop.security.Groups.getGroups(Groups.java:228) at
org.apache.atlas.web.security.AtlasAbstractAuthenticationProvider.getAuthoritiesFromUGI(AtlasAbstractAuthenticationProvider.java:125
{quote}
> it can't get group with ldap
>
>
> Key: ATLAS-4357
> URL: https://issues.apache.org/jira/browse/ATLAS-4357
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: ighack
>Priority: Major
>
> atlas.authentication.method.ldap.url=ldap://hoostdd:389
> atlas.authentication.method.ldap.userDNpattern=uid=\{0},ou=people,dc=join,dc=com
> atlas.authentication.method.ldap.groupSearchBase=ou=group,dc=join,dc=com
> atlas.authentication.method.ldap.groupSearchFilter=(memberUid=uid=\{0},ou=peopel,dc=join,dc=com)
> atlas.authentication.method.ldap.groupRoleAttribute=cn
> atlas.authentication.method.ldap.base.dn=dc=join,dc=com
> atlas.authentication.method.ldap.bind.dn=uid=ldapadmin,ou=people,dc=join,dc=com
> atlas.authentication.method.ldap.bind.password= 00
> atlas.authentication.method.ldap.referral=ignore
> atlas.authentication.method.ldap.user.searchfilter=(uid=\{0})
> atlas.authentication.method.ldap.default.role=ROLE_USER
>
> but I get error
> 2021-07-13 13:02:45,523 WARN - [pool-2-thread-4:] ~ Failed to get groups for
> user jztwk (retry=0) by javax.naming.OperationNotSupportedException: [LDAP:
> error code 53 - unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,523 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=0) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,524 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=1) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,526 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=2) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,533 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=0) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,535 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=1) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,536 WARN - [pool-2-thread-4:] ~
> Failed to get groups for user jztwk (retry=2) by
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> unauthenticated bind (DN with no password) disallowed]
> (LdapGroupsMapping:290)2021-07-13 13:02:45,538 ERROR - [pool-2-thread-4:] ~
> Exception while fetching groups
> (AtlasAbstractAuthenticationProvider:137)java.io.IOException: No groups found
> for user jztwk at
> org.apache.hadoop.security.Groups.noGroupsForUser(Groups.java:200) at
> org.apache.hadoop.security.Groups.access$400(Groups.java:75) at
> org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:334) at
> org.apache.hadoop.security.Groups$GroupCacheLoader.load(Groups.java:270) at
> com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3527)
> at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2276)
> at
> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2154)
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2044) at
> com.google.common.cache.LocalCache.get(LocalCache.java:3951) at
> com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3973) at
> com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4957)
> at org.apache.hadoop.security.Groups.getGroups(Groups.java:228) at
> org.apache.atlas.web.security.AtlasAbstractAuthenticationProvider.getAuthoritiesFromUGI(AtlasAbstractAuthenticationProvider.java:125)
> at
>
[jira] [Created] (ATLAS-4353) Atlas typedef name issue with name="name"
Nixon Rodrigues created ATLAS-4353: -- Summary: Atlas typedef name issue with name="name" Key: ATLAS-4353 URL: https://issues.apache.org/jira/browse/ATLAS-4353 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues In Atlas, when we create a new classification with name of "name", then the result is it will create a classification named "[]" after that if we tried to remove it then it will failed and even we tried with API to remove the "[]" classification, it will responding with invalid name error -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-1167) Cannot create term with deleted term name
[ https://issues.apache.org/jira/browse/ATLAS-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1167. Resolution: Not A Bug > Cannot create term with deleted term name > - > > Key: ATLAS-1167 > URL: https://issues.apache.org/jira/browse/ATLAS-1167 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Major > > If a Term is created (TermTest) and it is been deleted and the user again > wants to create term with same name(TermTest) term then he is not able to > create. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4158) Atlas authorization for Add/Update/Remove classification on entities.
[ https://issues.apache.org/jira/browse/ATLAS-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-4158. Fix Version/s: 2.2.0 3.0.0 Resolution: Fixed > Atlas authorization for Add/Update/Remove classification on entities. > - > > Key: ATLAS-4158 > URL: https://issues.apache.org/jira/browse/ATLAS-4158 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > *Requirement* > The new requirement is to provide a way to authorize who can > Add/Remove/Update Classification for an entity even if the entities on which > classification have to be applied do not have classifications already tagged > to it. > > e.g. Any users belonging to user group - 'finance_group' can add > classification - FINANCE_PII to any entities (these entities may not have > any classifications associated) if policy has given access to the user or > user-group. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (ATLAS-4346) Informasi pengeluaran nomor toto4D
[ https://issues.apache.org/jira/browse/ATLAS-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues closed ATLAS-4346. -- > Informasi pengeluaran nomor toto4D > -- > > Key: ATLAS-4346 > URL: https://issues.apache.org/jira/browse/ATLAS-4346 > Project: Atlas > Issue Type: New Feature >Reporter: Hongkong Prize >Priority: Trivial > > Informasi pengeluaran nomor togel [Hongkong Prize|http://149.28.170.209/] > tercepat dan terpercaya -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4346) Informasi pengeluaran nomor toto4D
[ https://issues.apache.org/jira/browse/ATLAS-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-4346. Resolution: Invalid > Informasi pengeluaran nomor toto4D > -- > > Key: ATLAS-4346 > URL: https://issues.apache.org/jira/browse/ATLAS-4346 > Project: Atlas > Issue Type: New Feature >Reporter: Hongkong Prize >Priority: Trivial > > Informasi pengeluaran nomor togel [Hongkong Prize|http://149.28.170.209/] > tercepat dan terpercaya -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4271) When unauthorised user is tries to create a relationship, message thrown is incorrect
[
https://issues.apache.org/jira/browse/ATLAS-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues resolved ATLAS-4271.
Fix Version/s: 2.2.0
3.0.0
Resolution: Fixed
> When unauthorised user is tries to create a relationship, message thrown is
> incorrect
> -
>
> Key: ATLAS-4271
> URL: https://issues.apache.org/jira/browse/ATLAS-4271
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Jayendra Parab
>Assignee: Jayendra Parab
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> When an unauthorized user (say user1) tries to create a relationship between
> two entities (say type1 and type2), the error message thrown is
> {code:java}
> user1 is not authorized to perform create relationship-def{code}
> The expected message should be
> {code:java}
> user1 is not authorized to perform read type-def of category ENTITY
> type1{code}
> The current message should be thrown when an user with read-only access tries
> to create a relationship.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4286) UI: User is taken to incorrect page as you go one page back after reaching page limit.
[ https://issues.apache.org/jira/browse/ATLAS-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370412#comment-17370412 ] Nixon Rodrigues commented on ATLAS-4286: +1 for the patch, [~prasadpp13] Thanks! for the patch. > UI: User is taken to incorrect page as you go one page back after reaching > page limit. > -- > > Key: ATLAS-4286 > URL: https://issues.apache.org/jira/browse/ATLAS-4286 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4286-UI-1-User-is-taken-to-incorrect-page-as-y.patch > > > Video link: > https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing > Steps: > 1. Make sure there are exactly 25 entries and the default page limit is 5 > items displayed on a single page. > 2. Go to the last page and you will see that the 'next' page button will be > enabled > 3. Click the 'next' page button and you will see a blank page along with > notification that no record exists. This is expected. But the page no is > still showing as page no 5. > 4. Try to click the previous page > You will be taken to page 4 whereas the expectation is that user will be > taken to page 5. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4008) Cache getGuid and getStatus in GraphTransactionInterceptor
[ https://issues.apache.org/jira/browse/ATLAS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4008: --- Attachment: branch-0.8-ATLAS-4008-Cache-getGuid-and-getStatus-in-GraphTrans.patch > Cache getGuid and getStatus in GraphTransactionInterceptor > -- > > Key: ATLAS-4008 > URL: https://issues.apache.org/jira/browse/ATLAS-4008 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > ATLAS-4008-Cache-getGuid-and-getStatus-in-GraphTrans-v1.patch, > branch-0.8-ATLAS-4008-Cache-getGuid-and-getStatus-in-GraphTrans.patch > > > *Problem Statement:* > GraphHelper.getGuid() & GraphHelper.getStatus() causes overhead when called > multiple times in a same request. > > *Approach:* > Implement a caching mechanism in GraphTransactionInterceptor to cache the > following mappings: > *vertexID -> guid* > *vertexID -> entityStatus* > *edgeId -> status* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4317) Upgrade curator jar version to 4.3.0
[ https://issues.apache.org/jira/browse/ATLAS-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367153#comment-17367153 ] Nixon Rodrigues commented on ATLAS-4317: +1 for the patch > Upgrade curator jar version to 4.3.0 > > > Key: ATLAS-4317 > URL: https://issues.apache.org/jira/browse/ATLAS-4317 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Upgrade curator jar version to 4.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3923) Exception in audit page
[ https://issues.apache.org/jira/browse/ATLAS-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-3923. Fix Version/s: (was: trunk) Resolution: Fixed > Exception in audit page > --- > > Key: ATLAS-3923 > URL: https://issues.apache.org/jira/browse/ATLAS-3923 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Zhangyy >Priority: Minor > Labels: pull-request-available > Fix For: 3.0.0, 2.2.0 > > Attachments: bug.png, bug2.png > > Time Spent: 20m > Remaining Estimate: 0h > > 1. In debug mode, the audit page reports a NullPointException。 > 2. The bug exists in > org.apache.atlas.repository.audit.HBaseBasedAuditRepository, line 231 > 3. debug: auditAction.toString --> auditAction -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4337) Atlas UI:Add entity icons for all the Kafka types
[ https://issues.apache.org/jira/browse/ATLAS-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364099#comment-17364099 ] Nixon Rodrigues commented on ATLAS-4337: +1 for the kafka types icons , thanks [~prasadpp13] for the patch > Atlas UI:Add entity icons for all the Kafka types > - > > Key: ATLAS-4337 > URL: https://issues.apache.org/jira/browse/ATLAS-4337 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Labels: entity-icons > Attachments: > 0001-ATLAS-4337-1-Atlas-UI-Add-entity-icons-for-all-the-K.patch > > > Create Entity icons for all the Kafka types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4058) UI - On entity details page, for Hive column 'position' is getting set as 0(zero)
[ https://issues.apache.org/jira/browse/ATLAS-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360934#comment-17360934 ] Nixon Rodrigues commented on ATLAS-4058: Need to revert the commit , since showing showing 0 instead NA is proper by design. > UI - On entity details page, for Hive column 'position' is getting set as > 0(zero) > - > > Key: ATLAS-4058 > URL: https://issues.apache.org/jira/browse/ATLAS-4058 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4058-UI-Entity-detail-page-Hive-Column-Positio.patch, > Atlas-4058.png, Atlas-4058_1.png, > screenshot-issues.apache.org-2020.12.03-10_47_09.png > > > Hive Column position should get set to N/A OR blank instead of 0. > PFA image -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4321) Ignore files generated under webapp/overlays
[
https://issues.apache.org/jira/browse/ATLAS-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues resolved ATLAS-4321.
Fix Version/s: 2.2.0
3.0.0
Resolution: Fixed
> Ignore files generated under webapp/overlays
>
>
> Key: ATLAS-4321
> URL: https://issues.apache.org/jira/browse/ATLAS-4321
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Nixon Rodrigues
>Priority: Trivial
> Fix For: 3.0.0, 2.2.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Merge PR [https://github.com/apache/atlas/pull/132]
>
> By modifying the {{.gitignore}} configuration file, we can ignore the files
> generated under {{webapp/overlays}} and avoid submitting temporary files by
> mistake.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4320) Fixing location uri for DB entities in QuickStartV2
[ https://issues.apache.org/jira/browse/ATLAS-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-4320. Fix Version/s: 2.2.0 3.0.0 Resolution: Fixed > Fixing location uri for DB entities in QuickStartV2 > --- > > Key: ATLAS-4320 > URL: https://issues.apache.org/jira/browse/ATLAS-4320 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Fixing location uri for DB entities in QuickStartV2 > Fix is provided in PR. > https://github.com/apache/atlas/pull/131 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4319) Code refactoring in kafka bridge
[ https://issues.apache.org/jira/browse/ATLAS-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-4319. Fix Version/s: 2.2.0 3.0.0 Resolution: Fixed > Code refactoring in kafka bridge > - > > Key: ATLAS-4319 > URL: https://issues.apache.org/jira/browse/ATLAS-4319 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Trivial > Fix For: 3.0.0, 2.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > merge > [https://github.com/apache/atlas/pull/136] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4319) Code refactoring in kafka bridge
[ https://issues.apache.org/jira/browse/ATLAS-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4319: --- Description: merge [https://github.com/apache/atlas/pull/136] was:https://github.com/apache/atlas/pull/136 > Code refactoring in kafka bridge > - > > Key: ATLAS-4319 > URL: https://issues.apache.org/jira/browse/ATLAS-4319 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Trivial > Time Spent: 10m > Remaining Estimate: 0h > > merge > [https://github.com/apache/atlas/pull/136] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4318) Fix python client issues and code refactoring
[ https://issues.apache.org/jira/browse/ATLAS-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4318: --- Description: Merge PR reported on github. [https://github.com/apache/atlas/pull/130] [https://github.com/apache/atlas/pull/135] https://github.com/apache/atlas/pull/134 was: Merge PR reported on github. [https://github.com/apache/atlas/pull/130] https://github.com/apache/atlas/pull/135 > Fix python client issues and code refactoring > - > > Key: ATLAS-4318 > URL: https://issues.apache.org/jira/browse/ATLAS-4318 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Merge PR reported on github. > [https://github.com/apache/atlas/pull/130] > [https://github.com/apache/atlas/pull/135] > https://github.com/apache/atlas/pull/134 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4318) Fix python client issues and code refactoring
[ https://issues.apache.org/jira/browse/ATLAS-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-4318. Fix Version/s: 2.2.0 3.0.0 Resolution: Fixed > Fix python client issues and code refactoring > - > > Key: ATLAS-4318 > URL: https://issues.apache.org/jira/browse/ATLAS-4318 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Merge PR reported on github. > [https://github.com/apache/atlas/pull/130] > [https://github.com/apache/atlas/pull/135] > https://github.com/apache/atlas/pull/134 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4321) Ignore files generated under webapp/overlays
[
https://issues.apache.org/jira/browse/ATLAS-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-4321:
---
Description:
Merge PR [https://github.com/apache/atlas/pull/132]
By modifying the {{.gitignore}} configuration file, we can ignore the files
generated under {{webapp/overlays}} and avoid submitting temporary files by
mistake.
was:Merge PR https://github.com/apache/atlas/pull/132
> Ignore files generated under webapp/overlays
>
>
> Key: ATLAS-4321
> URL: https://issues.apache.org/jira/browse/ATLAS-4321
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Nixon Rodrigues
>Priority: Trivial
>
> Merge PR [https://github.com/apache/atlas/pull/132]
>
> By modifying the {{.gitignore}} configuration file, we can ignore the files
> generated under {{webapp/overlays}} and avoid submitting temporary files by
> mistake.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4321) Ignore files generated under webapp/overlays
Nixon Rodrigues created ATLAS-4321: -- Summary: Ignore files generated under webapp/overlays Key: ATLAS-4321 URL: https://issues.apache.org/jira/browse/ATLAS-4321 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Nixon Rodrigues Merge PR https://github.com/apache/atlas/pull/132 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4320) Fixing location uri for DB entities in QuickStartV2
Nixon Rodrigues created ATLAS-4320: -- Summary: Fixing location uri for DB entities in QuickStartV2 Key: ATLAS-4320 URL: https://issues.apache.org/jira/browse/ATLAS-4320 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues Fixing location uri for DB entities in QuickStartV2 Fix is provided in PR. https://github.com/apache/atlas/pull/131 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4319) Code refactoring in kafka bridge
Nixon Rodrigues created ATLAS-4319: -- Summary: Code refactoring in kafka bridge Key: ATLAS-4319 URL: https://issues.apache.org/jira/browse/ATLAS-4319 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues https://github.com/apache/atlas/pull/136 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4318) Fix python client issues and code refactoring
[ https://issues.apache.org/jira/browse/ATLAS-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4318: --- Description: Merge PR reported on github. [https://github.com/apache/atlas/pull/130] https://github.com/apache/atlas/pull/135 was: Merge PR reported on github. [https://github.com/apache/atlas/pull/130] > Fix python client issues and code refactoring > - > > Key: ATLAS-4318 > URL: https://issues.apache.org/jira/browse/ATLAS-4318 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Merge PR reported on github. > [https://github.com/apache/atlas/pull/130] > https://github.com/apache/atlas/pull/135 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4318) Fix python client issues and code refactoring
[ https://issues.apache.org/jira/browse/ATLAS-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4318: --- Description: Merge PR reported on github. [https://github.com/apache/atlas/pull/130] was:https://github.com/apache/atlas/pull/130 > Fix python client issues and code refactoring > - > > Key: ATLAS-4318 > URL: https://issues.apache.org/jira/browse/ATLAS-4318 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Major > > Merge PR reported on github. > [https://github.com/apache/atlas/pull/130] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4318) Fix python client issues and code refactoring
Nixon Rodrigues created ATLAS-4318: -- Summary: Fix python client issues and code refactoring Key: ATLAS-4318 URL: https://issues.apache.org/jira/browse/ATLAS-4318 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues https://github.com/apache/atlas/pull/130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4317) Upgrade curator jar version to 4.3.0
[ https://issues.apache.org/jira/browse/ATLAS-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4317: --- Summary: Upgrade curator jar version to 4.3.0 (was: Atlas should use downstream Curator) > Upgrade curator jar version to 4.3.0 > > > Key: ATLAS-4317 > URL: https://issues.apache.org/jira/browse/ATLAS-4317 > Project: Atlas > Issue Type: Improvement >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > > Upgrade curator jar version to 4.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4294) Format long description of Glossary term and category UI
[ https://issues.apache.org/jira/browse/ATLAS-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4294: --- Summary: Format long description of Glossary term and category UI (was: Format long description of Glossary term and category) > Format long description of Glossary term and category UI > > > Key: ATLAS-4294 > URL: https://issues.apache.org/jira/browse/ATLAS-4294 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > > Currently the long description is render as long string and it all appears > as a single text string > It is hard to read multiple lines. > Makes to support newline character in rendering long description > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4294) Atlas UI : Format long description of Glossary term and category UI
[ https://issues.apache.org/jira/browse/ATLAS-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4294: --- Summary: Atlas UI : Format long description of Glossary term and category UI (was: Format long description of Glossary term and category UI) > Atlas UI : Format long description of Glossary term and category UI > --- > > Key: ATLAS-4294 > URL: https://issues.apache.org/jira/browse/ATLAS-4294 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > > Currently the long description is render as long string and it all appears > as a single text string > It is hard to read multiple lines. > Makes to support newline character in rendering long description > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4294) Format long description of Glossary term and category
Nixon Rodrigues created ATLAS-4294: -- Summary: Format long description of Glossary term and category Key: ATLAS-4294 URL: https://issues.apache.org/jira/browse/ATLAS-4294 Project: Atlas Issue Type: Improvement Reporter: Nixon Rodrigues Currently the long description is render as long string and it all appears as a single text string It is hard to read multiple lines. Makes to support newline character in rendering long description -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4250) Support HA for admin/task API
[ https://issues.apache.org/jira/browse/ATLAS-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4250: --- Attachment: ATLAS-4250.patch > Support HA for admin/task API > - > > Key: ATLAS-4250 > URL: https://issues.apache.org/jira/browse/ATLAS-4250 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Nixon Rodrigues >Priority: Major > Attachments: ATLAS-4250.patch > > > Support HA for newly added *admin/task* API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4250) Support HA for admin/task API
[ https://issues.apache.org/jira/browse/ATLAS-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reassigned ATLAS-4250: -- Assignee: Nixon Rodrigues > Support HA for admin/task API > - > > Key: ATLAS-4250 > URL: https://issues.apache.org/jira/browse/ATLAS-4250 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Attachments: ATLAS-4250.patch > > > Support HA for newly added *admin/task* API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4250) Support HA for admin/task API
Nixon Rodrigues created ATLAS-4250: -- Summary: Support HA for admin/task API Key: ATLAS-4250 URL: https://issues.apache.org/jira/browse/ATLAS-4250 Project: Atlas Issue Type: Improvement Components: atlas-webui Reporter: Nixon Rodrigues Support HA for newly added *admin/task* API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4186) Black icons on lineage tab in case of type has spaces
[ https://issues.apache.org/jira/browse/ATLAS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-4186. Fix Version/s: 2.2.0 3.0.0 Resolution: Fixed > Black icons on lineage tab in case of type has spaces > -- > > Key: ATLAS-4186 > URL: https://issues.apache.org/jira/browse/ATLAS-4186 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Roman Hres >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: DataSetEntities.json, ProcessEntity.json, Test Entity > Defs.json, black_icons.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently there is an UI issue which can be found on Apache Atlas lineage UI > in case when entity type definition has space in the name. As it is possible > to create such a type definition I assume that it is a valid use case. > Steps to reproduce: > # Create following type defs (example of test definitions: [^Test Entity > Defs.json]): > ## a new type with space in name. DataSet is used as superType > ## a new type with space in name. DataSet is used as superType > ## a new type with space in name. Process is used as superType > # Create several entities for created types (example: > [^DataSetEntities.json]) > # Create process entity which use one of the created entities as input and > the other one as output (example: [^ProcessEntity.json]) > Actual result: > There are black icons instead inside lineage graph > !black_icons.png|width=784,height=371! > Expected result: > There are normal apache atlas icons > > *Additional note:* > During investigation, I found out that this issue related to encoding of the > fill attribute in the html. Adding encodeURI before setting fill attribute > helped with this issue. > Details of the fix can be found here: https://github.com/apache/atlas/pull/124 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4224) UI : Redirect Atlas UI to login/index page when session is expired in backend.
[ https://issues.apache.org/jira/browse/ATLAS-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311147#comment-17311147 ] Nixon Rodrigues commented on ATLAS-4224: +1 for the patch, Thanks [~prasadpp13] for the patch > UI : Redirect Atlas UI to login/index page when session is expired in backend. > -- > > Key: ATLAS-4224 > URL: https://issues.apache.org/jira/browse/ATLAS-4224 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4224-UI-Redirect-Atlas-UI-to-login-index-page-.patch > > > Redirect Atlas UI to login/index page when session is expired in backend when > cookie is expired or deleted instead of showing notification in Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4224) UI : Redirect Atlas UI to login/index page when session is expired in backend.
Nixon Rodrigues created ATLAS-4224: -- Summary: UI : Redirect Atlas UI to login/index page when session is expired in backend. Key: ATLAS-4224 URL: https://issues.apache.org/jira/browse/ATLAS-4224 Project: Atlas Issue Type: Improvement Reporter: Nixon Rodrigues Assignee: Prasad P. Pawar Redirect Atlas UI to login/index page when session is expired in backend when cookie is expired or deleted instead of showing notification in Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4213) Atlas UI is taking lot of time to load.
[ https://issues.apache.org/jira/browse/ATLAS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304639#comment-17304639 ] Nixon Rodrigues commented on ATLAS-4213: +1 for the patch, [~prasadpp13] thanks > Atlas UI is taking lot of time to load. > --- > > Key: ATLAS-4213 > URL: https://issues.apache.org/jira/browse/ATLAS-4213 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4213-Atlas-UI-is-taking-lot-of-time-to-load.fi.patch, > 0001-ATLAS-4213-V1-UIAtlas-UI-is-taking-lot-of-time-to-lo.patch > > > Description- > Atlas UI is taking a lot of time to load, after metadata creation part of > scale testing, a large number of classifications & entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4209) Add better logging in AtlasPAMAuthentication
Nixon Rodrigues created ATLAS-4209: -- Summary: Add better logging in AtlasPAMAuthentication Key: ATLAS-4209 URL: https://issues.apache.org/jira/browse/ATLAS-4209 Project: Atlas Issue Type: Improvement Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues Improve error logging of errors and exception while PAM authentication. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.
[ https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288917#comment-17288917 ] Nixon Rodrigues commented on ATLAS-3376: +1 for the patch. Thanks [~prasadpp13] for the patch. > UI: When no Catalogs are present, user should be presented with an > appropriate message when trying to associate Category to Term. > - > > Key: ATLAS-3376 > URL: https://issues.apache.org/jira/browse/ATLAS-3376 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-3376-UI-V1-When-no-Catalogs-are-present-user-s.patch, > 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, > ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 > 22-25-05.png, screenshot-newtab-2021.02.22-22_31_06.png > > > If a user tries to associate a Category to a Term, and if not a single > Category has been created for any of the Glossaries, the user is presented > with the Category association screen but with no Categories for the user to > assign to the term. > This could create a confusion that there might be a Catalog present somewhere > but is not visible to the user, when actually no Catalogs exist. A > notification should be fired in this scenario, informing the user that no > Catalog exists that can be assigned to the term. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3186) UI: Background navigation is possible when "Advanced Search Queries" popup is active.
[ https://issues.apache.org/jira/browse/ATLAS-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288916#comment-17288916 ] Nixon Rodrigues commented on ATLAS-3186: +1 for the patch. Thanks [~prasadpp13] for the patch. > UI: Background navigation is possible when "Advanced Search Queries" popup is > active. > - > > Key: ATLAS-3186 > URL: https://issues.apache.org/jira/browse/ATLAS-3186 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-3186-UI-Background-navigation-is-possible-when.patch > > > Steps: > # From Atlas UI, navigate as follows: Search–>Classification–>Change button > from Flat to Tree->Glossary–>Search > # Click on "?" icon in Search. > # Click the back button of your browser > You will see that as you go on pressing the back button, navigation will > occur in the background in the reverse order of menus mentioned in step 1 > (and the button selection will be reversed from Tree to Flat). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4167) Large no. of calls are getting generated while rendering search results
[ https://issues.apache.org/jira/browse/ATLAS-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288915#comment-17288915 ] Nixon Rodrigues commented on ATLAS-4167: +1 for the patch. Thanks [~prasadpp13] for the patch. > Large no. of calls are getting generated while rendering search results > --- > > Key: ATLAS-4167 > URL: https://issues.apache.org/jira/browse/ATLAS-4167 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4167-UI-Large-no.-of-calls-are-getting-generat.patch, > ATLAS-4167Bug.png, ATLAS-4167fix.png > > > While rendering search-results, there are large number of calls to Atlas > server to retrieve entity-icon. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-4162) invalid value: unknown relationship type
[
https://issues.apache.org/jira/browse/ATLAS-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285854#comment-17285854
]
Nixon Rodrigues edited comment on ATLAS-4162 at 2/17/21, 2:52 PM:
--
[~kirill]
Please set relationshipType and end1 and end2 type name correctly as specified
in relationshipDef.
Here is an example of REST API call to create relationship between 2 entities:
POST api/atlas/v2/relationship
{noformat}
{
"typeName": "",
"end1": {
"guid": ""
},
"end2": {
"guid": ""
}
}
{noformat}
All other fields are optional.
was (Author: nixonrodrigues):
[~kirill]
Here is an example of REST API call to create relationship between 2 entities:
POST api/atlas/v2/relationship
{noformat}
{
"typeName": "",
"end1": {
"guid": ""
},
"end2": {
"guid": ""
}
}
{noformat}
All other fields are optional.
> invalid value: unknown relationship type
>
>
> Key: ATLAS-4162
> URL: https://issues.apache.org/jira/browse/ATLAS-4162
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: kirill
>Priority: Major
>
> {"Description":"Metadata Management and Data Governance Platform over
> Hadoop","Revision":"21b15842fd74bc91910b2d8901dbea57769065d0","Version":"3.0.0-SNAPSHOT","Name":"apache-atlas"}
>
>
>
> 'http://localhost:21000/api/atlas/v2/relationship' -d '
> {
> "typeName": "Table",
> "end1": {
> "typeName": "Table",
> "uniqueAttributes": {
> "qualifiedName": "Table1"
> }
> },
> "end2": {
> "typeName": "Table",
> "uniqueAttributes": {
> "qualifiedName": "Table2"
> }
> }
> }
> '
>
> "invalid value: unknown relationship type'
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4162) invalid value: unknown relationship type
[
https://issues.apache.org/jira/browse/ATLAS-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285854#comment-17285854
]
Nixon Rodrigues commented on ATLAS-4162:
[~kirill]
Here is an example of REST API call to create relationship between 2 entities:
POST api/atlas/v2/relationship
{noformat}
{
"typeName": "",
"end1": {
"guid": ""
},
"end2": {
"guid": ""
}
}
{noformat}
All other fields are optional.
> invalid value: unknown relationship type
>
>
> Key: ATLAS-4162
> URL: https://issues.apache.org/jira/browse/ATLAS-4162
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: kirill
>Priority: Major
>
> {"Description":"Metadata Management and Data Governance Platform over
> Hadoop","Revision":"21b15842fd74bc91910b2d8901dbea57769065d0","Version":"3.0.0-SNAPSHOT","Name":"apache-atlas"}
>
>
>
> 'http://localhost:21000/api/atlas/v2/relationship' -d '
> {
> "typeName": "Table",
> "end1": {
> "typeName": "Table",
> "uniqueAttributes": {
> "qualifiedName": "Table1"
> }
> },
> "end2": {
> "typeName": "Table",
> "uniqueAttributes": {
> "qualifiedName": "Table2"
> }
> }
> }
> '
>
> "invalid value: unknown relationship type'
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4159) Build failure on ARM64
[
https://issues.apache.org/jira/browse/ATLAS-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285182#comment-17285182
]
Nixon Rodrigues commented on ATLAS-4159:
I think JDK/JVM is not compatible with your OS. you can skip the integration
tests with this option and try.
*-DskipTests*
> Build failure on ARM64
> --
>
> Key: ATLAS-4159
> URL: https://issues.apache.org/jira/browse/ATLAS-4159
> Project: Atlas
> Issue Type: Bug
> Components: storm-integration
>Reporter: Martin Tzvetanov Grigorov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Apache Atlas build fails on ARM64/AARCH64 machines with:
>
> {code:java}
> INFO] --- maven-failsafe-plugin:2.18.1:integration-test (integration-test) @
> storm-bridge ---
> [WARNING] useSystemClassloader setting has no effect when not forking
> [INFO] Failsafe report directory:
> /home/ubuntu/git/apache/atlas/addons/storm-bridge/target/failsafe-reports
> Running org.apache.atlas.storm.hook.StormAtlasHookIT
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 2.758 sec <<<
> FAILURE! - in org.apache.atlas.storm.hook.StormAtlasHookIT
> setUp(org.apache.atlas.storm.hook.StormAtlasHookIT) Time elapsed: 2.686 sec
> <<< FAILURE!
> java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni7739762391070118246.so:
> /tmp/librocksdbjni7739762391070118246.so: cannot open shared object file: No
> such file or directory (Possible cause: can't load AMD 64-bit .so on a
> AARCH64-bit platform)
> at java.lang.ClassLoader$NativeLibrary.load(Native Method)
> at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934)
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1817)
> at java.lang.Runtime.load0(Runtime.java:810)
> at java.lang.System.load(System.java:1088)
> at
> org.rocksdb.NativeLibraryLoader.loadLibraryFromJar(NativeLibraryLoader.java:78)
> at
> org.rocksdb.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:56)
> at org.rocksdb.RocksDB.loadLibrary(RocksDB.java:64)
> at org.rocksdb.RocksDB.(RocksDB.java:35)
> at
> org.apache.storm.metricstore.rocksdb.RocksDbStore.prepare(RocksDbStore.java:67)
> at
> org.apache.storm.metricstore.MetricStoreConfig.configure(MetricStoreConfig.java:33)
> at org.apache.storm.daemon.nimbus.Nimbus.(Nimbus.java:531)
> at org.apache.storm.LocalCluster.(LocalCluster.java:244)
> at org.apache.storm.LocalCluster.(LocalCluster.java:126)
> at org.apache.storm.LocalCluster$Builder.build(LocalCluster.java:1234)
> at org.apache.storm.Testing.getLocalCluster(Testing.java:231)
> at
> org.apache.atlas.storm.hook.StormTestUtil.createLocalStormCluster(StormTestUtil.java:45)
> at
> org.apache.atlas.storm.hook.StormAtlasHookIT.setUp(StormAtlasHookIT.java:53)
> Results :Failed tests:
> StormAtlasHookIT.setUp:53 » UnsatisfiedLink
> /tmp/librocksdbjni7739762391070118...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4158) Atlas authorization for Add/Update/Remove classification on entities.
Nixon Rodrigues created ATLAS-4158: -- Summary: Atlas authorization for Add/Update/Remove classification on entities. Key: ATLAS-4158 URL: https://issues.apache.org/jira/browse/ATLAS-4158 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues *Requirement* The new requirement is to provide a way to authorize who can Add/Remove/Update Classification for an entity even if the entities on which classification have to be applied do not have classifications already tagged to it. e.g. Any users belonging to user group - 'finance_group' can add classification - FINANCE_PII to any entities (these entities may not have any classifications associated) if policy has given access to the user or user-group. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4075) Client side error is thrown as server error when a mal-formed payload is used in creating a classification
[
https://issues.apache.org/jira/browse/ATLAS-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues resolved ATLAS-4075.
Resolution: Duplicate
> Client side error is thrown as server error when a mal-formed payload is used
> in creating a classification
> --
>
> Key: ATLAS-4075
> URL: https://issues.apache.org/jira/browse/ATLAS-4075
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Priority: Major
> Attachments: Screenshot 2020-12-11 at 1.29.32 PM.png, Screenshot
> 2020-12-11 at 1.31.22 PM.png
>
>
> {code:java|title=Malformed payload for creating a classification}
> {
> "classificationDefs": [
> {
> "name": "tag_1",
> }
> ]
> }
> {code}
> {code:java|title=Malformed payload for creating a classification}
> {
> "classificationDefs": [
> {
> "name": "tag_1"
> },
> ]
> }
> {code}
> There is an additional "," in the above 2 payloads, which make it a client
> side payload error. But when firing such a request 500 internal server error
> is thrown
> {code}
> 2020-12-11 07:47:28,482 ERROR - [etp402695541-552 -
> 6420db24-b42f-45eb-a6bb-25ffb3c8ce0e:] ~ Error handling a request:
> 31167d3d0dc60f70 (ExceptionMapperUtil:32)2020-12-11 07:47:28,482 ERROR -
> [etp402695541-552 - 6420db24-b42f-45eb-a6bb-25ffb3c8ce0e:] ~ Error handling a
> request: 31167d3d0dc60f70
> (ExceptionMapperUtil:32)com.fasterxml.jackson.databind.JsonMappingException:
> Unexpected character (']' (code 93)): expected a value at [Source:
> (org.eclipse.jetty.server.HttpInputOverHTTP); line: 6, column: 6] (through
> reference chain:
> org.apache.atlas.model.typedef.AtlasTypesDef["classificationDefs"]) at
> com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:397)
> at
> com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:356)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapAndThrow(BeanDeserializerBase.java:1719)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:290)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
> at com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1682)
> at
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:977)
> at
> com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:814)
> at
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
> at
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
> at
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$VoidOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:166)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at
> org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1411)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:763)
[jira] [Updated] (ATLAS-4113) Atlas UI: Entity Lineage Details Box layout rendering and centring issue.
[ https://issues.apache.org/jira/browse/ATLAS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4113: --- Fix Version/s: 2.2.0 > Atlas UI: Entity Lineage Details Box layout rendering and centring issue. > - > > Key: ATLAS-4113 > URL: https://issues.apache.org/jira/browse/ATLAS-4113 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-Atlas-4113-UI-Entity-Lineage-Details-Box-layout-rend.patch, > Atlas-4113_1.png, Atlas-4113_2.png, entity-detailpage.png > > > The lineage layout doesn't seem to be centred on the page, also there is an > effect where the lineage appears from top-right. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4113) Atlas UI: Entity Lineage Details Box layout rendering and centring issue.
[ https://issues.apache.org/jira/browse/ATLAS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17281570#comment-17281570 ] Nixon Rodrigues commented on ATLAS-4113: +1 for the patch. thank [~prasadpp13] > Atlas UI: Entity Lineage Details Box layout rendering and centring issue. > - > > Key: ATLAS-4113 > URL: https://issues.apache.org/jira/browse/ATLAS-4113 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-Atlas-4113-UI-Entity-Lineage-Details-Box-layout-rend.patch, > Atlas-4113_1.png, Atlas-4113_2.png, entity-detailpage.png > > > The lineage layout doesn't seem to be centred on the page, also there is an > effect where the lineage appears from top-right. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17278531#comment-17278531
]
Nixon Rodrigues commented on ATLAS-4116:
+1 for the patch , thanks [~prasadpp13] for the patch and [~kevalbhatt] for the
code review
> UI should not allow the user to create a glossary with blank(" ") name
> --
>
> Key: ATLAS-4116
> URL: https://issues.apache.org/jira/browse/ATLAS-4116
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch,
> 0001-ATLAS-4116-UI-V1-UI-should-not-allow-the-user-to-cre.patch,
> 0001-Atlas-4166-UI-V2-UI-should-not-allow-the-user-to-cre.patch,
> Atlas-4116Fix.png
>
>
> When just space is input the "Create" button is not enabled, but when the
> space is selected, then the "Create" button is enabled and User is allowed to
> click on "*Create*".
> This results in un-necessary failures
> *
> {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and
> name are missing. Failed to derive a unique name for Glossary"}
> *
> It is better to not allow clicking on "Create" for such an input via UI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
Nixon Rodrigues created ATLAS-4116:
--
Summary: UI should not allow the user to create a glossary with
blank(" ") name
Key: ATLAS-4116
URL: https://issues.apache.org/jira/browse/ATLAS-4116
Project: Atlas
Issue Type: Bug
Reporter: Nixon Rodrigues
Assignee: Prasad P. Pawar
When just space is input the "Create" button is not enabled, but when the space
is selected, then the "Create" button is enabled and User is allowed to click
on "*Create*".
This results in un-necessary failures
*
{"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and
name are missing. Failed to derive a unique name for Glossary"}
*
It is better to not allow clicking on "Create" for such an input via UI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4114) Atlas UI : Atlas Entity Audit UI changes for Sorting
Nixon Rodrigues created ATLAS-4114:
--
Summary: Atlas UI : Atlas Entity Audit UI changes for Sorting
Key: ATLAS-4114
URL: https://issues.apache.org/jira/browse/ATLAS-4114
Project: Atlas
Issue Type: Bug
Reporter: Nixon Rodrigues
In ATLAS-4094 Sorting functionality on Atlas entity audit api was added
{quote}/api/atlas/v2/entity/\{entity-guid}/audit?sortBy=
Unknown macro: \{user|action|timestamp}
=\{asc|desc}=10=20
{quote}
Now we can sort entity audits based on the following columns:
* user
* action
* timestamp
and also enable sort in ascending or descending order with limit and offset.
This jira is to add UI end changes for Atlas entity audit sorting
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4113) Atlas UI: Entity Lineage Details Box layout rendering and centring issue.
Nixon Rodrigues created ATLAS-4113: -- Summary: Atlas UI: Entity Lineage Details Box layout rendering and centring issue. Key: ATLAS-4113 URL: https://issues.apache.org/jira/browse/ATLAS-4113 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues Attachments: entity-detailpage.png The lineage layout doesn't seem to be centred on the page, also there is an effect where the lineage appears from top-right. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
Nixon Rodrigues created ATLAS-4107:
--
Summary: Atlas not picking the ldap bind password from the correct
jceks file.
Key: ATLAS-4107
URL: https://issues.apache.org/jira/browse/ATLAS-4107
Project: Atlas
Issue Type: Bug
Reporter: Nixon Rodrigues
There are two jceks file in Atlas, ldap bind password should be retrieved from
{{hadoop.security.credential.provider.path}} instead
{{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4107) Atlas not picking the ldap bind password from the correct jceks file.
[
https://issues.apache.org/jira/browse/ATLAS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues reassigned ATLAS-4107:
--
Assignee: Nixon Rodrigues
> Atlas not picking the ldap bind password from the correct jceks file.
> -
>
> Key: ATLAS-4107
> URL: https://issues.apache.org/jira/browse/ATLAS-4107
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
>
> There are two jceks file in Atlas, ldap bind password should be retrieved
> from {{hadoop.security.credential.provider.path}} instead
> {{cert.stores.credential.provider.path}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4102) UI - DSL Search: Web UI hangs When Executing Certain Queries
Nixon Rodrigues created ATLAS-4102:
--
Summary: UI - DSL Search: Web UI hangs When Executing Certain
Queries
Key: ATLAS-4102
URL: https://issues.apache.org/jira/browse/ATLAS-4102
Project: Atlas
Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Nixon Rodrigues
Assignee: Prasad P. Pawar
*Background*
Certain types of Advanced Search (DSL) queries within Atlas return
_AtlasSearchResult_ in a slightly different format.
The current UI is not able to render the search results.
The REST APIs however, return the output successfully.
*Steps to Duplicate*
# Within Atlas web UI, Advanced Search, execute: _hive_table groupby (owner)
select min(name)_ _URL:
http://:31000/index.html#!/search/searchResult?query=hive_table%20groupby%20(owner)%20select%20min(name)=dsl=true_
_Expected result:_ Search results should be displayed.
Actual result: Web UI freezes. Upon inspecting using Developer tools, a JS
exception is displayed.
Additional info:
Query: _hive_table groupby(owner) select owner, max(name)_
Output json:
{code:java}
{
"attributes": {
"name": [
"owner",
"max(name)"
],
"values": [
[
"hive",
"tuarp_uarmt_pmtreq_h"
],
[
"iadetldev",
"video_analytics_log_id"
],
[
"atsacoli",
"aj_psync_test_h"
]
]
},
"approximateCount": -1
}{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4102) UI - DSL Search: UI hangs When Executing Certain Queries
[
https://issues.apache.org/jira/browse/ATLAS-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-4102:
---
Summary: UI - DSL Search: UI hangs When Executing Certain Queries (was:
UI - DSL Search: Web UI hangs When Executing Certain Queries)
> UI - DSL Search: UI hangs When Executing Certain Queries
> -
>
> Key: ATLAS-4102
> URL: https://issues.apache.org/jira/browse/ATLAS-4102
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
>
> *Background*
> Certain types of Advanced Search (DSL) queries within Atlas return
> _AtlasSearchResult_ in a slightly different format.
> The current UI is not able to render the search results.
> The REST APIs however, return the output successfully.
> *Steps to Duplicate*
> # Within Atlas web UI, Advanced Search, execute: _hive_table groupby (owner)
> select min(name)_ _URL:
> http://:31000/index.html#!/search/searchResult?query=hive_table%20groupby%20(owner)%20select%20min(name)=dsl=true_
> _Expected result:_ Search results should be displayed.
> Actual result: Web UI freezes. Upon inspecting using Developer tools, a JS
> exception is displayed.
> Additional info:
> Query: _hive_table groupby(owner) select owner, max(name)_
> Output json:
> {code:java}
> {
> "attributes": {
> "name": [
> "owner",
> "max(name)"
> ],
> "values": [
> [
> "hive",
> "tuarp_uarmt_pmtreq_h"
> ],
> [
> "iadetldev",
> "video_analytics_log_id"
> ],
> [
> "atsacoli",
> "aj_psync_test_h"
> ]
> ]
> },
> "approximateCount": -1
> }{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4101) 500 internal server error is thrown instead of 400 malformed request from atlas when the payload is malformed
Nixon Rodrigues created ATLAS-4101:
--
Summary: 500 internal server error is thrown instead of 400
malformed request from atlas when the payload is malformed
Key: ATLAS-4101
URL: https://issues.apache.org/jira/browse/ATLAS-4101
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
{code:java|title=Malformed payload for creating a classification}
{
"classificationDefs": [
{
"name": "tag_1",
}
]
}
{code}
{code:java|title=Malformed payload for creating a classification}
{
"classificationDefs": [
{
"name": "tag_1"
},
]
}
{code}
There is an additional "," in the above 2 payloads, which make it a client side
payload error.
But when firing such a request 500 internal server error is thrown
*These are client errors that are being thrown as server errors*
{code:java}
2020-12-11 07:47:28,482 ERROR - [etp402695541-552 -
6420db24-b42f-45eb-a6bb-25ffb3c8ce0e:] ~ Error handling a request:
31167d3d0dc60f70 (ExceptionMapperUtil:32)2020-12-11 07:47:28,482 ERROR -
[etp402695541-552 - 6420db24-b42f-45eb-a6bb-25ffb3c8ce0e:] ~ Error handling a
request: 31167d3d0dc60f70
(ExceptionMapperUtil:32)com.fasterxml.jackson.databind.JsonMappingException:
Unexpected character (']' (code 93)): expected a value at [Source:
(org.eclipse.jetty.server.HttpInputOverHTTP); line: 6, column: 6] (through
reference chain:
org.apache.atlas.model.typedef.AtlasTypesDef["classificationDefs"]) at
com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:397)
at
com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:356)
at
com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapAndThrow(BeanDeserializerBase.java:1719)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:290)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
at com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1682)
at com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:977)
at
com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:814)
at
com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
at
com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
at
com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:153)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$VoidOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:166)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at
org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1411)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:763) at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1651)
at org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:106) at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1638)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
at
[jira] [Commented] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api
[
https://issues.apache.org/jira/browse/ATLAS-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260225#comment-17260225
]
Nixon Rodrigues commented on ATLAS-4092:
+1 for the patch , thanks [~mandar_va]
> Remove unused attributes and add right attributes to the atlas admin audit api
> --
>
> Key: ATLAS-4092
> URL: https://issues.apache.org/jira/browse/ATLAS-4092
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4092.patch
>
>
> {code:java|title=Sample payload:}
> {
> "currentPage": "page",
> "pageSize": "per_page",
> "totalPages": "total_pages",
> "totalRecords": "total_entries",
> "sortKey": "sort_by",
> "order": "order",
> "directions": {
> "1": "desc",
> "-1": "asc"
> },
> "auditFilters": {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "operation",
> "operator": "eq",
> "attributeValue": "TYPE_DEF_CREATE"
> }
> ]
> },
> "limit": 25,
> "offset": 0
> }
> {code}
> Here the following attributes do not work:
> {code}
> "sortKey": "sort_by",
> "order": "order",
> {code}
> Instead the following works
> {code}
> "sortBy" : "startTime",
> "sortOrder" : "DESCENDING",
> {code}
> sortKey and order has to be removed and sortBy and sortOrder has to be added
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api
[
https://issues.apache.org/jira/browse/ATLAS-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-4092:
---
Comment: was deleted
(was: +1 for the patch, thanks [~mandar_va])
> Remove unused attributes and add right attributes to the atlas admin audit api
> --
>
> Key: ATLAS-4092
> URL: https://issues.apache.org/jira/browse/ATLAS-4092
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4092.patch
>
>
> {code:java|title=Sample payload:}
> {
> "currentPage": "page",
> "pageSize": "per_page",
> "totalPages": "total_pages",
> "totalRecords": "total_entries",
> "sortKey": "sort_by",
> "order": "order",
> "directions": {
> "1": "desc",
> "-1": "asc"
> },
> "auditFilters": {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "operation",
> "operator": "eq",
> "attributeValue": "TYPE_DEF_CREATE"
> }
> ]
> },
> "limit": 25,
> "offset": 0
> }
> {code}
> Here the following attributes do not work:
> {code}
> "sortKey": "sort_by",
> "order": "order",
> {code}
> Instead the following works
> {code}
> "sortBy" : "startTime",
> "sortOrder" : "DESCENDING",
> {code}
> sortKey and order has to be removed and sortBy and sortOrder has to be added
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4092) Remove unused attributes and add right attributes to the atlas admin audit api
[
https://issues.apache.org/jira/browse/ATLAS-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259523#comment-17259523
]
Nixon Rodrigues commented on ATLAS-4092:
+1 for the patch, thanks [~mandar_va]
> Remove unused attributes and add right attributes to the atlas admin audit api
> --
>
> Key: ATLAS-4092
> URL: https://issues.apache.org/jira/browse/ATLAS-4092
> Project: Atlas
> Issue Type: Improvement
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: ATLAS-4092.patch
>
>
> {code:java|title=Sample payload:}
> {
> "currentPage": "page",
> "pageSize": "per_page",
> "totalPages": "total_pages",
> "totalRecords": "total_entries",
> "sortKey": "sort_by",
> "order": "order",
> "directions": {
> "1": "desc",
> "-1": "asc"
> },
> "auditFilters": {
> "condition": "AND",
> "criterion": [
> {
> "attributeName": "operation",
> "operator": "eq",
> "attributeValue": "TYPE_DEF_CREATE"
> }
> ]
> },
> "limit": 25,
> "offset": 0
> }
> {code}
> Here the following attributes do not work:
> {code}
> "sortKey": "sort_by",
> "order": "order",
> {code}
> Instead the following works
> {code}
> "sortBy" : "startTime",
> "sortOrder" : "DESCENDING",
> {code}
> sortKey and order has to be removed and sortBy and sortOrder has to be added
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-3980) classic UI: When classification is created, the left pane takes the control to the end of the long list of classifications
[ https://issues.apache.org/jira/browse/ATLAS-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-3980. Resolution: Fixed > classic UI: When classification is created, the left pane takes the control > to the end of the long list of classifications > -- > > Key: ATLAS-3980 > URL: https://issues.apache.org/jira/browse/ATLAS-3980 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3980.patch > > > When a new classification is created, the control goes to the end of the list > of classifications created, instead of taking it to the new classification > created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3980) classic UI: When classification is created, the left pane takes the control to the end of the long list of classifications
[ https://issues.apache.org/jira/browse/ATLAS-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17257968#comment-17257968 ] Nixon Rodrigues commented on ATLAS-3980: +1 for the patch, [~kevalbhatt] thanks for the patch > classic UI: When classification is created, the left pane takes the control > to the end of the long list of classifications > -- > > Key: ATLAS-3980 > URL: https://issues.apache.org/jira/browse/ATLAS-3980 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3980.patch > > > When a new classification is created, the control goes to the end of the list > of classifications created, instead of taking it to the new classification > created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4066) [UI] Attribute Filter: 'is null' and 'is not null' does not work for user-defined properties
[ https://issues.apache.org/jira/browse/ATLAS-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253995#comment-17253995 ] Nixon Rodrigues commented on ATLAS-4066: +1 for the patch, [~prasadpp13] thanks for the patch > [UI] Attribute Filter: 'is null' and 'is not null' does not work for > user-defined properties > - > > Key: ATLAS-4066 > URL: https://issues.apache.org/jira/browse/ATLAS-4066 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-Atlas-4066-UI-Attribute-Filter-is-null-and-is-not-nu.patch, Screenshot > 2020-12-08 at 11.56.36 PM.png, Screenshot 2020-12-08 at 11.56.45 PM.png, > Screenshot 2020-12-08 at 11.56.54 PM.png, Screenshot 2020-12-10 at 12.56.11 > PM.png > > > For user-defined properties, currently only 'contains' filter is working. > !Screenshot 2020-12-08 at 11.56.54 PM.png! > When I select either 'is null' or 'is not null', nothing happens (both when i > click on apply or search) > !Screenshot 2020-12-08 at 11.56.45 PM.png! > !Screenshot 2020-12-08 at 11.56.36 PM.png! > 'is null' or 'is not null' works fine for all other System attributes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4078) UI - Lineage tab not shown on UI for entity with type Dataset or Process.
[
https://issues.apache.org/jira/browse/ATLAS-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250131#comment-17250131
]
Nixon Rodrigues commented on ATLAS-4078:
+1 , thanks [~prasadpp13] for the fix.
> UI - Lineage tab not shown on UI for entity with type Dataset or Process.
> -
>
> Key: ATLAS-4078
> URL: https://issues.apache.org/jira/browse/ATLAS-4078
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.8.3, 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-Atlas-4078-0.8-branch-UI-To-display-Lineage-tab-for-.patch,
> 0001-Atlas-4078-master-UI-Lineage-tab-not-shown-on-UI-for.patch
>
>
>
> Two Dataset type entities created and a Process type entity with inputs and
> outputs attribute as dataset entities respectively is created .
>
> *Creating base Entities*
> To begin with, on a blank installation of Atlas, first two DataSet entities
> are created through the use of the Atlas REST API. Both entities are created
> with separate CURL requests to the following REST
> endpoint:
> POST /api/atlas/v2/entity
> Payload for entity 1
> {noformat}
> {
> "entity": {
> "typeName": "DataSet",
> "attributes": {
> "qualifiedName": "dataset1@cluster01",
> "name": "DataSet1",
> "description": "This is an Example DataSet Created Through the REST API for
> Lineage",
> "owner": "admin"
> },
> "guid": -1
> }
> }
> {noformat}
> Payload for entity 2
>
> {noformat}
> {
> "entity": {
> "typeName": "DataSet",
> "attributes": {
> "qualifiedName": "dataset2@cluster01",
> "name": "DataSet2",
> "description": "This is an Example DataSet Created Through the REST API for
> Lineage",
> "owner": "admin"
> },
> "guid": -1
> }
> }
> {noformat}
>
> *Creating a Process Entity*
> Next a Process entity is created with the following REST API call (Note, the
> guids for each of the DataSet's were found using the Atlas UI):
> POST /api/atlas/v2/entity
> Payload
>
> {noformat}
> {
> "entity": {
> "typeName": "Process",
> "attributes": {
> "qualifiedName": "exampleProcess@cluster01",
> "name": "Example Process",
> "description": "This is an Example Process Created Through the REST API",
> "owner": "admin",
> "inputs": [
> {
> "guid": "3b5c3fce-fb83-4b2b-b95f-0cf76ae88eb6",
> "typeName": "DataSet",
> "uniqueAttributes": {
> "qualifiedName": "dataset1@cluster01"
> }
> }
> ],
> "outputs": [
> {
> "guid": "1d019580-86a2-4da3-9146-8bd81c74608b",
> "typeName": "DataSet",
> "uniqueAttributes": {
> "qualifiedName": "dataset2@cluster01"
> }
> }
> ]
> },
> "guid": -1
> }
> }
> {noformat}
> The REST API call successfully creates a Process entity within Atlas, which
> can be found in the UI
> In Atlas server lineage entity is created but on Atlas UI the lineage tab is
> not shown for these entities.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4078) UI - Lineage tab not shown on UI for entity with type Dataset or Process.
Nixon Rodrigues created ATLAS-4078:
--
Summary: UI - Lineage tab not shown on UI for entity with type
Dataset or Process.
Key: ATLAS-4078
URL: https://issues.apache.org/jira/browse/ATLAS-4078
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Affects Versions: 2.1.0, 0.8.3
Reporter: Nixon Rodrigues
Assignee: Prasad P. Pawar
Two Dataset type entities created and a Process type entity with inputs and
outputs attribute as dataset entities respectively is created .
*Creating base Entities*
To begin with, on a blank installation of Atlas, first two DataSet entities
are created through the use of the Atlas REST API. Both entities are created
with separate CURL requests to the following REST
endpoint:
POST /api/atlas/v2/entity
Payload for entity 1
{noformat}
{
"entity": {
"typeName": "DataSet",
"attributes": {
"qualifiedName": "dataset1@cluster01",
"name": "DataSet1",
"description": "This is an Example DataSet Created Through the REST API for
Lineage",
"owner": "admin"
},
"guid": -1
}
}
{noformat}
Payload for entity 2
{noformat}
{
"entity": {
"typeName": "DataSet",
"attributes": {
"qualifiedName": "dataset2@cluster01",
"name": "DataSet2",
"description": "This is an Example DataSet Created Through the REST API for
Lineage",
"owner": "admin"
},
"guid": -1
}
}
{noformat}
*Creating a Process Entity*
Next a Process entity is created with the following REST API call (Note, the
guids for each of the DataSet's were found using the Atlas UI):
POST /api/atlas/v2/entity
Payload
{noformat}
{
"entity": {
"typeName": "Process",
"attributes": {
"qualifiedName": "exampleProcess@cluster01",
"name": "Example Process",
"description": "This is an Example Process Created Through the REST API",
"owner": "admin",
"inputs": [
{
"guid": "3b5c3fce-fb83-4b2b-b95f-0cf76ae88eb6",
"typeName": "DataSet",
"uniqueAttributes": {
"qualifiedName": "dataset1@cluster01"
}
}
],
"outputs": [
{
"guid": "1d019580-86a2-4da3-9146-8bd81c74608b",
"typeName": "DataSet",
"uniqueAttributes": {
"qualifiedName": "dataset2@cluster01"
}
}
]
},
"guid": -1
}
}
{noformat}
The REST API call successfully creates a Process entity within Atlas, which can
be found in the UI
In Atlas server lineage entity is created but on Atlas UI the lineage tab is
not shown for these entities.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4064) Atlas HEADER validation
Nixon Rodrigues created ATLAS-4064: -- Summary: Atlas HEADER validation Key: ATLAS-4064 URL: https://issues.apache.org/jira/browse/ATLAS-4064 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues Validation of HEADERS in backend. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4058) UI - On entity details page, for Hive column 'position' is getting set as 0(zero)
[ https://issues.apache.org/jira/browse/ATLAS-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4058: --- Summary: UI - On entity details page, for Hive column 'position' is getting set as 0(zero) (was: On entity details page, for Hive column 'position' is getting set as 0(zero)) > UI - On entity details page, for Hive column 'position' is getting set as > 0(zero) > - > > Key: ATLAS-4058 > URL: https://issues.apache.org/jira/browse/ATLAS-4058 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: Atlas-4058.patch, Atlas-4058.png, Atlas-4058_1.png, > screenshot-issues.apache.org-2020.12.03-10_47_09.png > > > Hive Column position should get set to N/A OR blank instead of 0. > PFA image -- This message was sent by Atlassian Jira (v8.3.4#803005)
