[jira] [Created] (ATLAS-4883) Atlas UI CSRF token error
Paresh Devalia created ATLAS-4883: - Summary: Atlas UI CSRF token error Key: ATLAS-4883 URL: https://issues.apache.org/jira/browse/ATLAS-4883 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia Assignee: Paresh Devalia Attachments: 1-_Atlas_webUI_with_error.png, 2-_Atlas_webUI_with_error.png => Customer is facing issues , as sometimes the basic search is not working and the error: + Missing header or invalid Header value for CSRF Vulnerability Protection + is coming up intermittently on the right corner of the WebUI. Please refer to the screenshots attached to the Jira - Dev analysis steps to reproduce # Set the session-timeout to 1 min in web.xml file. # Wait for 1 min after Atlas login. # Do basic search and response will get as 400 error code with Missing header or invalid Header value for CSRF Vulnerability Protection. # Also while doing metric API (Statistics) call we get the 409 error code and it redirect to login page. Which should be a correct way. As the sever-side session get timed-out and user was in-active. so it get 400 error code. Fix will provide redirection to login-page or any other solution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4883) Atlas UI CSRF token error
[ https://issues.apache.org/jira/browse/ATLAS-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4883: -- Attachment: 1-_Atlas_webUI_with_error.png 2-_Atlas_webUI_with_error.png > Atlas UI CSRF token error > - > > Key: ATLAS-4883 > URL: https://issues.apache.org/jira/browse/ATLAS-4883 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > Attachments: 1-_Atlas_webUI_with_error.png, > 2-_Atlas_webUI_with_error.png > > > => Customer is facing issues , as sometimes the basic search is not working > and the error: > + > Missing header or invalid Header value for CSRF Vulnerability Protection > + > is coming up intermittently on the right corner of the WebUI. > Please refer to the screenshots attached to the Jira > > - > Dev analysis > steps to reproduce > # Set the session-timeout to 1 min in web.xml file. > # Wait for 1 min after Atlas login. > # Do basic search and response will get as 400 error code with Missing > header or invalid Header value for CSRF Vulnerability Protection. > # Also while doing metric API (Statistics) call we get the 409 error code > and it redirect to login page. Which should be a correct way. > As the sever-side session get timed-out and user was in-active. so it get 400 > error code. > Fix will provide redirection to login-page or any other solution. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4846) Source the atlas-env file in ATLAS import script to get all the argument
[ https://issues.apache.org/jira/browse/ATLAS-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia resolved ATLAS-4846. --- Resolution: Fixed > Source the atlas-env file in ATLAS import script to get all the argument > > > Key: ATLAS-4846 > URL: https://issues.apache.org/jira/browse/ATLAS-4846 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > User has to run manually export command to get all the argument which are > set, to run the Atlas import script. > The problem is not with the Atlas service itself but with these scripts: > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-kafka.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hbase.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh > > Need to set argument before this script are being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4867) Improve Metrics API
Paresh Devalia created ATLAS-4867: - Summary: Improve Metrics API Key: ATLAS-4867 URL: https://issues.apache.org/jira/browse/ATLAS-4867 Project: Atlas Issue Type: Bug Components: atlas-intg Reporter: Paresh Devalia Assignee: Paresh Devalia Attachments: Screenshot from 2024-02-05 20-30-39.png Metrics API : http://<>/api/atlas/admin/metrics 1. There is some information in the Metrics API response, which is not been used like Count of the typeAndSubTypes, Active, deleted, Shell Approach: Identify time taken by the above counts Take reading of metric api Take reading of metric api without the above counts !Screenshot from 2024-02-05 20-30-39.png! 2. Also we can get the total number of count of vertices and edges present in graph This helps in estimating the time on Reindexing Patch. Also it may be helpful while debugging the escalations Approach: Embed this count in MetricUtil Or Create seperate API h3. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4764) CuratorFrameWork should work only with Zookeeper HA mode
[ https://issues.apache.org/jira/browse/ATLAS-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835598#comment-17835598 ] Paresh Devalia commented on ATLAS-4764: --- Hi Team, Code review:- https://reviews.apache.org/r/74738/diff/5#index_header > CuratorFrameWork should work only with Zookeeper HA mode > > > Key: ATLAS-4764 > URL: https://issues.apache.org/jira/browse/ATLAS-4764 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > Zookeeper Non-HA mode should not run through CuratorFramework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4846) Source the atlas-env file in ATLAS import script to get all the argument
[ https://issues.apache.org/jira/browse/ATLAS-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835597#comment-17835597 ] Paresh Devalia commented on ATLAS-4846: --- Hi Team, Code review:-[https://reviews.apache.org/r/74954/] > Source the atlas-env file in ATLAS import script to get all the argument > > > Key: ATLAS-4846 > URL: https://issues.apache.org/jira/browse/ATLAS-4846 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > User has to run manually export command to get all the argument which are > set, to run the Atlas import script. > The problem is not with the Atlas service itself but with these scripts: > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-kafka.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hbase.sh > * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh > > Need to set argument before this script are being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4846) Source the atlas-env file in ATLAS import script to get all the argument
Paresh Devalia created ATLAS-4846: - Summary: Source the atlas-env file in ATLAS import script to get all the argument Key: ATLAS-4846 URL: https://issues.apache.org/jira/browse/ATLAS-4846 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia Assignee: Paresh Devalia User has to run manually export command to get all the argument which are set, to run the Atlas import script. The problem is not with the Atlas service itself but with these scripts: * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-kafka.sh * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hbase.sh * /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh Need to set argument before this script are being called. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4804) set name field with qualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia resolved ATLAS-4804.
---
Resolution: Fixed
> set name field with qualifiedName for impala_process and
> impala_process_execution
> -
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments:
> ATLAS-4804-Migrated-Data-Process-Entity-Name-not-set.patch
>
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ATLAS-4803) Optimize Relationship Edge fetch
[ https://issues.apache.org/jira/browse/ATLAS-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia resolved ATLAS-4803. --- Resolution: Fixed > Optimize Relationship Edge fetch > > > Key: ATLAS-4803 > URL: https://issues.apache.org/jira/browse/ATLAS-4803 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > CU kafka lag was not decreasing for ATLAS_HOOK topics, create Entity API was > taking 50-60 sec per request. > Hive_table count was 10mn record. > Impala_lineage_column count was 26mn count. > Able to reproduce the issue on in-house cluster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4803) Optimize Relationship Edge fetch
[ https://issues.apache.org/jira/browse/ATLAS-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4803: -- Summary: Optimize Relationship Edge fetch (was: Optimize Edge fetch) > Optimize Relationship Edge fetch > > > Key: ATLAS-4803 > URL: https://issues.apache.org/jira/browse/ATLAS-4803 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > CU kafka lag was not decreasing for ATLAS_HOOK topics, create Entity API was > taking 50-60 sec per request. > Hive_table count was 10mn record. > Impala_lineage_column count was 26mn count. > Able to reproduce the issue on in-house cluster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4804) set name field with qualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4804:
--
Summary: set name field with qualifiedName for impala_process and
impala_process_execution (was: Entity Name not set to QualifiedName for
impala_process and impala_process_execution)
> set name field with qualifiedName for impala_process and
> impala_process_execution
> -
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments:
> ATLAS-4804-Migrated-Data-Process-Entity-Name-not-set.patch
>
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4804) Entity Name not set to QualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4804:
--
Summary: Entity Name not set to QualifiedName for impala_process and
impala_process_execution (was: Migrated Data: Process Entity Name not set to
QualifiedName for impala_process and impala_process_execution)
> Entity Name not set to QualifiedName for impala_process and
> impala_process_execution
>
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments:
> ATLAS-4804-Migrated-Data-Process-Entity-Name-not-set.patch
>
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4804) Migrated Data: Process Entity Name not set to QualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4804:
--
Attachment: ATLAS-4804-Migrated-Data-Process-Entity-Name-not-set.patch
> Migrated Data: Process Entity Name not set to QualifiedName for
> impala_process and impala_process_execution
> ---
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments:
> ATLAS-4804-Migrated-Data-Process-Entity-Name-not-set.patch
>
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4804) Migrated Data: Process Entity Name not set to QualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4804:
--
External issue URL: (was: https://reviews.apache.org/r/74708/)
> Migrated Data: Process Entity Name not set to QualifiedName for
> impala_process and impala_process_execution
> ---
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4804) Migrated Data: Process Entity Name not set to QualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781636#comment-17781636
]
Paresh Devalia commented on ATLAS-4804:
---
Code review board :- https://reviews.apache.org/r/74708/
> Migrated Data: Process Entity Name not set to QualifiedName for
> impala_process and impala_process_execution
> ---
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4804) Migrated Data: Process Entity Name not set to QualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4804:
--
External issue URL: https://reviews.apache.org/r/74708/
> Migrated Data: Process Entity Name not set to QualifiedName for
> impala_process and impala_process_execution
> ---
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
>
> *Background*
> In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as
> the name. Latest version onwards where _name_ and _qualifiedName_ are same.
> *Solution*
> Add Java patch that updates the name property.
> *Impact of Not Doing this Update*
> The _queryText_ in _impala_process_ and impala_process_execution entities
> tends to be large. The name field is part of {_}AtlasEntityHeader{_}. When
> fetching search results, lineage display are some of the flows that have
> these entities.
> *Issue* *occurred*
> Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
> Error from server at
> [http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
> Exception writing document id muydq8 to the index; possible analysis error:
> Document contains at least one immense term in field="cgsl_s" (whose UTF8
> encoding is longer than the max length 32766), all of which were skipped.
> Please correct the analyzer to not produce such terms. The prefix of the
> first immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116,
> 111, 32, 103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103,
> 105, 103, 121]...', original message: bytes can be at most 32766 in length;
> got 41069. Perhaps the document has an indexed string field (solr.StrField)
> which is too large at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
> at
> org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
> at
> org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
> at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
> ... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4804) Migrated Data: Process Entity Name not set to QualifiedName for impala_process and impala_process_execution
[
https://issues.apache.org/jira/browse/ATLAS-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4804:
--
Description:
*Background*
In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as the
name. Latest version onwards where _name_ and _qualifiedName_ are same.
*Solution*
Add Java patch that updates the name property.
*Impact of Not Doing this Update*
The _queryText_ in _impala_process_ and impala_process_execution entities tends
to be large. The name field is part of {_}AtlasEntityHeader{_}. When fetching
search results, lineage display are some of the flows that have these entities.
*Issue* *occurred*
Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
Error from server at
[http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
Exception writing document id muydq8 to the index; possible analysis error:
Document contains at least one immense term in field="cgsl_s" (whose UTF8
encoding is longer than the max length 32766), all of which were skipped.
Please correct the analyzer to not produce such terms. The prefix of the first
immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116, 111, 32,
103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103, 105, 103,
121]...', original message: bytes can be at most 32766 in length; got 41069.
Perhaps the document has an indexed string field (solr.StrField) which is too
large at
org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
at org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
... 9 more
was:
*Background*
In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as the
name. This in 7.1.7 SP2 onwards where _name_ and _qualifiedName_ are same.
*Solution*
Add Java patch that updates the name property.
*Impact of Not Doing this Update*
The _queryText_ in _impala_process_ and impala_process_execution entities tends
to be large. The name field is part of {_}AtlasEntityHeader{_}. When fetching
search results, lineage display are some of the flows that have these entities.
*Issue* *occurred*
Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
Error from server at
[http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
Exception writing document id muydq8 to the index; possible analysis error:
Document contains at least one immense term in field="cgsl_s" (whose UTF8
encoding is longer than the max length 32766), all of which were skipped.
Please correct the analyzer to not produce such terms. The prefix of the first
immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116, 111, 32,
103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103, 105, 103,
121]...', original message: bytes can be at most 32766 in length; got 41069.
Perhaps the document has an indexed string field (solr.StrField) which is too
large at
org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
at org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
... 9 more
> Migrated Data: Process Entity Name not set to QualifiedName for
> impala_process and impala_process_execution
> ---
>
> Key: ATLAS-4804
> URL: https://issues.apache.org/jira/browse/ATLAS-4804
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
>
> *Background*
> In
[jira] [Created] (ATLAS-4804) Migrated Data: Process Entity Name not set to QualifiedName for impala_process and impala_process_execution
Paresh Devalia created ATLAS-4804:
-
Summary: Migrated Data: Process Entity Name not set to
QualifiedName for impala_process and impala_process_execution
Key: ATLAS-4804
URL: https://issues.apache.org/jira/browse/ATLAS-4804
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Paresh Devalia
Assignee: Paresh Devalia
*Background*
In Atlas process names ({_}impala_process.name{_}) was using _queryText_ as the
name. This in 7.1.7 SP2 onwards where _name_ and _qualifiedName_ are same.
*Solution*
Add Java patch that updates the name property.
*Impact of Not Doing this Update*
The _queryText_ in _impala_process_ and impala_process_execution entities tends
to be large. The name field is part of {_}AtlasEntityHeader{_}. When fetching
search results, lineage display are some of the flows that have these entities.
*Issue* *occurred*
Caused by: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException:
Error from server at
[http://cdhworker11.cinconet.local:8993/solr/vertex_index_shard3_replica_n14:]
Exception writing document id muydq8 to the index; possible analysis error:
Document contains at least one immense term in field="cgsl_s" (whose UTF8
encoding is longer than the max length 32766), all of which were skipped.
Please correct the analyzer to not produce such terms. The prefix of the first
immense term is: '[105, 110, 115, 101, 114, 116, 32, 105, 110, 116, 111, 32,
103, 105, 103, 121, 97, 46, 115, 116, 103, 95, 108, 97, 98, 95, 103, 105, 103,
121]...', original message: bytes can be at most 32766 in length; got 41069.
Perhaps the document has an indexed string field (solr.StrField) which is too
large at
org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:125)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.getRouteException(CloudSolrClient.java:46)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.directUpdate(BaseCloudSolrClient.java:557)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1046)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:906)
at
org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:838)
at org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:633)
at org.janusgraph.diskstorage.solr.Solr6Index.restore(Solr6Index.java:593)
... 9 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4803) Optimize Edge fetch
Paresh Devalia created ATLAS-4803: - Summary: Optimize Edge fetch Key: ATLAS-4803 URL: https://issues.apache.org/jira/browse/ATLAS-4803 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia Assignee: Paresh Devalia CU kafka lag was not decreasing for ATLAS_HOOK topics, create Entity API was taking 50-60 sec per request. Hive_table count was 10mn record. Impala_lineage_column count was 26mn count. Able to reproduce the issue on in-house cluster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4764) CuratorFrameWork should work only with Zookeeper HA mode
[ https://issues.apache.org/jira/browse/ATLAS-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4764: -- Component/s: atlas-core > CuratorFrameWork should work only with Zookeeper HA mode > > > Key: ATLAS-4764 > URL: https://issues.apache.org/jira/browse/ATLAS-4764 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > Zookeeper Non-HA mode should not run through CuratorFramework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4764) CuratorFrameWork should work only with Zookeeper HA mode
[ https://issues.apache.org/jira/browse/ATLAS-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4764: -- Description: Zookeeper Non-HA mode should not run through CuratorFramework. (was: Zookeeper Non-HA mode runs with CuratorFramework.) > CuratorFrameWork should work only with Zookeeper HA mode > > > Key: ATLAS-4764 > URL: https://issues.apache.org/jira/browse/ATLAS-4764 > Project: Atlas > Issue Type: Bug >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > Zookeeper Non-HA mode should not run through CuratorFramework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4764) CuratorFrameWork should work only with Zookeeper HA mode
[ https://issues.apache.org/jira/browse/ATLAS-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4764: -- Summary: CuratorFrameWork should work only with Zookeeper HA mode (was: CuratorFrameWork should work only Zookeeper HA mode) > CuratorFrameWork should work only with Zookeeper HA mode > > > Key: ATLAS-4764 > URL: https://issues.apache.org/jira/browse/ATLAS-4764 > Project: Atlas > Issue Type: Bug >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > Zookeeper Non-HA mode runs with CuratorFramework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4764) CuratorFrameWork should work only Zookeeper HA mode
Paresh Devalia created ATLAS-4764: - Summary: CuratorFrameWork should work only Zookeeper HA mode Key: ATLAS-4764 URL: https://issues.apache.org/jira/browse/ATLAS-4764 Project: Atlas Issue Type: Bug Reporter: Paresh Devalia Assignee: Paresh Devalia Zookeeper Non-HA mode runs with CuratorFramework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4731) Entity fetch api call fails for some entity which has businessMetaData with Biginteger attributes
[ https://issues.apache.org/jira/browse/ATLAS-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4731: -- Attachment: BigInt_Test_Entity_BusMeta.json BigInt_Test_Create.json > Entity fetch api call fails for some entity which has businessMetaData with > Biginteger attributes > - > > Key: ATLAS-4731 > URL: https://issues.apache.org/jira/browse/ATLAS-4731 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > Attachments: BigInt_Test_Create.json, BigInt_Test_Entity_BusMeta.json > > > Using the beta interface we can see our custom typeDefs in the left hand panel > >-- localTypeDef (1,012) > custom_typedef_a (1) > custom_typedef_b (1,008) > custom_typedef_c (3) > Selecting localTypeDev/custom__b displays the list of entities in the right > hand panel. > Selecting any of the results generates a "Something went wrong" popup, the > rotating loading icon and an unpopulated > Properties/Relationships/Classifications/Audits/Tasks page. > The following ERROR message can be seen in the ATLAS application.log :- > ERROR - [etp2052996178-280 - xnxnxxnn--nnnx-xnnn-nxnnxnnnxnnx:] ~ graph > rollback due to exception (GraphTransactionInterceptor:200) > java.lang.ArrayIndexOutOfBoundsException: Required size [1] exceeds actual > remaining size [0] > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.require(StaticArrayBuffer.java:94) > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.getByte(StaticArrayBuffer.java:170) > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.getBytes(StaticArrayBuffer.java:253) > at > org.janusgraph.diskstorage.util.ReadArrayBuffer.getBytes(ReadArrayBuffer.java:120) > at > org.janusgraph.graphdb.database.serialize.attribute.ByteArraySerializer.read(ByteArraySerializer.java:46) > at > org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:36) > at > org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:30) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectNotNullInternal(StandardSerializer.java:305) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectInternal(StandardSerializer.java:295) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObject(StandardSerializer.java:275) > at > org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:215) > at > org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:205) > at > org.janusgraph.graphdb.database.EdgeSerializer.parseRelation(EdgeSerializer.java:135) > at > org.janusgraph.graphdb.database.EdgeSerializer.readRelation(EdgeSerializer.java:135) > at > org.janusgraph.graphdb.transaction.RelationConstructor.readRelation(RelationConstructor.java:70) > at > org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:57) > at > org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:45) > at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:72) > at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:38) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusElement.getProperty(AtlasJanusElement.java:66) > at > org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.getProperty(AtlasGraphUtilsV2.java:283) > ~~ > So while writing the BusinessMetaData for BigInteger, value=4 we do not call > BigIntegerSerializer class, so i won't throw the exception. > And while access through UI it fetch data from BigintegerSerializer class and > throw the Required size [1] exceeds actual remaining size [0] exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4731) Entity fetch api call fails for some entity which has businessMetaData with Biginteger attributes
[ https://issues.apache.org/jira/browse/ATLAS-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia reassigned ATLAS-4731: - Assignee: Paresh Devalia > Entity fetch api call fails for some entity which has businessMetaData with > Biginteger attributes > - > > Key: ATLAS-4731 > URL: https://issues.apache.org/jira/browse/ATLAS-4731 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > Using the beta interface we can see our custom typeDefs in the left hand panel > >-- localTypeDef (1,012) > custom_typedef_a (1) > custom_typedef_b (1,008) > custom_typedef_c (3) > Selecting localTypeDev/custom__b displays the list of entities in the right > hand panel. > Selecting any of the results generates a "Something went wrong" popup, the > rotating loading icon and an unpopulated > Properties/Relationships/Classifications/Audits/Tasks page. > The following ERROR message can be seen in the ATLAS application.log :- > ERROR - [etp2052996178-280 - xnxnxxnn--nnnx-xnnn-nxnnxnnnxnnx:] ~ graph > rollback due to exception (GraphTransactionInterceptor:200) > java.lang.ArrayIndexOutOfBoundsException: Required size [1] exceeds actual > remaining size [0] > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.require(StaticArrayBuffer.java:94) > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.getByte(StaticArrayBuffer.java:170) > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.getBytes(StaticArrayBuffer.java:253) > at > org.janusgraph.diskstorage.util.ReadArrayBuffer.getBytes(ReadArrayBuffer.java:120) > at > org.janusgraph.graphdb.database.serialize.attribute.ByteArraySerializer.read(ByteArraySerializer.java:46) > at > org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:36) > at > org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:30) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectNotNullInternal(StandardSerializer.java:305) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectInternal(StandardSerializer.java:295) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObject(StandardSerializer.java:275) > at > org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:215) > at > org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:205) > at > org.janusgraph.graphdb.database.EdgeSerializer.parseRelation(EdgeSerializer.java:135) > at > org.janusgraph.graphdb.database.EdgeSerializer.readRelation(EdgeSerializer.java:135) > at > org.janusgraph.graphdb.transaction.RelationConstructor.readRelation(RelationConstructor.java:70) > at > org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:57) > at > org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:45) > at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:72) > at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:38) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusElement.getProperty(AtlasJanusElement.java:66) > at > org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.getProperty(AtlasGraphUtilsV2.java:283) > ~~ > So while writing the BusinessMetaData for BigInteger, value=4 we do not call > BigIntegerSerializer class, so i won't throw the exception. > And while access through UI it fetch data from BigintegerSerializer class and > throw the Required size [1] exceeds actual remaining size [0] exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4731) Entity fetch api call fails for some entity which has businessMetaData with Biginteger attributes
Paresh Devalia created ATLAS-4731: - Summary: Entity fetch api call fails for some entity which has businessMetaData with Biginteger attributes Key: ATLAS-4731 URL: https://issues.apache.org/jira/browse/ATLAS-4731 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia Using the beta interface we can see our custom typeDefs in the left hand panel >-- localTypeDef (1,012) custom_typedef_a (1) custom_typedef_b (1,008) custom_typedef_c (3) Selecting localTypeDev/custom__b displays the list of entities in the right hand panel. Selecting any of the results generates a "Something went wrong" popup, the rotating loading icon and an unpopulated Properties/Relationships/Classifications/Audits/Tasks page. The following ERROR message can be seen in the ATLAS application.log :- ERROR - [etp2052996178-280 - xnxnxxnn--nnnx-xnnn-nxnnxnnnxnnx:] ~ graph rollback due to exception (GraphTransactionInterceptor:200) java.lang.ArrayIndexOutOfBoundsException: Required size [1] exceeds actual remaining size [0] at org.janusgraph.diskstorage.util.StaticArrayBuffer.require(StaticArrayBuffer.java:94) at org.janusgraph.diskstorage.util.StaticArrayBuffer.getByte(StaticArrayBuffer.java:170) at org.janusgraph.diskstorage.util.StaticArrayBuffer.getBytes(StaticArrayBuffer.java:253) at org.janusgraph.diskstorage.util.ReadArrayBuffer.getBytes(ReadArrayBuffer.java:120) at org.janusgraph.graphdb.database.serialize.attribute.ByteArraySerializer.read(ByteArraySerializer.java:46) at org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:36) at org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:30) at org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectNotNullInternal(StandardSerializer.java:305) at org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectInternal(StandardSerializer.java:295) at org.janusgraph.graphdb.database.serialize.StandardSerializer.readObject(StandardSerializer.java:275) at org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:215) at org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:205) at org.janusgraph.graphdb.database.EdgeSerializer.parseRelation(EdgeSerializer.java:135) at org.janusgraph.graphdb.database.EdgeSerializer.readRelation(EdgeSerializer.java:135) at org.janusgraph.graphdb.transaction.RelationConstructor.readRelation(RelationConstructor.java:70) at org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:57) at org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:45) at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:72) at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:38) at org.apache.atlas.repository.graphdb.janus.AtlasJanusElement.getProperty(AtlasJanusElement.java:66) at org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.getProperty(AtlasGraphUtilsV2.java:283) ~~ So while writing the BusinessMetaData for BigInteger, value=4 we do not call BigIntegerSerializer class, so i won't throw the exception. And while access through UI it fetch data from BigintegerSerializer class and throw the Required size [1] exceeds actual remaining size [0] exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4627) Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command.
[ https://issues.apache.org/jira/browse/ATLAS-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603900#comment-17603900 ] Paresh Devalia commented on ATLAS-4627: --- Patch in [review board|https://reviews.apache.org/r/74036/] > Delete Existing entity in Atlas which are not present in Hive, DB wise > through Import-hive command. > --- > > Key: ATLAS-4627 > URL: https://issues.apache.org/jira/browse/ATLAS-4627 > Project: Atlas > Issue Type: Bug >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > Attachments: ATLAS-4627-6.patch > > > PROBLEM STATEMENT > Created a DB_1 and DB_2 in Hive and disable the Atlas hook from hive and > hive_tez. > Created tables with 10 record in DB_1 and DB_2 . > In Atlas UI we checked it has no entity created, so we ran import-hive.sh > bash import-hive.sh -d DB_1 -t table_1, so this command will only create one > entity in atlas. > bash import-hive.sh -d DB_1, so this command will create all entity in atlas. > Drop table_1 from DB_1 and DB_2 in Hive, but will be present in atlas as > hooks are disable, so we will ran import-hive command to delete from atlas . > bash import-hive.sh -d DB_1 -t table_1 -deleteNonExisting, this command will > delete all the table from all DB which are present in Atlas and dropped from > Hive. > As we have mention -d and -t argument in command for DB and table wise > deleting, but still it ran for all DB and Tables. > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4627) Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command.
[ https://issues.apache.org/jira/browse/ATLAS-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603898#comment-17603898 ] Paresh Devalia commented on ATLAS-4627: --- Patch in [https://reviews.apache.org/r/74036/ |review board] > Delete Existing entity in Atlas which are not present in Hive, DB wise > through Import-hive command. > --- > > Key: ATLAS-4627 > URL: https://issues.apache.org/jira/browse/ATLAS-4627 > Project: Atlas > Issue Type: Bug >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > Attachments: ATLAS-4627-6.patch > > > PROBLEM STATEMENT > Created a DB_1 and DB_2 in Hive and disable the Atlas hook from hive and > hive_tez. > Created tables with 10 record in DB_1 and DB_2 . > In Atlas UI we checked it has no entity created, so we ran import-hive.sh > bash import-hive.sh -d DB_1 -t table_1, so this command will only create one > entity in atlas. > bash import-hive.sh -d DB_1, so this command will create all entity in atlas. > Drop table_1 from DB_1 and DB_2 in Hive, but will be present in atlas as > hooks are disable, so we will ran import-hive command to delete from atlas . > bash import-hive.sh -d DB_1 -t table_1 -deleteNonExisting, this command will > delete all the table from all DB which are present in Atlas and dropped from > Hive. > As we have mention -d and -t argument in command for DB and table wise > deleting, but still it ran for all DB and Tables. > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (ATLAS-4627) Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command.
[ https://issues.apache.org/jira/browse/ATLAS-4627 ] Paresh Devalia deleted comment on ATLAS-4627: --- was (Author: pareshd): Patch in [https://reviews.apache.org/r/74036/ |review board] > Delete Existing entity in Atlas which are not present in Hive, DB wise > through Import-hive command. > --- > > Key: ATLAS-4627 > URL: https://issues.apache.org/jira/browse/ATLAS-4627 > Project: Atlas > Issue Type: Bug >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > Attachments: ATLAS-4627-6.patch > > > PROBLEM STATEMENT > Created a DB_1 and DB_2 in Hive and disable the Atlas hook from hive and > hive_tez. > Created tables with 10 record in DB_1 and DB_2 . > In Atlas UI we checked it has no entity created, so we ran import-hive.sh > bash import-hive.sh -d DB_1 -t table_1, so this command will only create one > entity in atlas. > bash import-hive.sh -d DB_1, so this command will create all entity in atlas. > Drop table_1 from DB_1 and DB_2 in Hive, but will be present in atlas as > hooks are disable, so we will ran import-hive command to delete from atlas . > bash import-hive.sh -d DB_1 -t table_1 -deleteNonExisting, this command will > delete all the table from all DB which are present in Atlas and dropped from > Hive. > As we have mention -d and -t argument in command for DB and table wise > deleting, but still it ran for all DB and Tables. > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4638) Column inconsistent in Hive and Atlas
[ https://issues.apache.org/jira/browse/ATLAS-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia resolved ATLAS-4638. --- Assignee: Paresh Devalia Resolution: Cannot Reproduce > Column inconsistent in Hive and Atlas > - > > Key: ATLAS-4638 > URL: https://issues.apache.org/jira/browse/ATLAS-4638 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > PROBLEM STATEMENT > Created a DB_1 in Hive and disable the Atlas hook from hive and hive_tez. > Created 1 tables with 2 column in DB_1. > In Atlas UI we checked it has no entity created, so we ran import-hive.sh > bash import-hive.sh -d DB_1 -t table_1, so this command will only create one > entity with 2 column in atlas. > Add 3rd column on that table from hive -> ALTER TABLE tableName ADD COLUMNS > (columnName int); > Than we ran import-hive.sh -d DB_1 -t table_1. > In Atlas UI we checked entity already created, but 3rd column is not added. > 3 column in hive and in atlas only 2 column present. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4638) Column inconsistent in Hive and Atlas
Paresh Devalia created ATLAS-4638: - Summary: Column inconsistent in Hive and Atlas Key: ATLAS-4638 URL: https://issues.apache.org/jira/browse/ATLAS-4638 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia PROBLEM STATEMENT Created a DB_1 in Hive and disable the Atlas hook from hive and hive_tez. Created 1 tables with 2 column in DB_1. In Atlas UI we checked it has no entity created, so we ran import-hive.sh bash import-hive.sh -d DB_1 -t table_1, so this command will only create one entity with 2 column in atlas. Add 3rd column on that table from hive -> ALTER TABLE tableName ADD COLUMNS (columnName int); Than we ran import-hive.sh -d DB_1 -t table_1. In Atlas UI we checked entity already created, but 3rd column is not added. 3 column in hive and in atlas only 2 column present. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4627) Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command.
Paresh Devalia created ATLAS-4627: - Summary: Delete Existing entity in Atlas which are not present in Hive, DB wise through Import-hive command. Key: ATLAS-4627 URL: https://issues.apache.org/jira/browse/ATLAS-4627 Project: Atlas Issue Type: Bug Reporter: Paresh Devalia Assignee: Paresh Devalia PROBLEM STATEMENT Created a DB_1 and DB_2 in Hive and disable the Atlas hook from hive and hive_tez. Created tables with 10 record in DB_1 and DB_2 . In Atlas UI we checked it has no entity created, so we ran import-hive.sh bash import-hive.sh -d DB_1 -t table_1, so this command will only create one entity in atlas. bash import-hive.sh -d DB_1, so this command will create all entity in atlas. Drop table_1 from DB_1 and DB_2 in Hive, but will be present in atlas as hooks are disable, so we will ran import-hive command to delete from atlas . bash import-hive.sh -d DB_1 -t table_1 -deleteNonExisting, this command will delete all the table from all DB which are present in Atlas and dropped from Hive. As we have mention -d and -t argument in command for DB and table wise deleting, but still it ran for all DB and Tables. h4. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (ATLAS-4614) Deferred Actions : Add classification name in response
[ https://issues.apache.org/jira/browse/ATLAS-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4614: -- Summary: Deferred Actions : Add classification name in response (was: Deferred Actions : Support to add classification name instead of classificationVertexId) > Deferred Actions : Add classification name in response > > > Key: ATLAS-4614 > URL: https://issues.apache.org/jira/browse/ATLAS-4614 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > In /api/atlas/admin/tasks call , when a tag is propagated , the > classificationVertexId is displayed. It becomes tough to debug when there are > many pending tasks . classification name can be added in the response in > addition to/instead of classificationVertexId. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (ATLAS-4615) Not able to edit custom entity in Atlas
[
https://issues.apache.org/jira/browse/ATLAS-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4615:
--
Description:
PROBLEM STATEMENT
Not able to edit custom entities in Atlas
~~
ANALYSIS
1. Customer created a custom type and custom entity
2. If the custom type has attributes with datatype array then we are not able
to edit the entity
example:
{ "name":"Master_Item", "dataTypeName":"array",
"multiplicity":"optional", "isComposite":false, "isUnique":false,
"isIndexable":true, "reverseAttributeName":null }
was:
PROBLEM STATEMENT
Not able to edit custom entities in Atlas
~~
ANALYSIS
1. Customer created a custom type and custom entity
2. If the custom type has attributes with datatype array then we are not able
to edit the entity
example:
{ "name":"Master_Item", "dataTypeName":"array",
"multiplicity":"optional", "isComposite":false, "isUnique":false,
"isIndexable":true, "reverseAttributeName":null }
~~
EXPECTED ENGINEERING ACTION
Kindly help debug this issue
> Not able to edit custom entity in Atlas
> ---
>
> Key: ATLAS-4615
> URL: https://issues.apache.org/jira/browse/ATLAS-4615
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments: type.json
>
>
> PROBLEM STATEMENT
> Not able to edit custom entities in Atlas
> ~~
> ANALYSIS
> 1. Customer created a custom type and custom entity
> 2. If the custom type has attributes with datatype array then we are not able
> to edit the entity
> example:
> { "name":"Master_Item", "dataTypeName":"array",
> "multiplicity":"optional", "isComposite":false, "isUnique":false,
> "isIndexable":true, "reverseAttributeName":null }
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ATLAS-4615) Not able to edit custom entity in Atlas
[
https://issues.apache.org/jira/browse/ATLAS-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4615:
--
Description:
PROBLEM STATEMENT
Not able to edit custom entities in Atlas
~~
ANALYSIS
1. Customer created a custom type and custom entity
2. If the custom type has attributes with datatype array then we are not able
to edit the entity
example:
{ "name":"Master_Item", "dataTypeName":"array",
"multiplicity":"optional", "isComposite":false, "isUnique":false,
"isIndexable":true, "reverseAttributeName":null }
~~
EXPECTED ENGINEERING ACTION
Kindly help debug this issue
was:
PROBLEM STATEMENT
Not able to edit custom entities in Atlas
~~
SUPPORT ANALYSIS
1. Customer created a custom type and custom entity
2. If the custom type has attributes with datatype array then we are not able
to edit the entity
example:
{ "name":"Master_Item", "dataTypeName":"array",
"multiplicity":"optional", "isComposite":false, "isUnique":false,
"isIndexable":true, "reverseAttributeName":null }
~~
EXPECTED ENGINEERING ACTION
Kindly help debug this issue
> Not able to edit custom entity in Atlas
> ---
>
> Key: ATLAS-4615
> URL: https://issues.apache.org/jira/browse/ATLAS-4615
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments: type.json
>
>
> PROBLEM STATEMENT
> Not able to edit custom entities in Atlas
> ~~
> ANALYSIS
> 1. Customer created a custom type and custom entity
> 2. If the custom type has attributes with datatype array then we are not able
> to edit the entity
> example:
> { "name":"Master_Item", "dataTypeName":"array",
> "multiplicity":"optional", "isComposite":false, "isUnique":false,
> "isIndexable":true, "reverseAttributeName":null }
>
> ~~
> EXPECTED ENGINEERING ACTION
> Kindly help debug this issue
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ATLAS-4615) Not able to edit custom entity in Atlas
[
https://issues.apache.org/jira/browse/ATLAS-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4615:
--
Description:
PROBLEM STATEMENT
Not able to edit custom entities in Atlas
~~
SUPPORT ANALYSIS
1. Customer created a custom type and custom entity
2. If the custom type has attributes with datatype array then we are not able
to edit the entity
example:
{ "name":"Master_Item", "dataTypeName":"array",
"multiplicity":"optional", "isComposite":false, "isUnique":false,
"isIndexable":true, "reverseAttributeName":null }
~~
EXPECTED ENGINEERING ACTION
Kindly help debug this issue
was:
PROBLEM STATEMENT
Not able to edit custom entities in Atlas
~~
SUPPORT ANALYSIS
1. Customer created a custom type and custom entity
2. If the custom type has attributes with datatype array then we are not able
to edit the entity
example:
{ "name":"Master_Item", "dataTypeName":"array",
"multiplicity":"optional", "isComposite":false, "isUnique":false,
"isIndexable":true, "reverseAttributeName":null }
,
I am able to reproduce this and can share the squadron cluster if required
~~
EXPECTED ENGINEERING ACTION
Kindly help debug this issue
> Not able to edit custom entity in Atlas
> ---
>
> Key: ATLAS-4615
> URL: https://issues.apache.org/jira/browse/ATLAS-4615
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Paresh Devalia
>Assignee: Paresh Devalia
>Priority: Major
> Attachments: type.json
>
>
> PROBLEM STATEMENT
> Not able to edit custom entities in Atlas
> ~~
> SUPPORT ANALYSIS
> 1. Customer created a custom type and custom entity
> 2. If the custom type has attributes with datatype array then we are not able
> to edit the entity
> example:
> { "name":"Master_Item", "dataTypeName":"array",
> "multiplicity":"optional", "isComposite":false, "isUnique":false,
> "isIndexable":true, "reverseAttributeName":null }
>
> ~~
> EXPECTED ENGINEERING ACTION
> Kindly help debug this issue
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (ATLAS-4615) Not able to edit custom entity in Atlas
Paresh Devalia created ATLAS-4615:
-
Summary: Not able to edit custom entity in Atlas
Key: ATLAS-4615
URL: https://issues.apache.org/jira/browse/ATLAS-4615
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Paresh Devalia
Assignee: Paresh Devalia
Attachments: type.json
PROBLEM STATEMENT
Not able to edit custom entities in Atlas
~~
SUPPORT ANALYSIS
1. Customer created a custom type and custom entity
2. If the custom type has attributes with datatype array then we are not able
to edit the entity
example:
{ "name":"Master_Item", "dataTypeName":"array",
"multiplicity":"optional", "isComposite":false, "isUnique":false,
"isIndexable":true, "reverseAttributeName":null }
,
I am able to reproduce this and can share the squadron cluster if required
~~
EXPECTED ENGINEERING ACTION
Kindly help debug this issue
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (ATLAS-4614) Deferred Actions : Support to add classification name instead of classificationVertexId
Paresh Devalia created ATLAS-4614: - Summary: Deferred Actions : Support to add classification name instead of classificationVertexId Key: ATLAS-4614 URL: https://issues.apache.org/jira/browse/ATLAS-4614 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia Assignee: Paresh Devalia In /api/atlas/admin/tasks call , when a tag is propagated , the classificationVertexId is displayed. It becomes tough to debug when there are many pending tasks . classification name can be added in the response in addition to/instead of classificationVertexId. -- This message was sent by Atlassian Jira (v8.20.7#820007)
