[jira] [Commented] (ATLAS-4607) UI improvements to support Atlas Lineage fetch on-demand
[ https://issues.apache.org/jira/browse/ATLAS-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550916#comment-17550916 ] Farhan Khan commented on ATLAS-4607: Review Board patch: https://reviews.apache.org/r/74012/ > UI improvements to support Atlas Lineage fetch on-demand > > > Key: ATLAS-4607 > URL: https://issues.apache.org/jira/browse/ATLAS-4607 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 3.0.0, 2.3.0 >Reporter: Radhika Kundam >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4607-UI-improvements-to-support-Atlas-Lineage-.patch > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
Review Request 74012: UI improvements to support Atlas Lineage fetch on-demand
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74012/ --- Review request for atlas, Jayendra Parab and Prasad Pawar. Bugs: ATLAS-4607 https://issues.apache.org/jira/browse/ATLAS-4607 Repository: atlas Description --- Atlas lineage for an entity returns all the entities connected in a single call, this is expensive if lineage is long and has multi-level. Lineage API response is large and UI fails to render the response. Diffs - dashboardv2/public/img/entity-icon/expandBtn.svg PRE-CREATION dashboardv2/public/js/collection/VLineageList.js bda649220 dashboardv2/public/js/external_lib/atlas-lineage/dist/index.js b31ee4911 dashboardv2/public/js/external_lib/atlas-lineage/dist/styles.css 2d7f9d9de dashboardv2/public/js/external_lib/atlas-lineage/src/Utils/DataUtils.js 1255eb070 dashboardv2/public/js/external_lib/atlas-lineage/src/Utils/LineageUtils.js 448a95ae6 dashboardv2/public/js/external_lib/atlas-lineage/src/index.js 3ceb3d90a dashboardv2/public/js/external_lib/atlas-lineage/src/styles/graph.scss ab1e82df3 dashboardv2/public/js/main.js 603e5ec3d dashboardv2/public/js/templates/graph/LineageLayoutView_tmpl.html 5f90b096e dashboardv2/public/js/utils/Globals.js c30f840f7 dashboardv2/public/js/utils/Helper.js f211bd055 dashboardv2/public/js/views/graph/LineageLayoutView.js e989c4719 dashboardv3/public/img/entity-icon/expandBtn.svg PRE-CREATION dashboardv3/public/js/collection/VLineageList.js bda649220 dashboardv3/public/js/external_lib/atlas-lineage/dist/index.js b31ee4911 dashboardv3/public/js/external_lib/atlas-lineage/dist/styles.css 2d7f9d9de dashboardv3/public/js/external_lib/atlas-lineage/src/Utils/DataUtils.js 1255eb070 dashboardv3/public/js/external_lib/atlas-lineage/src/Utils/LineageUtils.js 448a95ae6 dashboardv3/public/js/external_lib/atlas-lineage/src/index.js 3ceb3d90a dashboardv3/public/js/external_lib/atlas-lineage/src/styles/graph.scss ab1e82df3 dashboardv3/public/js/main.js 008fbb222 dashboardv3/public/js/templates/graph/LineageLayoutView_tmpl.html 5f90b096e dashboardv3/public/js/utils/Globals.js 5bbc71a69 dashboardv3/public/js/utils/Helper.js a242098b1 dashboardv3/public/js/views/graph/LineageLayoutView.js e989c4719 Diff: https://reviews.apache.org/r/74012/diff/1/ Testing --- Manually tested on the local for various possible scenarios. Thanks, Farhan Khan
[jira] [Updated] (ATLAS-4607) UI improvements to support Atlas Lineage fetch on-demand
[ https://issues.apache.org/jira/browse/ATLAS-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4607: --- Attachment: 0001-ATLAS-4607-UI-improvements-to-support-Atlas-Lineage-.patch > UI improvements to support Atlas Lineage fetch on-demand > > > Key: ATLAS-4607 > URL: https://issues.apache.org/jira/browse/ATLAS-4607 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 3.0.0, 2.3.0 >Reporter: Radhika Kundam >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4607-UI-improvements-to-support-Atlas-Lineage-.patch > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (ATLAS-4607) UI improvements to support Atlas Lineage fetch on-demand
[ https://issues.apache.org/jira/browse/ATLAS-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4607: --- Attachment: (was: 0001-ATLAS-4607-UI-improvements-to-support-Atlas-Lineage-.patch) > UI improvements to support Atlas Lineage fetch on-demand > > > Key: ATLAS-4607 > URL: https://issues.apache.org/jira/browse/ATLAS-4607 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 3.0.0, 2.3.0 >Reporter: Radhika Kundam >Assignee: Farhan Khan >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ATLAS-4583) UI: When there is no data, error is encountered on switching UI at a specific page
[ https://issues.apache.org/jira/browse/ATLAS-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550814#comment-17550814 ] ASF subversion and git services commented on ATLAS-4583: Commit 56bacf47d657e0e4a3bcc69eb3460c2d910dbc8c in atlas's branch refs/heads/branch-2.0 from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=56bacf47d ] ATLAS-4583 : (UI)When there is no data, error is encountered on switching UI at a specific page Signed-off-by: Pinal Shah (cherry picked from commit 12438ff2a20c382307cc375478740e7108cd6a74) > UI: When there is no data, error is encountered on switching UI at a specific > page > -- > > Key: ATLAS-4583 > URL: https://issues.apache.org/jira/browse/ATLAS-4583 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 3.0.0, 2.3.0 >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4583-UI-When-there-is-no-data-error-is-encount.patch > > > In old UI, when there is no data for classification and glossary, if the user > selects either 'tree' toggle in classification or 'category' toggle in > glossary section, and then attempts to switch UI, they get an endless loading > page with the following error message: > viewType=tree: Unknown/invalid classification > or > Given instance guid viewType=category is invalid/not found > > 23/05/22: Also found an issue where after creating a classification, > switching from Classic UI to new UI and then deleting the classification > results in an endless loading within the deletion dialog box. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ATLAS-4583) UI: When there is no data, error is encountered on switching UI at a specific page
[ https://issues.apache.org/jira/browse/ATLAS-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550813#comment-17550813 ] ASF subversion and git services commented on ATLAS-4583: Commit 12438ff2a20c382307cc375478740e7108cd6a74 in atlas's branch refs/heads/master from Farhan Khan [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=12438ff2a ] ATLAS-4583 : (UI)When there is no data, error is encountered on switching UI at a specific page Signed-off-by: Pinal Shah > UI: When there is no data, error is encountered on switching UI at a specific > page > -- > > Key: ATLAS-4583 > URL: https://issues.apache.org/jira/browse/ATLAS-4583 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 3.0.0, 2.3.0 >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4583-UI-When-there-is-no-data-error-is-encount.patch > > > In old UI, when there is no data for classification and glossary, if the user > selects either 'tree' toggle in classification or 'category' toggle in > glossary section, and then attempts to switch UI, they get an endless loading > page with the following error message: > viewType=tree: Unknown/invalid classification > or > Given instance guid viewType=category is invalid/not found > > 23/05/22: Also found an issue where after creating a classification, > switching from Classic UI to new UI and then deleting the classification > results in an endless loading within the deletion dialog box. -- This message was sent by Atlassian Jira (v8.20.7#820007)
