[jira] [Assigned] (ATLAS-4062) Fails to create Classification if the validity period is greater than 12 hours
[ https://issues.apache.org/jira/browse/ATLAS-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4062: -- Assignee: Prasad P. Pawar > Fails to create Classification if the validity period is greater than 12 hours > -- > > Key: ATLAS-4062 > URL: https://issues.apache.org/jira/browse/ATLAS-4062 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Major > Attachments: End_date_selected_14_15.png, End_date_shows_2_15.png > > > Classification date picker does not work if the time selected is greater than > 12 hours. > For example:: If the time selected is 14:15 it shows 2:15 > > PFA evidence files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4062) [UI] Fails to create Classification if the validity period is greater than 12 hours
[ https://issues.apache.org/jira/browse/ATLAS-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4062: --- Attachment: Atlas-4062-date.png > [UI] Fails to create Classification if the validity period is greater than 12 > hours > --- > > Key: ATLAS-4062 > URL: https://issues.apache.org/jira/browse/ATLAS-4062 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Major > Attachments: Atlas-4062-date.png, Atlas-4062.patch, > End_date_selected_14_15.png, End_date_shows_2_15.png > > > Classification date picker does not work if the time selected is greater than > 12 hours. > For example:: If the time selected is 14:15 it shows 2:15 > > PFA evidence files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4058) 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 ] Prasad P. Pawar reassigned ATLAS-4058: -- Assignee: Prasad P. Pawar > 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 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: 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] [Assigned] (ATLAS-4056) [UI] While searching nodes in Lineage, previously searched/highlighted labels does not get clear
[ https://issues.apache.org/jira/browse/ATLAS-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4056: -- Assignee: Prasad P. Pawar > [UI] While searching nodes in Lineage, previously searched/highlighted labels > does not get clear > > > Key: ATLAS-4056 > URL: https://issues.apache.org/jira/browse/ATLAS-4056 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: lineage_search_selection_issue.mkv > > > When User searches a node in lineage, the node label get highlighted and also > a rectangle appears(expected), as soon as user searches another node, current > search selection works fine but the previous search selection remains > highlighted. > PFA evidence file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-4058) 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=17245000#comment-17245000 ] Prasad P. Pawar edited comment on ATLAS-4058 at 12/7/20, 7:57 AM: -- Hi, position=0 is shown as N/A. was (Author: prasadpp13): Hi, position=0 is shown as N/A., as suggested by Nixon sir. > 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 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: Atlas-4058.patch, > 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] [Comment Edited] (ATLAS-4058) 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=17245000#comment-17245000 ] Prasad P. Pawar edited comment on ATLAS-4058 at 12/7/20, 7:57 AM: -- Hi, Now position=0 is shown as N/A. was (Author: prasadpp13): Hi, position=0 is shown as N/A. > 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 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: Atlas-4058.patch, > 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] [Updated] (ATLAS-4058) 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 ] Prasad P. Pawar updated ATLAS-4058: --- Attachment: Atlas-4058.png > 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, > 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] [Updated] (ATLAS-4058) 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 ] Prasad P. Pawar updated ATLAS-4058: --- Fix Version/s: 2.2.0 3.0.0 > 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 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: Atlas-4058.patch, > 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] [Updated] (ATLAS-4058) 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 ] Prasad P. Pawar updated ATLAS-4058: --- Component/s: atlas-webui > 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, > 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] [Updated] (ATLAS-4058) 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 ] Prasad P. Pawar updated ATLAS-4058: --- Attachment: Atlas-4058_1.png > 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)
[jira] [Updated] (ATLAS-4062) [UI] Fails to create Classification if the validity period is greater than 12 hours
[ https://issues.apache.org/jira/browse/ATLAS-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4062: --- Attachment: (was: Atlas-4062.patch) > [UI] Fails to create Classification if the validity period is greater than 12 > hours > --- > > Key: ATLAS-4062 > URL: https://issues.apache.org/jira/browse/ATLAS-4062 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-Atlas-4062-UI-Classification-Daterange-Picker-TimeDa.patch, > Atlas-4062-date.png, End_date_selected_14_15.png, End_date_shows_2_15.png > > > Classification date picker does not work if the time selected is greater than > 12 hours. > For example:: If the time selected is 14:15 it shows 2:15 > > PFA evidence files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4062) [UI] Fails to create Classification if the validity period is greater than 12 hours
[ https://issues.apache.org/jira/browse/ATLAS-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4062: --- Attachment: 0001-Atlas-4062-UI-Classification-Daterange-Picker-TimeDa.patch > [UI] Fails to create Classification if the validity period is greater than 12 > hours > --- > > Key: ATLAS-4062 > URL: https://issues.apache.org/jira/browse/ATLAS-4062 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-Atlas-4062-UI-Classification-Daterange-Picker-TimeDa.patch, > Atlas-4062-date.png, End_date_selected_14_15.png, End_date_shows_2_15.png > > > Classification date picker does not work if the time selected is greater than > 12 hours. > For example:: If the time selected is 14:15 it shows 2:15 > > PFA evidence files -- 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=17252620#comment-17252620 ] Prasad P. Pawar commented on ATLAS-4066: Hi, The fix for 'is null' or 'is not null' is provided in the uploaded 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] [Assigned] (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:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4066: -- Assignee: Prasad P. Pawar > [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: 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=17249507#comment-17249507
]
Prasad P. Pawar commented on ATLAS-4078:
Hi,
Now in Dataset and Process type Lineage tab will be visible, these changes are
fixed in the provided Two patches,
one is for Master, and the other is for branch-0.8.
> 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] [Assigned] (ATLAS-4073) [UI] Column sorting not working in BusinessMetadata details page
[ https://issues.apache.org/jira/browse/ATLAS-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4073: -- Assignee: Prasad P. Pawar > [UI] Column sorting not working in BusinessMetadata details page > > > Key: ATLAS-4073 > URL: https://issues.apache.org/jira/browse/ATLAS-4073 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-Atlas-4073-UI-Column-sorting-not-working-in-Business.patch, sorting > works only once for column maxlength and Enable Multivalues.mkv > > > In Business Metadata, column sorting for 'Enable Multivalue' and 'Max Length' > sorting does not work. PFA -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4073) [UI] Column sorting not working in BusinessMetadata details page
[ https://issues.apache.org/jira/browse/ATLAS-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4073: --- Fix Version/s: 2.2.0 3.0.0 > [UI] Column sorting not working in BusinessMetadata details page > > > Key: ATLAS-4073 > URL: https://issues.apache.org/jira/browse/ATLAS-4073 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-Atlas-4073-UI-Column-sorting-not-working-in-Business.patch, sorting > works only once for column maxlength and Enable Multivalues.mkv > > > In Business Metadata, column sorting for 'Enable Multivalue' and 'Max Length' > sorting does not work. PFA -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4073) [UI] Column sorting not working in BusinessMetadata details page
[ https://issues.apache.org/jira/browse/ATLAS-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4073: --- Component/s: atlas-webui > [UI] Column sorting not working in BusinessMetadata details page > > > Key: ATLAS-4073 > URL: https://issues.apache.org/jira/browse/ATLAS-4073 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-Atlas-4073-UI-Column-sorting-not-working-in-Business.patch, sorting > works only once for column maxlength and Enable Multivalues.mkv > > > In Business Metadata, column sorting for 'Enable Multivalue' and 'Max Length' > sorting does not work. PFA -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4073) [UI] Column sorting not working in BusinessMetadata details page
[ https://issues.apache.org/jira/browse/ATLAS-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4073: --- Affects Version/s: 2.1.0 > [UI] Column sorting not working in BusinessMetadata details page > > > Key: ATLAS-4073 > URL: https://issues.apache.org/jira/browse/ATLAS-4073 > 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-4073-UI-Column-sorting-not-working-in-Business.patch, sorting > works only once for column maxlength and Enable Multivalues.mkv > > > In Business Metadata, column sorting for 'Enable Multivalue' and 'Max Length' > sorting does not work. PFA -- 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
]
Prasad P. Pawar updated ATLAS-4102:
---
Attachment: Atlas-4102.png
> 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
> Attachments:
> 0001-Atlas-4102-UI-DSL-Search-UI-hangs-When-Executing-Cer.patch,
> Atlas-4102.png
>
>
> *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] [Comment Edited] (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:comment-tabpanel=17264641#comment-17264641
]
Prasad P. Pawar edited comment on ATLAS-4102 at 1/14/21, 6:51 AM:
--
HI,
I have provided the fix in this available patch.
was (Author: prasadpp13):
HI,
I have provided the fix in theis available patch.
> 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
> Attachments:
> 0001-Atlas-4102-UI-DSL-Search-UI-hangs-When-Executing-Cer.patch
>
>
> *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-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 ] Prasad P. Pawar updated ATLAS-4058: --- Attachment: (was: Atlas-4058.patch) > 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.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] [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 ] Prasad P. Pawar updated ATLAS-4058: --- Attachment: 0001-ATLAS-4058-UI-Entity-detail-page-Hive-Column-Positio.patch > 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] [Updated] (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:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4116:
---
Attachment: 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch
> 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,
> 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] [Updated] (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:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4116:
---
Attachment: (was:
0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch)
> 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: 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] [Assigned] (ATLAS-4114) Atlas UI : Atlas Entity Audit UI changes for Sorting
[
https://issues.apache.org/jira/browse/ATLAS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar reassigned ATLAS-4114:
--
Assignee: Prasad P. Pawar
> 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
> Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: audit, sorting
> Fix For: 3.0.0
>
>
> 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] [Assigned] (ATLAS-4074) [UI] Image download in Typesystem and Lineage has issue
[ https://issues.apache.org/jira/browse/ATLAS-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4074: -- Assignee: Prasad P. Pawar > [UI] Image download in Typesystem and Lineage has issue > --- > > Key: ATLAS-4074 > URL: https://issues.apache.org/jira/browse/ATLAS-4074 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > Lineage_issue_shows_black_background_if_downloaded_image_with_search_applied.png, > Typesystem_issue_overlapped_entity_names_in_exported_image.png > > > # In TypeSystem, downloaded image shows overlapped names of hosts/nodes if > the name length is too large. > # When user downloads the lineage with the search result shows highlighted > image with black background, also label is not properly visible due to black > background. > PFA evidence files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (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 ] Prasad P. Pawar reassigned ATLAS-4113: -- Assignee: Prasad P. Pawar > 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: 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] [Updated] (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:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4116:
---
Attachment: Atlas-4116Fix.png
> 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: 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] [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=17274404#comment-17274404
]
Prasad P. Pawar commented on ATLAS-4116:
Hi,
This fix is provided on the available patch, also include a fix on
creating/edit glossary/term/classification, create an entity, detail page
label, create business metadata, save search input.
> 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,
> 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] [Updated] (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:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4116:
---
Attachment: 0001-ATLAS-4116-UI-V1-UI-should-not-allow-the-user-to-cre.patch
> 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,
> 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] [Updated] (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:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4116:
---
Attachment: 0001-Atlas-4166-UI-V2-UI-should-not-allow-the-user-to-cre.patch
> 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] [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=17277187#comment-17277187
]
Prasad P. Pawar commented on ATLAS-4116:
thanks [~kevalbhatt] for review comments,
There was one case in the edit glossary, where this button was getting enable
on the change of not required input field, if the required field is empty.
so to check all the inputs required field, a Filter is used.
I have bind the *keyup* on *modal-body*, and the changes are made in the update
patch.
> 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] [Comment Edited] (ATLAS-4283) UI: Description cannot be made blank for classification
[ https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349272#comment-17349272 ] Prasad P. Pawar edited comment on ATLAS-4283 at 6/9/21, 10:01 AM: -- Hi, While creating Classification with an empty description field, then the default classification name is returned in the response as a description value. As the description field cannot be empty so this fix is provided, On UI when you enter the Classification name, the same is getting reflected on the description field, Description field validation is also done for an empty value, also the Description field is editable. was (Author: prasadpp13): Hi, This fix is provided in the uploaded patch file. > UI: Description cannot be made blank for classification > --- > > Key: ATLAS-4283 > URL: https://issues.apache.org/jira/browse/ATLAS-4283 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch > > > If there is an existing description for a classification, and if the user > attempts to update it to blank, he will not be able to do so. > The API response for when the user inputs a blank value shows that the > updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4326) Atlas UI: Multiple continuous space is accepted on Short description for Classifications, Gloassarys, Categorys & Terms .
[ https://issues.apache.org/jira/browse/ATLAS-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4326: --- Attachment: (was: 0001-ATLAS-4326-Atlas-UI-Multiple-continuous-space-is-acc.patch) > Atlas UI: Multiple continuous space is accepted on Short description for > Classifications, Gloassarys, Categorys & Terms . > - > > Key: ATLAS-4326 > URL: https://issues.apache.org/jira/browse/ATLAS-4326 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4326-1-Atlas-UI-Multiple-continuous-space-is-a.patch > > > Add multiple continuous spaces in the short description field, this value is > accepted on UI by clicking the Save/Update button. > After updating the values, the Detail page doesn't show the entered value of > Short description files. eg: " This is Term1 " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4326) Atlas UI: Multiple continuous space is accepted on Short description for Classifications, Gloassarys, Categorys & Terms .
[ https://issues.apache.org/jira/browse/ATLAS-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4326: --- Attachment: 0001-ATLAS-4326-1-Atlas-UI-Multiple-continuous-space-is-a.patch > Atlas UI: Multiple continuous space is accepted on Short description for > Classifications, Gloassarys, Categorys & Terms . > - > > Key: ATLAS-4326 > URL: https://issues.apache.org/jira/browse/ATLAS-4326 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4326-1-Atlas-UI-Multiple-continuous-space-is-a.patch > > > Add multiple continuous spaces in the short description field, this value is > accepted on UI by clicking the Save/Update button. > After updating the values, the Detail page doesn't show the entered value of > Short description files. eg: " This is Term1 " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4283) UI: Description cannot be made blank for classification
[ https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360596#comment-17360596 ] Prasad P. Pawar commented on ATLAS-4283: cdpd commit id: f048f84e78840387822d5ab5a5678f17756aa0b1 > UI: Description cannot be made blank for classification > --- > > Key: ATLAS-4283 > URL: https://issues.apache.org/jira/browse/ATLAS-4283 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch > > > If there is an existing description for a classification, and if the user > attempts to update it to blank, he will not be able to do so. > The API response for when the user inputs a blank value shows that the > updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-4283) UI: Description cannot be made blank for classification
[ https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360596#comment-17360596 ] Prasad P. Pawar edited comment on ATLAS-4283 at 6/10/21, 6:39 AM: -- cdpd master:commit id: f048f84e78840387822d5ab5a5678f17756aa0b1 was (Author: prasadpp13): cdpd commit id: f048f84e78840387822d5ab5a5678f17756aa0b1 > UI: Description cannot be made blank for classification > --- > > Key: ATLAS-4283 > URL: https://issues.apache.org/jira/browse/ATLAS-4283 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch > > > If there is an existing description for a classification, and if the user > attempts to update it to blank, he will not be able to do so. > The API response for when the user inputs a blank value shows that the > updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4295) UI: The short/long description of term & category doesnt get updated immediately when made blank
[ https://issues.apache.org/jira/browse/ATLAS-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360594#comment-17360594 ] Prasad P. Pawar commented on ATLAS-4295: commit it: 5c11def9ed377d18199281c223d57c9725ff054a > UI: The short/long description of term & category doesnt get updated > immediately when made blank > > > Key: ATLAS-4295 > URL: https://issues.apache.org/jira/browse/ATLAS-4295 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4295-UI-UI-The-short-long-description-of-term-.patch > > > When one empties the the short and long description fields of term & category > and saves, > the UI doesn't get reflected immediately. But on refresh, it gets reflected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4328) Add flink favicon
[ https://issues.apache.org/jira/browse/ATLAS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4328: --- Fix Version/s: 2.2.0 3.0.0 > Add flink favicon > - > > Key: ATLAS-4328 > URL: https://issues.apache.org/jira/browse/ATLAS-4328 > Project: Atlas > Issue Type: Task > Components: atlas-intg >Reporter: Josh Yeh >Assignee: Prasad P. Pawar >Priority: Trivial > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4328-UI-Add-flink-favicon-images-fixed-1.patch, flink.png, > flink_process.png, image-2021-06-07-08-41-37-559.png > > > While testing ATLAS-3812, I noticed flink_application and flink_process icons > are missing. File this Jira to track. > !image-2021-06-07-08-41-37-559.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4316) UI : When lineage contains shell entities, the image couldn't be downloaded.
[ https://issues.apache.org/jira/browse/ATLAS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4316: --- Attachment: 0001-ATLAS-4316-UI-2-When-lineage-contains-shell-entities.patch > UI : When lineage contains shell entities, the image couldn't be downloaded. > > > Key: ATLAS-4316 > URL: https://issues.apache.org/jira/browse/ATLAS-4316 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4316-UI-1-When-lineage-contains-shell-entities.patch, > 0001-ATLAS-4316-UI-2-When-lineage-contains-shell-entities.patch > > > Added a screen recording where the lineage contains shell entities so the > image is not downloaded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4316) UI : When lineage contains shell entities, the image couldn't be downloaded.
[ https://issues.apache.org/jira/browse/ATLAS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367025#comment-17367025 ] Prasad P. Pawar commented on ATLAS-4316: The updated patch had pom.xml file changes for excluding .svg file > UI : When lineage contains shell entities, the image couldn't be downloaded. > > > Key: ATLAS-4316 > URL: https://issues.apache.org/jira/browse/ATLAS-4316 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4316-UI-1-When-lineage-contains-shell-entities.patch, > 0001-ATLAS-4316-UI-2-When-lineage-contains-shell-entities.patch > > > Added a screen recording where the lineage contains shell entities so the > image is not downloaded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (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:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4286: -- Assignee: Prasad P. Pawar > 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 > > 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-4283) UI: Description cannot be made blank for classification
[ https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4283: --- Fix Version/s: 2.2.0 3.0.0 > UI: Description cannot be made blank for classification > --- > > Key: ATLAS-4283 > URL: https://issues.apache.org/jira/browse/ATLAS-4283 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch > > > If there is an existing description for a classification, and if the user > attempts to update it to blank, he will not be able to do so. > The API response for when the user inputs a blank value shows that the > updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Prasad P. Pawar updated ATLAS-4337: --- Fix Version/s: 2.2.0 3.0.0 > 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 > Fix For: 3.0.0, 2.2.0 > > 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] [Updated] (ATLAS-4316) UI : When lineage contains shell entities, the image couldn't be downloaded.
[ https://issues.apache.org/jira/browse/ATLAS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4316: --- Fix Version/s: 2.2.0 3.0.0 > UI : When lineage contains shell entities, the image couldn't be downloaded. > > > Key: ATLAS-4316 > URL: https://issues.apache.org/jira/browse/ATLAS-4316 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4316-UI-1-When-lineage-contains-shell-entities.patch, > 0001-ATLAS-4316-UI-2-When-lineage-contains-shell-entities.patch > > > Added a screen recording where the lineage contains shell entities so the > image is not downloaded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4295) UI: The short/long description of term & category doesnt get updated immediately when made blank
[ https://issues.apache.org/jira/browse/ATLAS-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4295: --- Fix Version/s: 2.2.0 3.0.0 > UI: The short/long description of term & category doesnt get updated > immediately when made blank > > > Key: ATLAS-4295 > URL: https://issues.apache.org/jira/browse/ATLAS-4295 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4295-UI-UI-The-short-long-description-of-term-.patch > > > When one empties the the short and long description fields of term & category > and saves, > the UI doesn't get reflected immediately. But on refresh, it gets reflected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4327) UI: Deleting all glossaries and then switching to new UI results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4327: --- Fix Version/s: 2.2.0 3.0.0 > UI: Deleting all glossaries and then switching to new UI results in > unexpected behaviour > > > Key: ATLAS-4327 > URL: https://issues.apache.org/jira/browse/ATLAS-4327 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4327-1-UI-Deleting-all-glossaries-and-then-swi.patch > > > As seen in the below video url, if the user deletes all glossaries from old > UI and then switches over to new UI, the Glossary section is missing and a > endless loader animation keeps playing. > https://drive.google.com/file/d/1lXoFEGNNkC_49Zhc8Vb4rT47GT_YYPSq/view?usp=sharing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4337) Add entity icons for all the Kafka types
[ https://issues.apache.org/jira/browse/ATLAS-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4337: --- Component/s: atlas-webui > 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 > > Create Entity icons for all the Kafka types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4337) Add entity icons for all the Kafka types
[ https://issues.apache.org/jira/browse/ATLAS-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4337: --- Labels: entity-icons (was: ) > 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 > > Create Entity icons for all the Kafka types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Prasad P. Pawar updated ATLAS-4337: --- Summary: Atlas UI:Add entity icons for all the Kafka types (was: Add entity icons for all the Kafka types) > 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 > > Create Entity icons for all the Kafka types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (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=17363579#comment-17363579 ] Prasad P. Pawar edited comment on ATLAS-4337 at 6/15/21, 11:18 AM: --- Hi, Kafka types Entity icons created. was (Author: prasadpp13): Hi, Kafka types Entity icons creaded. > 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] [Created] (ATLAS-4337) Add entity icons for all the Kafka types
Prasad P. Pawar created ATLAS-4337: -- Summary: 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 Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar Create Entity icons for all the Kafka types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4326) Atlas UI: Multiple continuous space is accepted on Short description for Classifications, Gloassarys, Categorys & Terms .
[ https://issues.apache.org/jira/browse/ATLAS-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4326: --- Attachment: 0001-ATLAS-4326-2-Atlas-UI-Multiple-continuous-space-is-a.patch > Atlas UI: Multiple continuous space is accepted on Short description for > Classifications, Gloassarys, Categorys & Terms . > - > > Key: ATLAS-4326 > URL: https://issues.apache.org/jira/browse/ATLAS-4326 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4326-1-Atlas-UI-Multiple-continuous-space-is-a.patch, > 0001-ATLAS-4326-2-Atlas-UI-Multiple-continuous-space-is-a.patch > > > Add multiple continuous spaces in the short description field, this value is > accepted on UI by clicking the Save/Update button. > After updating the values, the Detail page doesn't show the entered value of > Short description files. eg: " This is Term1 " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4325) [Atlas: Glossary Term Bulk Import] [UI] Unable to perform bulk import glossary term via UI
[
https://issues.apache.org/jira/browse/ATLAS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4325:
---
Fix Version/s: 2.2.0
3.0.0
> [Atlas: Glossary Term Bulk Import] [UI] Unable to perform bulk import
> glossary term via UI
> --
>
> Key: ATLAS-4325
> URL: https://issues.apache.org/jira/browse/ATLAS-4325
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments:
> 0001-ATLAS-4325-Atlas-Glossary-Term-Bulk-Import-UI-Unable.patch, Screenshot
> 2021-06-03 at 5.41.57 PM.png
>
>
> Bulk import is failing with "\{"msgDesc":"Missing header or invalid Header
> value for CSRF Vulnerability Protection"}" !Screenshot 2021-06-03 at 5.41.57
> PM.png|width=443,height=273!
> NOTE: the same succeeds via api
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4281) Atlas UI: Tasks tab refresh button is seen on other tabs of entity detail page.
Prasad P. Pawar created ATLAS-4281: -- Summary: Atlas UI: Tasks tab refresh button is seen on other tabs of entity detail page. Key: ATLAS-4281 URL: https://issues.apache.org/jira/browse/ATLAS-4281 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar The refresh button of Tasks tab is seen at the bottom of Properties tab, Relationships tab, Classification tabs, Audit tab & schema tabs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4280: -- Attachment: 0001-ATLAS-4280-UI-Save-button-is-enabled-when-Classifica.patch Assignee: Prasad P. Pawar Labels: Atlas-UI classification (was: ) Hi, this fix is provided in the uploaded patch. > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Labels: Atlas-UI, classification > Attachments: > 0001-ATLAS-4280-UI-Save-button-is-enabled-when-Classifica.patch > > > Previously the Save button in the popup box for classification attribute > would not show as enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4280: --- Component/s: atlas-webui > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Labels: Atlas-UI, classification > Attachments: > 0001-ATLAS-4280-UI-Save-button-is-enabled-when-Classifica.patch > > > Previously the Save button in the popup box for classification attribute > would not show as enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4294) Format long description of Glossary term and category
[ https://issues.apache.org/jira/browse/ATLAS-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4294: -- Assignee: Prasad P. Pawar > 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 >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] [Assigned] (ATLAS-4283) UI: Description cannot be made blank for classification
[ https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4283: -- Assignee: Prasad P. Pawar > UI: Description cannot be made blank for classification > --- > > Key: ATLAS-4283 > URL: https://issues.apache.org/jira/browse/ATLAS-4283 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > > If there is an existing description for a classification, and if the user > attempts to update it to blank, he will not be able to do so. > The API response for when the user inputs a blank value shows that the > updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349148#comment-17349148 ] Prasad P. Pawar commented on ATLAS-4259: +1 > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil P Bonte >Priority: Major > Labels: REST_API, swagger > Attachments: ATLAS-4259-Swagger-Improve-Header-validation_v2.patch > > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4308) ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting happens on the previous sorted results received from the server
Prasad P. Pawar created ATLAS-4308: -- Summary: ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting happens on the previous sorted results received from the server Key: ATLAS-4308 URL: https://issues.apache.org/jira/browse/ATLAS-4308 Project: Atlas Issue Type: Bug Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar Attaching 2 screenshots where following was done 1)sort by action + sort by user (sort by action is done and on top of that result , sort by user is done) 2)sort by user (only sort by user is done) The results are different on UI. The query for : 1) is a) /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=action b) /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=user 2) is a) /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=user 1.b happens on the result of 1.a which is not expected. 1.b should be equal to 2.a -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4309) Atlas UI: After deleting the sub-classifications from Atlas UI, they still appear in UI.
Prasad P. Pawar created ATLAS-4309: -- Summary: Atlas UI: After deleting the sub-classifications from Atlas UI, they still appear in UI. Key: ATLAS-4309 URL: https://issues.apache.org/jira/browse/ATLAS-4309 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar - After deleting the sub-classifications from Atlas UI, they still appear super-classifications - While the sub-classification is deleted successfully and does not appear under parent classification available in flat/tree view, it does show up on the main screen for classification. - However, after refreshing the browser, the deleted sub-classification is removed from the UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4308) ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting happens on the previous sorted results received from the server
[ https://issues.apache.org/jira/browse/ATLAS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4308: --- Component/s: atlas-webui > ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting > happens on the previous sorted results received from the server > -- > > Key: ATLAS-4308 > URL: https://issues.apache.org/jira/browse/ATLAS-4308 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: Atlas-UI, audits > > Attaching 2 screenshots where following was done > > 1)sort by action + sort by user (sort by action is done and on top of that > result , sort by user is done) > 2)sort by user (only sort by user is done) > > The results are different on UI. > > The query for : > 1) is > a) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=action > > b) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=user > > 2) is > a) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=user > > 1.b happens on the result of 1.a which is not expected. > > 1.b should be equal to 2.a -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4308) ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting happens on the previous sorted results received from the server
[ https://issues.apache.org/jira/browse/ATLAS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4308: --- Labels: Atlas-UI audits (was: audits) > ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting > happens on the previous sorted results received from the server > -- > > Key: ATLAS-4308 > URL: https://issues.apache.org/jira/browse/ATLAS-4308 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: Atlas-UI, audits > > Attaching 2 screenshots where following was done > > 1)sort by action + sort by user (sort by action is done and on top of that > result , sort by user is done) > 2)sort by user (only sort by user is done) > > The results are different on UI. > > The query for : > 1) is > a) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=action > > b) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=user > > 2) is > a) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=user > > 1.b happens on the result of 1.a which is not expected. > > 1.b should be equal to 2.a -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4299) [Atlas: Debug Metrics] Several UI Issues are seen when the total count crossed 25
[
https://issues.apache.org/jira/browse/ATLAS-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4299:
---
Fix Version/s: 2.2.0
> [Atlas: Debug Metrics] Several UI Issues are seen when the total count
> crossed 25
> -
>
> Key: ATLAS-4299
> URL: https://issues.apache.org/jira/browse/ATLAS-4299
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch, Screenshot
> 2021-05-24 at 4.13.08 PM.png, Screenshot 2021-05-24 at 4.40.15 PM.png
>
>
> A list of UI issues are seen when the total issues crosses 25
> # The total number of data as per response is 29, but UI says 30
> # The data displayed are only 29 but one of them is a blank entry
> (Highlighted in screenshot)
> # Among the 29 entries present in api response, one of them is missing in
> the UI in this case [*TypesREST_getTypeDefHeaders*]
> # When all the data are made to display in same page, the UI shows page 1
> and 2
> # When the selection is made to display only 25, it still displays all the
> data [25+ entries are displayed]
> # Sorting does not work without refresh
> Response Data:
> {code:java}
> {
> "TypesREST_getTypeDefHeaders": {
> "name": "TypesREST_getTypeDefHeaders",
> "numops": 13,
> "minTime": 2,
> "maxTime": 37,
> "stdDevTime": 0,
> "avgTime": 2
> },
> "GlossaryREST_createGlossaryTerm": {
> "name": "GlossaryREST_createGlossaryTerm",
> "numops": 11,
> "minTime": 218,
> "maxTime": 308,
> "stdDevTime": 29.160475,
> "avgTime": 235.3
> },
> "GlossaryREST_deleteGlossaryCategory": {
> "name": "GlossaryREST_deleteGlossaryCategory",
> "numops": 2,
> "minTime": 197,
> "maxTime": 219,
> "stdDevTime": 0,
> "avgTime": 197
> },
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 3,
> "minTime": 165,
> "maxTime": 521,
> "stdDevTime": 251.73001,
> "avgTime": 343
> },
> "EntityREST_addClassifications": {
> "name": "EntityREST_addClassifications",
> "numops": 339,
> "minTime": 64,
> "maxTime": 430,
> "stdDevTime": 2.5495098,
> "avgTime": 101.5
> },
> "DiscoveryREST_getSavedSearches": {
> "name": "DiscoveryREST_getSavedSearches",
> "numops": 13,
> "minTime": 3,
> "maxTime": 38,
> "stdDevTime": 0,
> "avgTime": 3
> },
> "TypesREST_getClassificationDefByName": {
> "name": "TypesREST_getClassificationDefByName",
> "numops": 11,
> "minTime": 2,
> "maxTime": 2,
> "stdDevTime": 0,
> "avgTime": 1
> },
> "GlossaryREST_createGlossary": {
> "name": "GlossaryREST_createGlossary",
> "numops": 4,
> "minTime": 167,
> "maxTime": 197,
> "stdDevTime": 0,
> "avgTime": 179
> },
> "EntityREST_createOrUpdate": {
> "name": "EntityREST_createOrUpdate",
> "numops": 2,
> "minTime": 76,
> "maxTime": 133,
> "stdDevTime": 40.305088,
> "avgTime": 104.5
> },
> "GlossaryREST_getGlossaryCategory": {
> "name": "GlossaryREST_getGlossaryCategory",
> "numops": 14,
> "minTime": 5,
> "maxTime": 47,
> "stdDevTime": 18.384777,
> "avgTime": 25
> },
> "GlossaryREST_updateGlossaryTerm": {
> "name": "GlossaryREST_updateGlossaryTerm",
> "numops": 5,
> "minTime": 62,
> "maxTime": 559,
> "stdDevTime": 340.11835,
> "avgTime": 62
> },
> "DiscoveryREST_searchUsingBasic": {
> "name": "DiscoveryREST_searchUsingBasic",
> "numops": 2,
> "minTime": 25,
> "maxTime": 451,
> "stdDevTime": 0,
> "avgTime": 25
> },
> "EntityREST_getById": {
> "name": "EntityREST_getById",
> "numops": 5,
> "minTime": 37,
> "maxTime": 84,
> "stdDevTime": 20.067387,
> "avgTime": 52.8
> },
> "GlossaryREST_getGlossaries": {
> "name": "GlossaryREST_getGlossaries",
> "numops": 34,
> "minTime": 10,
> "maxTime": 291,
> "stdDevTime": 48.294235,
> "avgTime": 180
> },
> "TypesREST_getAllTypeDefs": {
> "name": "TypesREST_getAllTypeDefs",
> "numops": 44,
> "minTime": 0,
> "maxTime": 32,
> "stdDevTime": 0.5,
> "avgTime": 0.25
> },
> "DiscoveryREST_searchUsingDSL": {
> "name": "DiscoveryREST_searchUsingDSL",
> "numops": 4,
> "minTime": 13,
> "maxTime": 243,
> "stdDevTime": 155.56349,
> "avgTime": 16
> },
> "GlossaryREST_createGlossaryCategory": {
> "name": "GlossaryREST_createGlossaryCategory",
> "numops": 4,
> "minTime": 195,
> "maxTime": 293,
>
[jira] [Updated] (ATLAS-4299) [Atlas: Debug Metrics] Several UI Issues are seen when the total count crossed 25
[
https://issues.apache.org/jira/browse/ATLAS-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4299:
---
Fix Version/s: 3.0.0
> [Atlas: Debug Metrics] Several UI Issues are seen when the total count
> crossed 25
> -
>
> Key: ATLAS-4299
> URL: https://issues.apache.org/jira/browse/ATLAS-4299
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch, Screenshot
> 2021-05-24 at 4.13.08 PM.png, Screenshot 2021-05-24 at 4.40.15 PM.png
>
>
> A list of UI issues are seen when the total issues crosses 25
> # The total number of data as per response is 29, but UI says 30
> # The data displayed are only 29 but one of them is a blank entry
> (Highlighted in screenshot)
> # Among the 29 entries present in api response, one of them is missing in
> the UI in this case [*TypesREST_getTypeDefHeaders*]
> # When all the data are made to display in same page, the UI shows page 1
> and 2
> # When the selection is made to display only 25, it still displays all the
> data [25+ entries are displayed]
> # Sorting does not work without refresh
> Response Data:
> {code:java}
> {
> "TypesREST_getTypeDefHeaders": {
> "name": "TypesREST_getTypeDefHeaders",
> "numops": 13,
> "minTime": 2,
> "maxTime": 37,
> "stdDevTime": 0,
> "avgTime": 2
> },
> "GlossaryREST_createGlossaryTerm": {
> "name": "GlossaryREST_createGlossaryTerm",
> "numops": 11,
> "minTime": 218,
> "maxTime": 308,
> "stdDevTime": 29.160475,
> "avgTime": 235.3
> },
> "GlossaryREST_deleteGlossaryCategory": {
> "name": "GlossaryREST_deleteGlossaryCategory",
> "numops": 2,
> "minTime": 197,
> "maxTime": 219,
> "stdDevTime": 0,
> "avgTime": 197
> },
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 3,
> "minTime": 165,
> "maxTime": 521,
> "stdDevTime": 251.73001,
> "avgTime": 343
> },
> "EntityREST_addClassifications": {
> "name": "EntityREST_addClassifications",
> "numops": 339,
> "minTime": 64,
> "maxTime": 430,
> "stdDevTime": 2.5495098,
> "avgTime": 101.5
> },
> "DiscoveryREST_getSavedSearches": {
> "name": "DiscoveryREST_getSavedSearches",
> "numops": 13,
> "minTime": 3,
> "maxTime": 38,
> "stdDevTime": 0,
> "avgTime": 3
> },
> "TypesREST_getClassificationDefByName": {
> "name": "TypesREST_getClassificationDefByName",
> "numops": 11,
> "minTime": 2,
> "maxTime": 2,
> "stdDevTime": 0,
> "avgTime": 1
> },
> "GlossaryREST_createGlossary": {
> "name": "GlossaryREST_createGlossary",
> "numops": 4,
> "minTime": 167,
> "maxTime": 197,
> "stdDevTime": 0,
> "avgTime": 179
> },
> "EntityREST_createOrUpdate": {
> "name": "EntityREST_createOrUpdate",
> "numops": 2,
> "minTime": 76,
> "maxTime": 133,
> "stdDevTime": 40.305088,
> "avgTime": 104.5
> },
> "GlossaryREST_getGlossaryCategory": {
> "name": "GlossaryREST_getGlossaryCategory",
> "numops": 14,
> "minTime": 5,
> "maxTime": 47,
> "stdDevTime": 18.384777,
> "avgTime": 25
> },
> "GlossaryREST_updateGlossaryTerm": {
> "name": "GlossaryREST_updateGlossaryTerm",
> "numops": 5,
> "minTime": 62,
> "maxTime": 559,
> "stdDevTime": 340.11835,
> "avgTime": 62
> },
> "DiscoveryREST_searchUsingBasic": {
> "name": "DiscoveryREST_searchUsingBasic",
> "numops": 2,
> "minTime": 25,
> "maxTime": 451,
> "stdDevTime": 0,
> "avgTime": 25
> },
> "EntityREST_getById": {
> "name": "EntityREST_getById",
> "numops": 5,
> "minTime": 37,
> "maxTime": 84,
> "stdDevTime": 20.067387,
> "avgTime": 52.8
> },
> "GlossaryREST_getGlossaries": {
> "name": "GlossaryREST_getGlossaries",
> "numops": 34,
> "minTime": 10,
> "maxTime": 291,
> "stdDevTime": 48.294235,
> "avgTime": 180
> },
> "TypesREST_getAllTypeDefs": {
> "name": "TypesREST_getAllTypeDefs",
> "numops": 44,
> "minTime": 0,
> "maxTime": 32,
> "stdDevTime": 0.5,
> "avgTime": 0.25
> },
> "DiscoveryREST_searchUsingDSL": {
> "name": "DiscoveryREST_searchUsingDSL",
> "numops": 4,
> "minTime": 13,
> "maxTime": 243,
> "stdDevTime": 155.56349,
> "avgTime": 16
> },
> "GlossaryREST_createGlossaryCategory": {
> "name": "GlossaryREST_createGlossaryCategory",
> "numops": 4,
> "minTime": 195,
> "maxTime": 293,
> "stdDevTime": 0,
>
[jira] [Updated] (ATLAS-4298) [Atlas: Debug Metrics][UI] When REST API Metric page has more than 25 entries, the page does not load unless manually refreshed
[
https://issues.apache.org/jira/browse/ATLAS-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4298:
---
Fix Version/s: 2.2.0
3.0.0
> [Atlas: Debug Metrics][UI] When REST API Metric page has more than 25
> entries, the page does not load unless manually refreshed
> ---
>
> Key: ATLAS-4298
> URL: https://issues.apache.org/jira/browse/ATLAS-4298
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch
>
>
> When debug metrics is enabled by setting *atlas.debug.metrics.enabled=true*
> Debug metrics url page: :31443/index.html#!/debugMetrics displays the
> REST API Metrics.
> When the result page entry count crosses 25, the page does not load, unless
> refresh button is hit
> There are no error logs found in the cluster but console displays the
> following
> {code:java}
> backbone.paginator.min.js?bust=1621440039818:1
> Uncaught TypeError: Cannot read property 'add' of undefined
> at e (backbone.paginator.min.js?bust=1621440039818:1)
> at Object. (backbone.paginator.min.js?bust=1621440039818:1)
> at s (backbone-min.js?bust=1621440039818:1)
> at r (backbone-min.js?bust=1621440039818:1)
> at m (backbone-min.js?bust=1621440039818:1)
> at N.d.k.trigger (backbone-min.js?bust=1621440039818:1)
> at N.d._onModelEvent (backbone-min.js?bust=1621440039818:1)
> at s (backbone-min.js?bust=1621440039818:1)
> at r (backbone-min.js?bust=1621440039818:1)
> at m (backbone-min.js?bust=1621440039818:1){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4308) ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting happens on the previous sorted results received from the server
[ https://issues.apache.org/jira/browse/ATLAS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4308: --- Fix Version/s: 2.2.0 3.0.0 > ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting > happens on the previous sorted results received from the server > -- > > Key: ATLAS-4308 > URL: https://issues.apache.org/jira/browse/ATLAS-4308 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: Atlas-UI, audits > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4308-ATLAS-UI-Audit-sorting-When-consecutive-E.patch > > > Attaching 2 screenshots where following was done > > 1)sort by action + sort by user (sort by action is done and on top of that > result , sort by user is done) > 2)sort by user (only sort by user is done) > > The results are different on UI. > > The query for : > 1) is > a) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=action > > b) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=user > > 2) is > a) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc=0=25=user > > 1.b happens on the result of 1.a which is not expected. > > 1.b should be equal to 2.a -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4316) UI : When lineage contains shell entities, the image couldn't be downloaded.
Prasad P. Pawar created ATLAS-4316: -- Summary: UI : When lineage contains shell entities, the image couldn't be downloaded. Key: ATLAS-4316 URL: https://issues.apache.org/jira/browse/ATLAS-4316 Project: Atlas Issue Type: Bug Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar Added a screen recording where the lineage contains shell entities so the image is not downloaded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4325) [Atlas: Glossary Term Bulk Import] [UI] Unable to perform bulk import glossary term via UI
[
https://issues.apache.org/jira/browse/ATLAS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar reassigned ATLAS-4325:
--
Assignee: Prasad P. Pawar
> [Atlas: Glossary Term Bulk Import] [UI] Unable to perform bulk import
> glossary term via UI
> --
>
> Key: ATLAS-4325
> URL: https://issues.apache.org/jira/browse/ATLAS-4325
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments: Screenshot 2021-06-03 at 5.41.57 PM.png
>
>
> Bulk import is failing with "\{"msgDesc":"Missing header or invalid Header
> value for CSRF Vulnerability Protection"}" !Screenshot 2021-06-03 at 5.41.57
> PM.png|width=443,height=273!
> NOTE: the same succeeds via api
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4326) Atlas UI: Multiple continuous space is accepted on Short description for Classifications, Gloassarys, Categorys & Terms .
Prasad P. Pawar created ATLAS-4326: -- Summary: Atlas UI: Multiple continuous space is accepted on Short description for Classifications, Gloassarys, Categorys & Terms . Key: ATLAS-4326 URL: https://issues.apache.org/jira/browse/ATLAS-4326 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar Add multiple continuous spaces in the short description field, this value is accepted on UI by clicking the Save/Update button. After updating the values, the Detail page doesn't show the entered value of Short description files. eg: " This is Term1 " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4295) UI: The short/long description of term & category doesnt get updated immediately when made blank
[ https://issues.apache.org/jira/browse/ATLAS-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4295: -- Assignee: Prasad P. Pawar > UI: The short/long description of term & category doesnt get updated > immediately when made blank > > > Key: ATLAS-4295 > URL: https://issues.apache.org/jira/browse/ATLAS-4295 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > > When one empties the the short and long description fields of term & category > and saves, > the UI doesn't get reflected immediately. But on refresh, it gets reflected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4327) UI: Deleting all glossaries and then switching to new UI results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4327: -- Assignee: Prasad P. Pawar > UI: Deleting all glossaries and then switching to new UI results in > unexpected behaviour > > > Key: ATLAS-4327 > URL: https://issues.apache.org/jira/browse/ATLAS-4327 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > > As seen in the below video url, if the user deletes all glossaries from old > UI and then switches over to new UI, the Glossary section is missing and a > endless loader animation keeps playing. > [[^glossary_import_delete_new_ui.webm]|https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4298) [Atlas: Debug Metrics][UI] When REST API Metric page has more than 25 entries, the page does not load unless manually refreshed
[
https://issues.apache.org/jira/browse/ATLAS-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar reassigned ATLAS-4298:
--
Assignee: Prasad P. Pawar
> [Atlas: Debug Metrics][UI] When REST API Metric page has more than 25
> entries, the page does not load unless manually refreshed
> ---
>
> Key: ATLAS-4298
> URL: https://issues.apache.org/jira/browse/ATLAS-4298
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch
>
>
> When debug metrics is enabled by setting *atlas.debug.metrics.enabled=true*
> Debug metrics url page: :31443/index.html#!/debugMetrics displays the
> REST API Metrics.
> When the result page entry count crosses 25, the page does not load, unless
> refresh button is hit
> There are no error logs found in the cluster but console displays the
> following
> {code:java}
> backbone.paginator.min.js?bust=1621440039818:1
> Uncaught TypeError: Cannot read property 'add' of undefined
> at e (backbone.paginator.min.js?bust=1621440039818:1)
> at Object. (backbone.paginator.min.js?bust=1621440039818:1)
> at s (backbone-min.js?bust=1621440039818:1)
> at r (backbone-min.js?bust=1621440039818:1)
> at m (backbone-min.js?bust=1621440039818:1)
> at N.d.k.trigger (backbone-min.js?bust=1621440039818:1)
> at N.d._onModelEvent (backbone-min.js?bust=1621440039818:1)
> at s (backbone-min.js?bust=1621440039818:1)
> at r (backbone-min.js?bust=1621440039818:1)
> at m (backbone-min.js?bust=1621440039818:1){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4299) [Atlas: Debug Metrics] Several UI Issues are seen when the total count crossed 25
[
https://issues.apache.org/jira/browse/ATLAS-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar reassigned ATLAS-4299:
--
Assignee: Prasad P. Pawar
> [Atlas: Debug Metrics] Several UI Issues are seen when the total count
> crossed 25
> -
>
> Key: ATLAS-4299
> URL: https://issues.apache.org/jira/browse/ATLAS-4299
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch, Screenshot
> 2021-05-24 at 4.13.08 PM.png, Screenshot 2021-05-24 at 4.40.15 PM.png
>
>
> A list of UI issues are seen when the total issues crosses 25
> # The total number of data as per response is 29, but UI says 30
> # The data displayed are only 29 but one of them is a blank entry
> (Highlighted in screenshot)
> # Among the 29 entries present in api response, one of them is missing in
> the UI in this case [*TypesREST_getTypeDefHeaders*]
> # When all the data are made to display in same page, the UI shows page 1
> and 2
> # When the selection is made to display only 25, it still displays all the
> data [25+ entries are displayed]
> # Sorting does not work without refresh
> Response Data:
> {code:java}
> {
> "TypesREST_getTypeDefHeaders": {
> "name": "TypesREST_getTypeDefHeaders",
> "numops": 13,
> "minTime": 2,
> "maxTime": 37,
> "stdDevTime": 0,
> "avgTime": 2
> },
> "GlossaryREST_createGlossaryTerm": {
> "name": "GlossaryREST_createGlossaryTerm",
> "numops": 11,
> "minTime": 218,
> "maxTime": 308,
> "stdDevTime": 29.160475,
> "avgTime": 235.3
> },
> "GlossaryREST_deleteGlossaryCategory": {
> "name": "GlossaryREST_deleteGlossaryCategory",
> "numops": 2,
> "minTime": 197,
> "maxTime": 219,
> "stdDevTime": 0,
> "avgTime": 197
> },
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 3,
> "minTime": 165,
> "maxTime": 521,
> "stdDevTime": 251.73001,
> "avgTime": 343
> },
> "EntityREST_addClassifications": {
> "name": "EntityREST_addClassifications",
> "numops": 339,
> "minTime": 64,
> "maxTime": 430,
> "stdDevTime": 2.5495098,
> "avgTime": 101.5
> },
> "DiscoveryREST_getSavedSearches": {
> "name": "DiscoveryREST_getSavedSearches",
> "numops": 13,
> "minTime": 3,
> "maxTime": 38,
> "stdDevTime": 0,
> "avgTime": 3
> },
> "TypesREST_getClassificationDefByName": {
> "name": "TypesREST_getClassificationDefByName",
> "numops": 11,
> "minTime": 2,
> "maxTime": 2,
> "stdDevTime": 0,
> "avgTime": 1
> },
> "GlossaryREST_createGlossary": {
> "name": "GlossaryREST_createGlossary",
> "numops": 4,
> "minTime": 167,
> "maxTime": 197,
> "stdDevTime": 0,
> "avgTime": 179
> },
> "EntityREST_createOrUpdate": {
> "name": "EntityREST_createOrUpdate",
> "numops": 2,
> "minTime": 76,
> "maxTime": 133,
> "stdDevTime": 40.305088,
> "avgTime": 104.5
> },
> "GlossaryREST_getGlossaryCategory": {
> "name": "GlossaryREST_getGlossaryCategory",
> "numops": 14,
> "minTime": 5,
> "maxTime": 47,
> "stdDevTime": 18.384777,
> "avgTime": 25
> },
> "GlossaryREST_updateGlossaryTerm": {
> "name": "GlossaryREST_updateGlossaryTerm",
> "numops": 5,
> "minTime": 62,
> "maxTime": 559,
> "stdDevTime": 340.11835,
> "avgTime": 62
> },
> "DiscoveryREST_searchUsingBasic": {
> "name": "DiscoveryREST_searchUsingBasic",
> "numops": 2,
> "minTime": 25,
> "maxTime": 451,
> "stdDevTime": 0,
> "avgTime": 25
> },
> "EntityREST_getById": {
> "name": "EntityREST_getById",
> "numops": 5,
> "minTime": 37,
> "maxTime": 84,
> "stdDevTime": 20.067387,
> "avgTime": 52.8
> },
> "GlossaryREST_getGlossaries": {
> "name": "GlossaryREST_getGlossaries",
> "numops": 34,
> "minTime": 10,
> "maxTime": 291,
> "stdDevTime": 48.294235,
> "avgTime": 180
> },
> "TypesREST_getAllTypeDefs": {
> "name": "TypesREST_getAllTypeDefs",
> "numops": 44,
> "minTime": 0,
> "maxTime": 32,
> "stdDevTime": 0.5,
> "avgTime": 0.25
> },
> "DiscoveryREST_searchUsingDSL": {
> "name": "DiscoveryREST_searchUsingDSL",
> "numops": 4,
> "minTime": 13,
> "maxTime": 243,
> "stdDevTime": 155.56349,
> "avgTime": 16
> },
> "GlossaryREST_createGlossaryCategory": {
> "name": "GlossaryREST_createGlossaryCategory",
> "numops": 4,
> "minTime": 195,
> "maxTime": 293,
> "stdDevTime": 0,
> "avgTime": 293
[jira] [Commented] (ATLAS-4298) [Atlas: Debug Metrics][UI] When REST API Metric page has more than 25 entries, the page does not load unless manually refreshed
[
https://issues.apache.org/jira/browse/ATLAS-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351290#comment-17351290
]
Prasad P. Pawar commented on ATLAS-4298:
Hi,
the fix is provided on the uploaded patch.
> [Atlas: Debug Metrics][UI] When REST API Metric page has more than 25
> entries, the page does not load unless manually refreshed
> ---
>
> Key: ATLAS-4298
> URL: https://issues.apache.org/jira/browse/ATLAS-4298
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch
>
>
> When debug metrics is enabled by setting *atlas.debug.metrics.enabled=true*
> Debug metrics url page: :31443/index.html#!/debugMetrics displays the
> REST API Metrics.
> When the result page entry count crosses 25, the page does not load, unless
> refresh button is hit
> There are no error logs found in the cluster but console displays the
> following
> {code:java}
> backbone.paginator.min.js?bust=1621440039818:1
> Uncaught TypeError: Cannot read property 'add' of undefined
> at e (backbone.paginator.min.js?bust=1621440039818:1)
> at Object. (backbone.paginator.min.js?bust=1621440039818:1)
> at s (backbone-min.js?bust=1621440039818:1)
> at r (backbone-min.js?bust=1621440039818:1)
> at m (backbone-min.js?bust=1621440039818:1)
> at N.d.k.trigger (backbone-min.js?bust=1621440039818:1)
> at N.d._onModelEvent (backbone-min.js?bust=1621440039818:1)
> at s (backbone-min.js?bust=1621440039818:1)
> at r (backbone-min.js?bust=1621440039818:1)
> at m (backbone-min.js?bust=1621440039818:1){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4296) [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not matching the api response values
[
https://issues.apache.org/jira/browse/ATLAS-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351289#comment-17351289
]
Prasad P. Pawar commented on ATLAS-4296:
Hi,
the fix is provided on the uploaded patch.
> [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not
> matching the api response values
> --
>
> Key: ATLAS-4296
> URL: https://issues.apache.org/jira/browse/ATLAS-4296
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch,
> ATLAS-4296-1.patch, Screenshot 2021-05-21 at 4.18.34 PM.png, Screenshot
> 2021-05-21 at 4.18.34 PM.png
>
>
> Scenario: Enable debug Metrics
> !Screenshot 2021-05-21 at 4.18.34 PM.png|width=646,height=322!
> Eg: Consider the above highlighted example. *GlossaryREST_deleteGlossary*
> Here
> Min Time : 1.920 (seconds)
> Max Time : 5.530 (seconds) and
> Average Time : 5.530 (seconds)
> *Api response:*
> {code:java}
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 6,
> "minTime": 192,
> "maxTime": 553,
> "stdDevTime": 21.556128,
> "avgTime": 532
> } {code}
>
> 1.92 (seconds) has to be 1920 if the value is response is stored in
> milliseconds but it appears as 192
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4296) [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not matching the api response values
[
https://issues.apache.org/jira/browse/ATLAS-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4296:
---
Attachment: 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch
> [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not
> matching the api response values
> --
>
> Key: ATLAS-4296
> URL: https://issues.apache.org/jira/browse/ATLAS-4296
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch,
> ATLAS-4296-1.patch, Screenshot 2021-05-21 at 4.18.34 PM.png, Screenshot
> 2021-05-21 at 4.18.34 PM.png
>
>
> Scenario: Enable debug Metrics
> !Screenshot 2021-05-21 at 4.18.34 PM.png|width=646,height=322!
> Eg: Consider the above highlighted example. *GlossaryREST_deleteGlossary*
> Here
> Min Time : 1.920 (seconds)
> Max Time : 5.530 (seconds) and
> Average Time : 5.530 (seconds)
> *Api response:*
> {code:java}
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 6,
> "minTime": 192,
> "maxTime": 553,
> "stdDevTime": 21.556128,
> "avgTime": 532
> } {code}
>
> 1.92 (seconds) has to be 1920 if the value is response is stored in
> milliseconds but it appears as 192
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4299) [Atlas: Debug Metrics] Several UI Issues are seen when the total count crossed 25
[
https://issues.apache.org/jira/browse/ATLAS-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351291#comment-17351291
]
Prasad P. Pawar commented on ATLAS-4299:
Hi,
the fix is provided on the uploaded patch.
> [Atlas: Debug Metrics] Several UI Issues are seen when the total count
> crossed 25
> -
>
> Key: ATLAS-4299
> URL: https://issues.apache.org/jira/browse/ATLAS-4299
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch, Screenshot
> 2021-05-24 at 4.13.08 PM.png, Screenshot 2021-05-24 at 4.40.15 PM.png
>
>
> A list of UI issues are seen when the total issues crosses 25
> # The total number of data as per response is 29, but UI says 30
> # The data displayed are only 29 but one of them is a blank entry
> (Highlighted in screenshot)
> # Among the 29 entries present in api response, one of them is missing in
> the UI in this case [*TypesREST_getTypeDefHeaders*]
> # When all the data are made to display in same page, the UI shows page 1
> and 2
> # When the selection is made to display only 25, it still displays all the
> data [25+ entries are displayed]
> # Sorting does not work without refresh
> Response Data:
> {code:java}
> {
> "TypesREST_getTypeDefHeaders": {
> "name": "TypesREST_getTypeDefHeaders",
> "numops": 13,
> "minTime": 2,
> "maxTime": 37,
> "stdDevTime": 0,
> "avgTime": 2
> },
> "GlossaryREST_createGlossaryTerm": {
> "name": "GlossaryREST_createGlossaryTerm",
> "numops": 11,
> "minTime": 218,
> "maxTime": 308,
> "stdDevTime": 29.160475,
> "avgTime": 235.3
> },
> "GlossaryREST_deleteGlossaryCategory": {
> "name": "GlossaryREST_deleteGlossaryCategory",
> "numops": 2,
> "minTime": 197,
> "maxTime": 219,
> "stdDevTime": 0,
> "avgTime": 197
> },
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 3,
> "minTime": 165,
> "maxTime": 521,
> "stdDevTime": 251.73001,
> "avgTime": 343
> },
> "EntityREST_addClassifications": {
> "name": "EntityREST_addClassifications",
> "numops": 339,
> "minTime": 64,
> "maxTime": 430,
> "stdDevTime": 2.5495098,
> "avgTime": 101.5
> },
> "DiscoveryREST_getSavedSearches": {
> "name": "DiscoveryREST_getSavedSearches",
> "numops": 13,
> "minTime": 3,
> "maxTime": 38,
> "stdDevTime": 0,
> "avgTime": 3
> },
> "TypesREST_getClassificationDefByName": {
> "name": "TypesREST_getClassificationDefByName",
> "numops": 11,
> "minTime": 2,
> "maxTime": 2,
> "stdDevTime": 0,
> "avgTime": 1
> },
> "GlossaryREST_createGlossary": {
> "name": "GlossaryREST_createGlossary",
> "numops": 4,
> "minTime": 167,
> "maxTime": 197,
> "stdDevTime": 0,
> "avgTime": 179
> },
> "EntityREST_createOrUpdate": {
> "name": "EntityREST_createOrUpdate",
> "numops": 2,
> "minTime": 76,
> "maxTime": 133,
> "stdDevTime": 40.305088,
> "avgTime": 104.5
> },
> "GlossaryREST_getGlossaryCategory": {
> "name": "GlossaryREST_getGlossaryCategory",
> "numops": 14,
> "minTime": 5,
> "maxTime": 47,
> "stdDevTime": 18.384777,
> "avgTime": 25
> },
> "GlossaryREST_updateGlossaryTerm": {
> "name": "GlossaryREST_updateGlossaryTerm",
> "numops": 5,
> "minTime": 62,
> "maxTime": 559,
> "stdDevTime": 340.11835,
> "avgTime": 62
> },
> "DiscoveryREST_searchUsingBasic": {
> "name": "DiscoveryREST_searchUsingBasic",
> "numops": 2,
> "minTime": 25,
> "maxTime": 451,
> "stdDevTime": 0,
> "avgTime": 25
> },
> "EntityREST_getById": {
> "name": "EntityREST_getById",
> "numops": 5,
> "minTime": 37,
> "maxTime": 84,
> "stdDevTime": 20.067387,
> "avgTime": 52.8
> },
> "GlossaryREST_getGlossaries": {
> "name": "GlossaryREST_getGlossaries",
> "numops": 34,
> "minTime": 10,
> "maxTime": 291,
> "stdDevTime": 48.294235,
> "avgTime": 180
> },
> "TypesREST_getAllTypeDefs": {
> "name": "TypesREST_getAllTypeDefs",
> "numops": 44,
> "minTime": 0,
> "maxTime": 32,
> "stdDevTime": 0.5,
> "avgTime": 0.25
> },
> "DiscoveryREST_searchUsingDSL": {
> "name": "DiscoveryREST_searchUsingDSL",
> "numops": 4,
> "minTime": 13,
> "maxTime": 243,
> "stdDevTime": 155.56349,
> "avgTime": 16
> },
> "GlossaryREST_createGlossaryCategory": {
> "name": "GlossaryREST_createGlossaryCategory",
> "numops": 4,
> "minTime": 195,
>
[jira] [Assigned] (ATLAS-4304) [Business Metadata Bulk Import] [Beta UI] Bulk Import Business Metadata/Glossary options overlap
[ https://issues.apache.org/jira/browse/ATLAS-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4304: -- Assignee: Prasad P. Pawar > [Business Metadata Bulk Import] [Beta UI] Bulk Import Business > Metadata/Glossary options overlap > > > Key: ATLAS-4304 > URL: https://issues.apache.org/jira/browse/ATLAS-4304 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: Screenshot 2021-05-24 at 11.31.32 PM.png, Screenshot > 2021-05-24 at 11.31.48 PM.png > > > As seen in the screenshot below, the sub drop downs overlap and the Business > Metadata/Glossary in almost 50% hidden > !Screenshot 2021-05-24 at 11.31.32 PM.png! > !Screenshot 2021-05-24 at 11.31.48 PM.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4314) Atlas UI: Make Tasks tab default as hidden on entity detail page.
[ https://issues.apache.org/jira/browse/ATLAS-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4314: -- Assignee: Prasad P. Pawar > Atlas UI: Make Tasks tab default as hidden on entity detail page. > -- > > Key: ATLAS-4314 > URL: https://issues.apache.org/jira/browse/ATLAS-4314 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > > Task Tab is seen on the Entity detail page when session API doesn't have > atlas.tasks.enabled value. Tab should not be shown on Entity detail page UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4314) Atlas UI: Make Tasks tab default as hidden on entity detail page.
[ https://issues.apache.org/jira/browse/ATLAS-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4314: --- Labels: Atlas-UI (was: ) > Atlas UI: Make Tasks tab default as hidden on entity detail page. > -- > > Key: ATLAS-4314 > URL: https://issues.apache.org/jira/browse/ATLAS-4314 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: Atlas-UI > > Task Tab is seen on the Entity detail page when session API doesn't have > atlas.tasks.enabled value. Tab should not be shown on Entity detail page UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4314) Atlas UI: Make Tasks tab default as hidden on entity detail page.
Prasad P. Pawar created ATLAS-4314: -- Summary: Atlas UI: Make Tasks tab default as hidden on entity detail page. Key: ATLAS-4314 URL: https://issues.apache.org/jira/browse/ATLAS-4314 Project: Atlas Issue Type: Bug Reporter: Prasad P. Pawar Task Tab is seen on the Entity detail page when session API doesn't have atlas.tasks.enabled value. Tab should not be shown on Entity detail page UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4316) UI : When lineage contains shell entities, the image couldn't be downloaded.
[ https://issues.apache.org/jira/browse/ATLAS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355119#comment-17355119 ] Prasad P. Pawar commented on ATLAS-4316: Hi, this issue is only been seen on chrome > UI : When lineage contains shell entities, the image couldn't be downloaded. > > > Key: ATLAS-4316 > URL: https://issues.apache.org/jira/browse/ATLAS-4316 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > > Added a screen recording where the lineage contains shell entities so the > image is not downloaded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4345) UI: Lineage issues for when entities are greater than 9k in a given lineagee.
[ https://issues.apache.org/jira/browse/ATLAS-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4345: --- Summary: UI: Lineage issues for when entities are greater than 9k in a given lineagee. (was: UI: Lineage issues for when entities are greater than 9k in a given lineage.) > UI: Lineage issues for when entities are greater than 9k in a given lineagee. > - > > Key: ATLAS-4345 > URL: https://issues.apache.org/jira/browse/ATLAS-4345 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > > There are two issues that emerge when there are more than 9k entities in a > given lineage: > > # It doesn't display all the entities in the given page, but there is no > message saying why. > # When I attempt to download image, it does nothing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4345) UI: Lineage issues for when entities are greater than 9k in a given lineage.
[ https://issues.apache.org/jira/browse/ATLAS-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4345: --- Summary: UI: Lineage issues for when entities are greater than 9k in a given lineage. (was: UI: Lineage issues for when entities are greater than 9k in a given lineagee.) > UI: Lineage issues for when entities are greater than 9k in a given lineage. > > > Key: ATLAS-4345 > URL: https://issues.apache.org/jira/browse/ATLAS-4345 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > > There are two issues that emerge when there are more than 9k entities in a > given lineage: > > # It doesn't display all the entities in the given page, but there is no > message saying why. > # When I attempt to download image, it does nothing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4345) UI: Lineage issues for when entities are greater than 9k in a given lineage.
[ https://issues.apache.org/jira/browse/ATLAS-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4345: -- Assignee: Prasad P. Pawar > UI: Lineage issues for when entities are greater than 9k in a given lineage. > > > Key: ATLAS-4345 > URL: https://issues.apache.org/jira/browse/ATLAS-4345 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > > There are two issues that emerge when there are more than 9k entities in a > given lineage: > > # It doesn't display all the entities in the given page, but there is no > message saying why. > # When I attempt to download image, it does nothing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4243) UI: Legend in lineage gets duplicated
[ https://issues.apache.org/jira/browse/ATLAS-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17332983#comment-17332983 ] Prasad P. Pawar commented on ATLAS-4243: Hi, This fix is provided in the uploaded patch. > UI: Legend in lineage gets duplicated > - > > Key: ATLAS-4243 > URL: https://issues.apache.org/jira/browse/ATLAS-4243 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4243-UI-Legend-in-lineage-gets-duplicated-fixe.patch, > image-2021-04-14-10-21-12-123.png > > > The legend of the lineage gets duplicated whenever a value is selected from > the depth field in filters. > > !image-2021-04-14-10-21-12-123.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4270) Deferred Actions : Add a notification about task running in the background
[ https://issues.apache.org/jira/browse/ATLAS-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337287#comment-17337287 ] Prasad P. Pawar commented on ATLAS-4270: Hi, the fix is provided in the uploaded patch > Deferred Actions : Add a notification about task running in the background > -- > > Key: ATLAS-4270 > URL: https://issues.apache.org/jira/browse/ATLAS-4270 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: deferred-actions > Attachments: > 0001-ATLAS-4270-Deferred-Actions-Add-a-notification-about.patch > > > On UI, the Association of tags happens very fast and the propagation goes in > the background as deferred action. Users might get confused as to why the > tags are not propagated yet. it would be good to add a notification or a > popup saying the propagation is yet to complete. > Create a Tasks tabs on the Entity Detail page, which shows the deferred task. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4270) Deferred Actions : Add a notification about task running in the background
[ https://issues.apache.org/jira/browse/ATLAS-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4270: --- Attachment: 0001-ATLAS-4270-Deferred-Actions-Add-a-notification-about.patch > Deferred Actions : Add a notification about task running in the background > -- > > Key: ATLAS-4270 > URL: https://issues.apache.org/jira/browse/ATLAS-4270 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: deferred-actions > Attachments: > 0001-ATLAS-4270-Deferred-Actions-Add-a-notification-about.patch > > > On UI, the Association of tags happens very fast and the propagation goes in > the background as deferred action. Users might get confused as to why the > tags are not propagated yet. it would be good to add a notification or a > popup saying the propagation is yet to complete. > Create a Tasks tabs on the Entity Detail page, which shows the deferred task. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4270) Deferred Actions : Add a notification about task running in the background
Prasad P. Pawar created ATLAS-4270: -- Summary: Deferred Actions : Add a notification about task running in the background Key: ATLAS-4270 URL: https://issues.apache.org/jira/browse/ATLAS-4270 Project: Atlas Issue Type: Improvement Components: atlas-webui Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar On UI, the Association of tags happens very fast and the propagation goes in the background as deferred action. Users might get confused as to why the tags are not propagated yet. it would be good to add a notification or a popup saying the propagation is yet to complete. Create a Tasks tabs on the Entity Detail page, which shows the deferred task. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (ATLAS-4012) Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1
[ https://issues.apache.org/jira/browse/ATLAS-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reopened ATLAS-4012: In the integrity section, you should update with sha512 value. > Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1 > --- > > Key: ATLAS-4012 > URL: https://issues.apache.org/jira/browse/ATLAS-4012 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4012) Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1
[ https://issues.apache.org/jira/browse/ATLAS-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4012: --- Attachment: (was: 0001-ATLAS-4012-V2-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch) > Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1 > --- > > Key: ATLAS-4012 > URL: https://issues.apache.org/jira/browse/ATLAS-4012 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch, > 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4012) Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1
[ https://issues.apache.org/jira/browse/ATLAS-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4012: --- Attachment: 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch > Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1 > --- > > Key: ATLAS-4012 > URL: https://issues.apache.org/jira/browse/ATLAS-4012 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch, > 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4012) Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1
[ https://issues.apache.org/jira/browse/ATLAS-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4012: --- Attachment: 0001-ATLAS-4012-2-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-.patch > Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1 > --- > > Key: ATLAS-4012 > URL: https://issues.apache.org/jira/browse/ATLAS-4012 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4012-2-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-.patch, > 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4012) Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1
[ https://issues.apache.org/jira/browse/ATLAS-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4012: --- Attachment: (was: 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch) > Atlas - Upgrade bootstrap to 3.4.1 or 4.3.1 > --- > > Key: ATLAS-4012 > URL: https://issues.apache.org/jira/browse/ATLAS-4012 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: chaitali borole >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4012-UI-Atlas-Upgrade-bootstrap-to-3.4.1-or-4..patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4252) UI (New): Deleting subclassifications results in endless loading
[ https://issues.apache.org/jira/browse/ATLAS-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4252: --- Fix Version/s: 2.2.0 3.0.0 > UI (New): Deleting subclassifications results in endless loading > > > Key: ATLAS-4252 > URL: https://issues.apache.org/jira/browse/ATLAS-4252 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4252-UI-New-Deleting-subclassifications-result.patch > > > Steps: > # In new UI, create classification > # Create sub-classification for that classification > # Create sub-classification for that sub-classification > # Start deleting sub-classifications from latest to upwards > You will see that while deleting, the confirmation prompt for one of the > sub-classifications shows endless loading. Only on browser refresh it goes > away and we are able to delete it normally. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4240) UI: Some Categories are not shown in the tree that matches the search string of search bar.
[ https://issues.apache.org/jira/browse/ATLAS-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4240: --- Fix Version/s: 2.2.0 3.0.0 > UI: Some Categories are not shown in the tree that matches the search string > of search bar. > --- > > Key: ATLAS-4240 > URL: https://issues.apache.org/jira/browse/ATLAS-4240 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: categories > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-3903-UI-Glossary-category-not-reflected-in-the.patch, > CategoryList.png, Old-ui_Category_Bug.png, Old-ui_Category_bug_2.png > > > Consider "G6" glossary having "G6_C1" category, and "G6_C1" category having > "G6_SubCategory" category (refer image CategoryList.png) > Old-UI: > Glossary tab-> switch to category and refresh the page > Search for a category "G6" > It doesn't show "G6_SubCategory" in the search (refer to image > Old-ui_Category_Bug.png). > Expand the "G6_C1" category, Api is hit and "G6_SubCategory" is not > highlighted (refer to image Old-ui_Category_bug_2.png) > New-UI (left side search bar): > Glossary panel-> switch to category > Search for a category "G6" (left side search bar) > It doesn't show "G6_SubCategory" in the search > Expand "G6_C1" category, Api is hit and "G6_SubCategory" is not highlighted -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4242) (New UI) Single click of glossary doesn't work after clicking on Atlas logo.
[ https://issues.apache.org/jira/browse/ATLAS-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4242: --- Fix Version/s: 2.2.0 3.0.0 > (New UI) Single click of glossary doesn't work after clicking on Atlas logo. > > > Key: ATLAS-4242 > URL: https://issues.apache.org/jira/browse/ATLAS-4242 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > > Steps: > # Select any one existing glossary and single click it. > # Then click on Atlas logo > # Then once again single click the same glossary > You will see that the glossary does not get selected as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
