[jira] [Assigned] (ATLAS-4178) [UI] Save and Cancel buttons do not disappear after closing their respective sections in Entity Details page
[ https://issues.apache.org/jira/browse/ATLAS-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4178: -- Assignee: Prasad P. Pawar > [UI] Save and Cancel buttons do not disappear after closing their respective > sections in Entity Details page > > > Key: ATLAS-4178 > URL: https://issues.apache.org/jira/browse/ATLAS-4178 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: save_cancel_entity_details_page.webm > > > Steps: > 1. Open any section like "User Defined Properties", "Labels" and "Business > Metadata" > 2. Click on Add button > 3.Save and Cancel button should show up > 4. Close the section > You will see the Save and Cancel buttons still remains on the page, and in > certain browser resolutions appear to be misaligned with other elements of > the page. The whole process can be seen in the attached video. They remain on > the page and are clickable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3349) UI: Unable to edit AtlasServer entity with custom Required fields.
[ https://issues.apache.org/jira/browse/ATLAS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-3349: -- Assignee: Prasad P. Pawar (was: Keval Bhatt) > UI: Unable to edit AtlasServer entity with custom Required fields. > -- > > Key: ATLAS-3349 > URL: https://issues.apache.org/jira/browse/ATLAS-3349 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: editatlasserverentity.png > > > User creates a AtlasServer entity through UI with the following parameters: > "name": "$mycluster0", > "fullName": "server", > "displayName": "Myserver" > Then, if the user attempts to edit the entity by clicking the edit button, > the user will get a blank edit window with endless loop. (See attached > screenshot) > !editatlasserverentity.png|width=300, height=300! > The error in the console: > TypeError: that.entityData.get(...).relationshipAttributes is undefined -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4178) [UI] Save and Cancel buttons do not disappear after closing their respective sections in Entity Details page
[ https://issues.apache.org/jira/browse/ATLAS-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4178: --- Attachment: 0001-ATLAS-4178-UI-V1-Save-and-Cancel-buttons-do-not-disa.patch > [UI] Save and Cancel buttons do not disappear after closing their respective > sections in Entity Details page > > > Key: ATLAS-4178 > URL: https://issues.apache.org/jira/browse/ATLAS-4178 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4178-UI-Save-and-Cancel-buttons-do-not-disappe.patch, > 0001-ATLAS-4178-UI-V1-Save-and-Cancel-buttons-do-not-disa.patch, > save_cancel_entity_details_page.webm > > > Steps: > 1. Open any section like "User Defined Properties", "Labels" and "Business > Metadata" > 2. Click on Add button > 3.Save and Cancel button should show up > 4. Close the section > You will see the Save and Cancel buttons still remains on the page, and in > certain browser resolutions appear to be misaligned with other elements of > the page. The whole process can be seen in the attached video. They remain on > the page and are clickable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3352) UI: Improve Classification 'Propagated From' presentation
[ https://issues.apache.org/jira/browse/ATLAS-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-3352: -- Assignee: Prasad P. Pawar (was: Keval Bhatt) > UI: Improve Classification 'Propagated From' presentation > - > > Key: ATLAS-3352 > URL: https://issues.apache.org/jira/browse/ATLAS-3352 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: entity_pf_suggestion_1.png > > > Here is a suggestion to improve understanding of the UI Classification > "Propagated From" button. > !entity_pf_suggestion_1.png|width=400, height=300! > As visible in the above mockup, we can make the entity name from which the > classification has been propagated from visible in the button instead, and > the purpose of the link can be explained in the tooltip. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17298598#comment-17298598 ] Prasad P. Pawar commented on ATLAS-4012: Hi, the uploaded path has Upgrade bootstrap to 3.4.1 > 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] [Commented] (ATLAS-4157) UI: 'Assign' button in 'Related Terms' window should be disabled once it is clicked.
[ https://issues.apache.org/jira/browse/ATLAS-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298601#comment-17298601 ] Prasad P. Pawar commented on ATLAS-4157: This fix is present in ATLAS 4154 patch > UI: 'Assign' button in 'Related Terms' window should be disabled once it is > clicked. > > > Key: ATLAS-4157 > URL: https://issues.apache.org/jira/browse/ATLAS-4157 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: glossary-terms-assign-button-issue.png > > > When user tries to add 'Related Terms', the 'Assign' button in the popup > window for Related Terms should be disabled once it is clicked. > Currently it is still enabled while the update call is going on. This results > in multiple duplicate 'Related terms' entries when user double clicks the > Assign button. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4142) [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary Term"
[ https://issues.apache.org/jira/browse/ATLAS-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4142: -- Assignee: Prasad P. Pawar > [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary > Term" > - > > Key: ATLAS-4142 > URL: https://issues.apache.org/jira/browse/ATLAS-4142 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: image-2021-02-05-16-28-20-154.png > > > The upload window displays "Import Glossary". It will be good to rename it to > "Import Glossary Term" > !image-2021-02-05-16-28-20-154.png|width=720,height=388! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4142) [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary Term"
[ https://issues.apache.org/jira/browse/ATLAS-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-4142. Resolution: Resolved > [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary > Term" > - > > Key: ATLAS-4142 > URL: https://issues.apache.org/jira/browse/ATLAS-4142 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: image-2021-02-05-16-28-20-154.png > > > The upload window displays "Import Glossary". It will be good to rename it to > "Import Glossary Term" > !image-2021-02-05-16-28-20-154.png|width=720,height=388! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4142) [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary Term"
[ https://issues.apache.org/jira/browse/ATLAS-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300050#comment-17300050 ] Prasad P. Pawar commented on ATLAS-4142: This fix is merged in [ATLAS-4154|https://issues.apache.org/jira/browse/ATLAS-4154] > [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary > Term" > - > > Key: ATLAS-4142 > URL: https://issues.apache.org/jira/browse/ATLAS-4142 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: image-2021-02-05-16-28-20-154.png > > > The upload window displays "Import Glossary". It will be good to rename it to > "Import Glossary Term" > !image-2021-02-05-16-28-20-154.png|width=720,height=388! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3210) UI: Deleted relationship not appearing as expected in Edit Entity and Lineage
[ https://issues.apache.org/jira/browse/ATLAS-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-3210: -- Assignee: Prasad P. Pawar (was: Keval Bhatt) > UI: Deleted relationship not appearing as expected in Edit Entity and Lineage > - > > Key: ATLAS-3210 > URL: https://issues.apache.org/jira/browse/ATLAS-3210 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > Attachments: deleterelationship_scenario1.png, > deleterelationship_scenario1_2.png, deleterelationship_scenario1_3.png > > > Consider the following scenario: > > !deleterelationship_scenario1.png|width=650,height=250! > > empView has an input relationship as well as an output relationship with > TestProcess. *NOTE: EmpMaster, TestProcess, empView and all relationships > were all created within Atlas UI and not imported from anywhere.* > We go and edit TestProcess and delete "empView" from Inputs: > > !deleterelationship_scenario1_2.png|width=650,height=250! > > Go to TestProcess and then go to Relationships, select graph view, and then > click on hive_process. You will see the deletion icon for the view that has > been deleted. > !deleterelationship_scenario1_3.png|width=650,height=250! > But if we go to lineage it looks as though the relationship is still in place. > !deleterelationship_scenario1.png! > Similarly, if we go back to the Edit Entity page for TestProcess and scroll > down to Inputs and you will still see the empView in the input list. > Ideally, we should see some evidence of the deletion in both Lineage and Edit > Entity Page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4157) UI: 'Assign' button in 'Related Terms' window should be disabled once it is clicked.
[ https://issues.apache.org/jira/browse/ATLAS-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-4157. Resolution: Resolved > UI: 'Assign' button in 'Related Terms' window should be disabled once it is > clicked. > > > Key: ATLAS-4157 > URL: https://issues.apache.org/jira/browse/ATLAS-4157 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: glossary-terms-assign-button-issue.png > > > When user tries to add 'Related Terms', the 'Assign' button in the popup > window for Related Terms should be disabled once it is clicked. > Currently it is still enabled while the update call is going on. This results > in multiple duplicate 'Related terms' entries when user double clicks the > Assign button. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4143) [Atlas: Glossary Term Bulk Import] Adding supported file types in the import window will be user friendly
[ https://issues.apache.org/jira/browse/ATLAS-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4143: -- Assignee: Prasad P. Pawar > [Atlas: Glossary Term Bulk Import] Adding supported file types in the import > window will be user friendly > - > > Key: ATLAS-4143 > URL: https://issues.apache.org/jira/browse/ATLAS-4143 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: image-2021-02-05-17-09-56-855.png > > > The current text in upload window of "Import glossary term" feature displays > "*Drop files here or click to upload*" > !image-2021-02-05-17-09-56-855.png|width=518,height=275! > It would be user friendly if it displayed the supported formats. > Eg: Drop files (.csv, .xls) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4143) [Atlas: Glossary Term Bulk Import] Adding supported file types in the import window will be user friendly
[ https://issues.apache.org/jira/browse/ATLAS-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300060#comment-17300060 ] Prasad P. Pawar commented on ATLAS-4143: This Fix is merged in [ATLAS-4154|https://issues.apache.org/jira/browse/ATLAS-4154 ] > [Atlas: Glossary Term Bulk Import] Adding supported file types in the import > window will be user friendly > - > > Key: ATLAS-4143 > URL: https://issues.apache.org/jira/browse/ATLAS-4143 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: image-2021-02-05-17-09-56-855.png > > > The current text in upload window of "Import glossary term" feature displays > "*Drop files here or click to upload*" > !image-2021-02-05-17-09-56-855.png|width=518,height=275! > It would be user friendly if it displayed the supported formats. > Eg: Drop files (.csv, .xls) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-4143) [Atlas: Glossary Term Bulk Import] Adding supported file types in the import window will be user friendly
[ https://issues.apache.org/jira/browse/ATLAS-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300060#comment-17300060 ] Prasad P. Pawar edited comment on ATLAS-4143 at 3/12/21, 5:38 AM: -- This Fix is merged in [ATLAS-4154|https://issues.apache.org/jira/browse/ATLAS-4154] was (Author: prasadpp13): This Fix is merged in [ATLAS-4154|https://issues.apache.org/jira/browse/ATLAS-4154 ] > [Atlas: Glossary Term Bulk Import] Adding supported file types in the import > window will be user friendly > - > > Key: ATLAS-4143 > URL: https://issues.apache.org/jira/browse/ATLAS-4143 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: image-2021-02-05-17-09-56-855.png > > > The current text in upload window of "Import glossary term" feature displays > "*Drop files here or click to upload*" > !image-2021-02-05-17-09-56-855.png|width=518,height=275! > It would be user friendly if it displayed the supported formats. > Eg: Drop files (.csv, .xls) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4154) Atlas: UI Glossary changes & improvements
[ https://issues.apache.org/jira/browse/ATLAS-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4154: --- Fix Version/s: 2.2.0 3.0.0 > Atlas: UI Glossary changes & improvements > - > > Key: ATLAS-4154 > URL: https://issues.apache.org/jira/browse/ATLAS-4154 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: glossary > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4154-Atlas-UI-Glossary-changes-improvements-fi.patch, > 0001-ATLAS-4154-UI-Glossary-changes-improvements-fixed-V1.patch, > AssignButtonDisableFix.png, Atlas-4133Fix.png, CDPCD-22260Fix.png, > CDPD-22255_CDPD-22256fix.png, CDPD-22259_CDPD-22258Fix.png > > > 1)[Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary > Term" > 2)[Atlas: Glossary Term Bulk Import] Adding supported file types in the > import window will be user friendly > 3) [Atlas: Glossary Term Bulk Import] The file name becomes invisible as the > progress bar overlaps it during bulk glossary term import > 4)[Atlas: Glossary] While adding the related term, self should not be allowed > to be selected > 5)[Atlas: Glossary] On updating the related terms, UI allows the user to add > the already added term > 6) [ATLAS-4133|https://issues.apache.org/jira/browse/ATLAS-4133] > [Atlas: Glossary Term Bulk Import] Disable the option to download upload > template when the category is chosen on the glossary page > 7) [ATLAS-4157|https://issues.apache.org/jira/browse/ATLAS-4157] > UI: 'Assign' button in the 'Related Terms' window should be disabled once it > is clicked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4141) [Atlas: Glossary Term Bulk Import] The file name becomes invisible as the progress bar overlaps it during bulk glossary term import
[ https://issues.apache.org/jira/browse/ATLAS-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4141: -- Assignee: Prasad P. Pawar > [Atlas: Glossary Term Bulk Import] The file name becomes invisible as the > progress bar overlaps it during bulk glossary term import > --- > > Key: ATLAS-4141 > URL: https://issues.apache.org/jira/browse/ATLAS-4141 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: image-2021-02-05-16-20-38-116.png, > image-2021-02-05-16-21-08-865.png > > > The file name is this case is only_names.csv which is hidden by the progress > bar > !image-2021-02-05-16-21-08-865.png|width=486,height=312! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4145) [Atlas: Glossary] While adding related term, self should not be allowed to be selected
[ https://issues.apache.org/jira/browse/ATLAS-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4145: -- Assignee: Prasad P. Pawar > [Atlas: Glossary] While adding related term, self should not be allowed to be > selected > -- > > Key: ATLAS-4145 > URL: https://issues.apache.org/jira/browse/ATLAS-4145 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: image-2021-02-05-18-13-20-689.png > > > While adding any related term to any term, self is available to be selected. > If selected, "*Term cant have a relationship with self*" error is thrown. > !image-2021-02-05-18-13-20-689.png|width=493,height=274! > Though it throws the right error message, it will be good not to allow "self > term" to be selected in the first place for better user experience > Blocking from being selected conveys the message > > Steps to reproduce: > # Create a glossary and term > # Open the created term, in the "related terms" tab add any relation > # Select self as a term to be related -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4143) [Atlas: Glossary Term Bulk Import] Adding supported file types in the import window will be user friendly
[ https://issues.apache.org/jira/browse/ATLAS-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-4143. Resolution: Resolved > [Atlas: Glossary Term Bulk Import] Adding supported file types in the import > window will be user friendly > - > > Key: ATLAS-4143 > URL: https://issues.apache.org/jira/browse/ATLAS-4143 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: image-2021-02-05-17-09-56-855.png > > > The current text in upload window of "Import glossary term" feature displays > "*Drop files here or click to upload*" > !image-2021-02-05-17-09-56-855.png|width=518,height=275! > It would be user friendly if it displayed the supported formats. > Eg: Drop files (.csv, .xls) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4141) [Atlas: Glossary Term Bulk Import] The file name becomes invisible as the progress bar overlaps it during bulk glossary term import
[ https://issues.apache.org/jira/browse/ATLAS-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-4141. Resolution: Resolved > [Atlas: Glossary Term Bulk Import] The file name becomes invisible as the > progress bar overlaps it during bulk glossary term import > --- > > Key: ATLAS-4141 > URL: https://issues.apache.org/jira/browse/ATLAS-4141 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: image-2021-02-05-16-20-38-116.png, > image-2021-02-05-16-21-08-865.png > > > The file name is this case is only_names.csv which is hidden by the progress > bar > !image-2021-02-05-16-21-08-865.png|width=486,height=312! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (ATLAS-4142) [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary Term"
[ https://issues.apache.org/jira/browse/ATLAS-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reopened ATLAS-4142: > [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary > Term" > - > > Key: ATLAS-4142 > URL: https://issues.apache.org/jira/browse/ATLAS-4142 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: image-2021-02-05-16-28-20-154.png > > > The upload window displays "Import Glossary". It will be good to rename it to > "Import Glossary Term" > !image-2021-02-05-16-28-20-154.png|width=720,height=388! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4142) [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary Term"
[ https://issues.apache.org/jira/browse/ATLAS-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-4142. Resolution: Resolved > [Atlas: Glossary Term Bulk Import] Rename upload window to "Import Glossary > Term" > - > > Key: ATLAS-4142 > URL: https://issues.apache.org/jira/browse/ATLAS-4142 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: image-2021-02-05-16-28-20-154.png > > > The upload window displays "Import Glossary". It will be good to rename it to > "Import Glossary Term" > !image-2021-02-05-16-28-20-154.png|width=720,height=388! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4145) [Atlas: Glossary] While adding related term, self should not be allowed to be selected
[ https://issues.apache.org/jira/browse/ATLAS-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-4145. Resolution: Resolved > [Atlas: Glossary] While adding related term, self should not be allowed to be > selected > -- > > Key: ATLAS-4145 > URL: https://issues.apache.org/jira/browse/ATLAS-4145 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: image-2021-02-05-18-13-20-689.png > > > While adding any related term to any term, self is available to be selected. > If selected, "*Term cant have a relationship with self*" error is thrown. > !image-2021-02-05-18-13-20-689.png|width=493,height=274! > Though it throws the right error message, it will be good not to allow "self > term" to be selected in the first place for better user experience > Blocking from being selected conveys the message > > Steps to reproduce: > # Create a glossary and term > # Open the created term, in the "related terms" tab add any relation > # Select self as a term to be related -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4144) [Atlas: Glossary] UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar reassigned ATLAS-4144:
--
Assignee: Prasad P. Pawar
> [Atlas: Glossary] UI should not allow the user to create a glossary with
> blank(" ") name
>
>
> Key: ATLAS-4144
> URL: https://issues.apache.org/jira/browse/ATLAS-4144
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments: Screenshot 2021-01-25 at 6.05.02 PM.png, Screenshot
> 2021-02-05 at 5.12.46 PM.png, Screenshot 2021-02-05 at 5.12.56 PM.png
>
>
> *Steps to reproduce:*
> In UI, go to glossary tab
> Click on *+* icon to create a new glossary
> Enter (Create button will not be enabled)
> Now, Select the blank space, now "*Create*" button will be enabled
> !Screenshot 2021-01-25 at 6.05.02 PM.png|width=461,height=266!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4144) [Atlas: Glossary] UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar resolved ATLAS-4144.
Resolution: Resolved
> [Atlas: Glossary] UI should not allow the user to create a glossary with
> blank(" ") name
>
>
> Key: ATLAS-4144
> URL: https://issues.apache.org/jira/browse/ATLAS-4144
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments: Screenshot 2021-01-25 at 6.05.02 PM.png, Screenshot
> 2021-02-05 at 5.12.46 PM.png, Screenshot 2021-02-05 at 5.12.56 PM.png
>
>
> *Steps to reproduce:*
> In UI, go to glossary tab
> Click on *+* icon to create a new glossary
> Enter (Create button will not be enabled)
> Now, Select the blank space, now "*Create*" button will be enabled
> !Screenshot 2021-01-25 at 6.05.02 PM.png|width=461,height=266!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3210) UI: Deleted relationship not appearing as expected in Edit Entity and Lineage
[ https://issues.apache.org/jira/browse/ATLAS-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3210: --- Attachment: ATLAS-3210_1_fix.png ATLAS-3210_2_fix.png ATLAS-3210_3_fix.png ATLAS-3210_4_fix.png > UI: Deleted relationship not appearing as expected in Edit Entity and Lineage > - > > Key: ATLAS-3210 > URL: https://issues.apache.org/jira/browse/ATLAS-3210 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-3210-UI-Deleted-relationship-not-appearing-as-.patch, > ATLAS-3210_1_fix.png, ATLAS-3210_2_fix.png, ATLAS-3210_3_fix.png, > ATLAS-3210_4_fix.png, deleterelationship_scenario1.png, > deleterelationship_scenario1_2.png, deleterelationship_scenario1_3.png > > > Consider the following scenario: > > !deleterelationship_scenario1.png|width=650,height=250! > > empView has an input relationship as well as an output relationship with > TestProcess. *NOTE: EmpMaster, TestProcess, empView and all relationships > were all created within Atlas UI and not imported from anywhere.* > We go and edit TestProcess and delete "empView" from Inputs: > > !deleterelationship_scenario1_2.png|width=650,height=250! > > Go to TestProcess and then go to Relationships, select graph view, and then > click on hive_process. You will see the deletion icon for the view that has > been deleted. > !deleterelationship_scenario1_3.png|width=650,height=250! > But if we go to lineage it looks as though the relationship is still in place. > !deleterelationship_scenario1.png! > Similarly, if we go back to the Edit Entity page for TestProcess and scroll > down to Inputs and you will still see the empView in the input list. > Ideally, we should see some evidence of the deletion in both Lineage and Edit > Entity Page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4201) UI: Add attributes modal api hits when no attributes are added on Classification detail page.
Prasad P. Pawar created ATLAS-4201: -- Summary: UI: Add attributes modal api hits when no attributes are added on Classification detail page. Key: ATLAS-4201 URL: https://issues.apache.org/jira/browse/ATLAS-4201 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar Attachments: AddAttributesField.png, AddButtonEnabled.png, Api_SuccessMessage.png Steps: 1) Add attributes by clicking on the attribute + button on the classification detail page. Add Attribute modal opens with default 1 attribute field, "Add" button of the modal is disabled. 2) Click on the "Add New Attributes" button. Additional attribute field is added, with remove attribute field buttons. 3) Remove all the attributes fields by clicking on the remove buttons. 4) Add button gets enable (should be disabled), refer to the attached image. 5) Click on Add button, API is hit, an Attribute added success message is shown, refer to the attached image. Expectation: Show Validation message on "Add" Button click of the modal: "No attribute is added" or Disable the "Add" Button of modal or At least keep one Attribute field in the modal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4202) [Atlas: Audits] When there are no much data to display, it is better to hide in UI instead of displaying no records found
[ https://issues.apache.org/jira/browse/ATLAS-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4202: -- Assignee: Prasad P. Pawar > [Atlas: Audits] When there are no much data to display, it is better to hide > in UI instead of displaying no records found > - > > Key: ATLAS-4202 > URL: https://issues.apache.org/jira/browse/ATLAS-4202 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Attachments: Screenshot 2021-03-12 at 5.47.52 PM.png, > image-2021-03-12-17-51-44-307.png > > > When a tag is added or updated, there are no much technical details to > display. In such cases, it is better to hide those details in UI instead of > displaying *"No records found"* > *!image-2021-03-12-17-51-44-307.png|width=1187,height=181!* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3352) UI: Improve Classification 'Propagated From' presentation
[ https://issues.apache.org/jira/browse/ATLAS-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-3352. Resolution: Won't Fix As this fix may affect Atlas performance, from the backend we will need an extra key "name" from the response, or from the frontend we need to search in all the present classifications for the name (in case of a large number of classification) this may result in delay, > UI: Improve Classification 'Propagated From' presentation > - > > Key: ATLAS-3352 > URL: https://issues.apache.org/jira/browse/ATLAS-3352 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: entity_pf_suggestion_1.png > > > Here is a suggestion to improve understanding of the UI Classification > "Propagated From" button. > !entity_pf_suggestion_1.png|width=400, height=300! > As visible in the above mockup, we can make the entity name from which the > classification has been propagated from visible in the button instead, and > the purpose of the link can be explained in the tooltip. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4212) Wrong validation message is shown in attribute filter
[ https://issues.apache.org/jira/browse/ATLAS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4212: -- Attachment: 0001-ATLAS-4221-UI-Wrong-validation-message-is-shown-in-a.patch Assignee: Prasad P. Pawar > Wrong validation message is shown in attribute filter > - > > Key: ATLAS-4212 > URL: https://issues.apache.org/jira/browse/ATLAS-4212 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: Screenshot from 2021-03-17 15-34-45.png > > > Actual:: When user copy paste the label name while searching in attribute > filter it shows validation message as ' Label(s) is required', even if label > is provided. > Expected:: It should search for the label added. > PFA evidence file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4212) Wrong validation message is shown in attribute filter
[ https://issues.apache.org/jira/browse/ATLAS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4212: --- Attachment: (was: 0001-ATLAS-4221-UI-Wrong-validation-message-is-shown-in-a.patch) > Wrong validation message is shown in attribute filter > - > > Key: ATLAS-4212 > URL: https://issues.apache.org/jira/browse/ATLAS-4212 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: Screenshot from 2021-03-17 15-34-45.png > > > Actual:: When user copy paste the label name while searching in attribute > filter it shows validation message as ' Label(s) is required', even if label > is provided. > Expected:: It should search for the label added. > PFA evidence file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4212) Wrong validation message is shown in attribute filter
[ https://issues.apache.org/jira/browse/ATLAS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4212: --- Attachment: 0001-ATLAS-4212-UI-Wrong-validation-message-is-shown-in-a.patch > Wrong validation message is shown in attribute filter > - > > Key: ATLAS-4212 > URL: https://issues.apache.org/jira/browse/ATLAS-4212 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4212-UI-Wrong-validation-message-is-shown-in-a.patch, Screenshot > from 2021-03-17 15-34-45.png > > > Actual:: When user copy paste the label name while searching in attribute > filter it shows validation message as ' Label(s) is required', even if label > is provided. > Expected:: It should search for the label added. > PFA evidence file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4212) Wrong validation message is shown in attribute filter
[ https://issues.apache.org/jira/browse/ATLAS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303281#comment-17303281 ] Prasad P. Pawar commented on ATLAS-4212: Hi, This issue is fixed in the uploaded path, we have to change the label value Select field to Input filed. > Wrong validation message is shown in attribute filter > - > > Key: ATLAS-4212 > URL: https://issues.apache.org/jira/browse/ATLAS-4212 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4212-UI-Wrong-validation-message-is-shown-in-a.patch, Screenshot > from 2021-03-17 15-34-45.png > > > Actual:: When user copy paste the label name while searching in attribute > filter it shows validation message as ' Label(s) is required', even if label > is provided. > Expected:: It should search for the label added. > PFA evidence file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4213) Atlas UI is taking lot of time to load.
Prasad P. Pawar created ATLAS-4213: -- Summary: Atlas UI is taking lot of time to load. Key: ATLAS-4213 URL: https://issues.apache.org/jira/browse/ATLAS-4213 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 3.0.0 Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar Fix For: 2.2.0 Description- Atlas UI is taking a lot of time to load, after metadata creation part of scale testing, a large number of classifications & entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4166) Misalignment happened on entity page, when resized the browser window
[ https://issues.apache.org/jira/browse/ATLAS-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4166: --- Fix Version/s: 2.2.0 > Misalignment happened on entity page, when resized the browser window > - > > Key: ATLAS-4166 > URL: https://issues.apache.org/jira/browse/ATLAS-4166 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4166-UI-Misalignment-happened-on-entity-page-w.patch, > screenshot-newtab-2021.02.18-17_36_15.png > > > On resizing the browser window, entity details page shows overlapped fields > (User-defined properties, Labels, Business Metadata) > PFA -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4166) Misalignment happened on entity page, when resized the browser window
[ https://issues.apache.org/jira/browse/ATLAS-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4166: --- Affects Version/s: 3.0.0 > Misalignment happened on entity page, when resized the browser window > - > > Key: ATLAS-4166 > URL: https://issues.apache.org/jira/browse/ATLAS-4166 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4166-UI-Misalignment-happened-on-entity-page-w.patch, > screenshot-newtab-2021.02.18-17_36_15.png > > > On resizing the browser window, entity details page shows overlapped fields > (User-defined properties, Labels, Business Metadata) > PFA -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.
[ https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3376: --- Fix Version/s: 2.2.0 > UI: When no Catalogs are present, user should be presented with an > appropriate message when trying to associate Category to Term. > - > > Key: ATLAS-3376 > URL: https://issues.apache.org/jira/browse/ATLAS-3376 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-3376-UI-V1-When-no-Catalogs-are-present-user-s.patch, > 0001-ATLAS-3376-UI-V2-When-no-Catalogs-are-present-user-s.patch, > 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, > ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 > 22-25-05.png, screenshot-newtab-2021.02.22-22_31_06.png > > > If a user tries to associate a Category to a Term, and if not a single > Category has been created for any of the Glossaries, the user is presented > with the Category association screen but with no Categories for the user to > assign to the term. > This could create a confusion that there might be a Catalog present somewhere > but is not visible to the user, when actually no Catalogs exist. A > notification should be fired in this scenario, informing the user that no > Catalog exists that can be assigned to the term. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.
[ https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3376: --- Affects Version/s: 3.0.0 > UI: When no Catalogs are present, user should be presented with an > appropriate message when trying to associate Category to Term. > - > > Key: ATLAS-3376 > URL: https://issues.apache.org/jira/browse/ATLAS-3376 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-3376-UI-V1-When-no-Catalogs-are-present-user-s.patch, > 0001-ATLAS-3376-UI-V2-When-no-Catalogs-are-present-user-s.patch, > 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, > ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 > 22-25-05.png, screenshot-newtab-2021.02.22-22_31_06.png > > > If a user tries to associate a Category to a Term, and if not a single > Category has been created for any of the Glossaries, the user is presented > with the Category association screen but with no Categories for the user to > assign to the term. > This could create a confusion that there might be a Catalog present somewhere > but is not visible to the user, when actually no Catalogs exist. A > notification should be fired in this scenario, informing the user that no > Catalog exists that can be assigned to the term. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3186) UI: Background navigation is possible when "Advanced Search Queries" popup is active.
[ https://issues.apache.org/jira/browse/ATLAS-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3186: --- Fix Version/s: 2.2.0 > UI: Background navigation is possible when "Advanced Search Queries" popup is > active. > - > > Key: ATLAS-3186 > URL: https://issues.apache.org/jira/browse/ATLAS-3186 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-3186-UI-Background-navigation-is-possible-when.patch > > > Steps: > # From Atlas UI, navigate as follows: Search–>Classification–>Change button > from Flat to Tree->Glossary–>Search > # Click on "?" icon in Search. > # Click the back button of your browser > You will see that as you go on pressing the back button, navigation will > occur in the background in the reverse order of menus mentioned in step 1 > (and the button selection will be reversed from Tree to Flat). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3186) UI: Background navigation is possible when "Advanced Search Queries" popup is active.
[ https://issues.apache.org/jira/browse/ATLAS-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3186: --- Affects Version/s: 3.0.0 > UI: Background navigation is possible when "Advanced Search Queries" popup is > active. > - > > Key: ATLAS-3186 > URL: https://issues.apache.org/jira/browse/ATLAS-3186 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-3186-UI-Background-navigation-is-possible-when.patch > > > Steps: > # From Atlas UI, navigate as follows: Search–>Classification–>Change button > from Flat to Tree->Glossary–>Search > # Click on "?" icon in Search. > # Click the back button of your browser > You will see that as you go on pressing the back button, navigation will > occur in the background in the reverse order of menus mentioned in step 1 > (and the button selection will be reversed from Tree to Flat). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4167) Large no. of calls are getting generated while rendering search results
[ https://issues.apache.org/jira/browse/ATLAS-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4167: --- Affects Version/s: 3.0.0 > Large no. of calls are getting generated while rendering search results > --- > > Key: ATLAS-4167 > URL: https://issues.apache.org/jira/browse/ATLAS-4167 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4167-UI-Large-no.-of-calls-are-getting-generat.patch, > ATLAS-4167Bug.png, ATLAS-4167fix.png > > > While rendering search-results, there are large number of calls to Atlas > server to retrieve entity-icon. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4167) Large no. of calls are getting generated while rendering search results
[ https://issues.apache.org/jira/browse/ATLAS-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4167: --- Fix Version/s: 2.2.0 > Large no. of calls are getting generated while rendering search results > --- > > Key: ATLAS-4167 > URL: https://issues.apache.org/jira/browse/ATLAS-4167 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4167-UI-Large-no.-of-calls-are-getting-generat.patch, > ATLAS-4167Bug.png, ATLAS-4167fix.png > > > While rendering search-results, there are large number of calls to Atlas > server to retrieve entity-icon. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-4167) Large no. of calls are getting generated while rendering search results
[ https://issues.apache.org/jira/browse/ATLAS-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303323#comment-17303323 ] Prasad P. Pawar edited comment on ATLAS-4167 at 3/17/21, 12:00 PM: --- commit id: 5aab9b0c6d1379d3751e0d13f06819f143617fe4 was (Author: prasadpp13): commit id: https://gerrit.sjc.cloudera.com/c/cdh/atlas/+/120667 > Large no. of calls are getting generated while rendering search results > --- > > Key: ATLAS-4167 > URL: https://issues.apache.org/jira/browse/ATLAS-4167 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4167-UI-Large-no.-of-calls-are-getting-generat.patch, > ATLAS-4167Bug.png, ATLAS-4167fix.png > > > While rendering search-results, there are large number of calls to Atlas > server to retrieve entity-icon. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.
[ https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303350#comment-17303350 ] Prasad P. Pawar commented on ATLAS-3376: commit id: c551f66556e01d69f2918831b8b93b0397b04d75 > UI: When no Catalogs are present, user should be presented with an > appropriate message when trying to associate Category to Term. > - > > Key: ATLAS-3376 > URL: https://issues.apache.org/jira/browse/ATLAS-3376 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-3376-UI-V1-When-no-Catalogs-are-present-user-s.patch, > 0001-ATLAS-3376-UI-V2-When-no-Catalogs-are-present-user-s.patch, > 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, > ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 > 22-25-05.png, screenshot-newtab-2021.02.22-22_31_06.png > > > If a user tries to associate a Category to a Term, and if not a single > Category has been created for any of the Glossaries, the user is presented > with the Category association screen but with no Categories for the user to > assign to the term. > This could create a confusion that there might be a Catalog present somewhere > but is not visible to the user, when actually no Catalogs exist. A > notification should be fired in this scenario, informing the user that no > Catalog exists that can be assigned to the term. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4178) [UI] Save and Cancel buttons do not disappear after closing their respective sections in Entity Details page
[ https://issues.apache.org/jira/browse/ATLAS-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303358#comment-17303358 ] Prasad P. Pawar commented on ATLAS-4178: commit id: 122be98b6f2348951e860aead8d7e0bf1b88de79 > [UI] Save and Cancel buttons do not disappear after closing their respective > sections in Entity Details page > > > Key: ATLAS-4178 > URL: https://issues.apache.org/jira/browse/ATLAS-4178 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4178-UI-Save-and-Cancel-buttons-do-not-disappe.patch, > 0001-ATLAS-4178-UI-V1-Save-and-Cancel-buttons-do-not-disa.patch, > save_cancel_entity_details_page.webm > > > Steps: > 1. Open any section like "User Defined Properties", "Labels" and "Business > Metadata" > 2. Click on Add button > 3.Save and Cancel button should show up > 4. Close the section > You will see the Save and Cancel buttons still remains on the page, and in > certain browser resolutions appear to be misaligned with other elements of > the page. The whole process can be seen in the attached video. They remain on > the page and are clickable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3693) [Business Metadata] Unable to add negative values in multi-valued attributes for byte, short, int, long, float, double
[
https://issues.apache.org/jira/browse/ATLAS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar reassigned ATLAS-3693:
--
Assignee: Prasad P. Pawar
> [Business Metadata] Unable to add negative values in multi-valued attributes
> for byte, short, int, long, float, double
> ---
>
> Key: ATLAS-3693
> URL: https://issues.apache.org/jira/browse/ATLAS-3693
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Prasad P. Pawar
>Priority: Major
>
> byte, short, int, long, float, double data types can have values ranging from
> - to +, but when the attribute is defined as multi valued, unable to add
> negative values for these attributes. Entering a - sign, does nothing. The
> same works fine if the attribute is defined to be non multi-valued.
> Also, this works fine via the REST API.
> {code:java}
> curl -X POST \
> 'https://:31443/api/atlas/v2/entity/guid/ab29815d-6d20-44ee-b426-8fba946b72a5/businessmetata?isOverwrite=true'
> \ -H 'cache-control: no-cache' \ -H 'content-type: application/json' \ -H
> 'postman-token: 43107e84-a29c-b1b9-b628-4e0cf4645158' \ -H 'x-xsrf-header:
> \"\"' \ -d '{"Test Multi":{"int":["1221","121222",
> "-99162"]},"Test":{"long":"922337203685477"}}' {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4213) Atlas UI is taking lot of time to load.
[ https://issues.apache.org/jira/browse/ATLAS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4213: --- Attachment: 0001-ATLAS-4213-V1-UIAtlas-UI-is-taking-lot-of-time-to-lo.patch > Atlas UI is taking lot of time to load. > --- > > Key: ATLAS-4213 > URL: https://issues.apache.org/jira/browse/ATLAS-4213 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4213-Atlas-UI-is-taking-lot-of-time-to-load.fi.patch, > 0001-ATLAS-4213-V1-UIAtlas-UI-is-taking-lot-of-time-to-lo.patch > > > Description- > Atlas UI is taking a lot of time to load, after metadata creation part of > scale testing, a large number of classifications & entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4213) Atlas UI is taking lot of time to load.
[ https://issues.apache.org/jira/browse/ATLAS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303994#comment-17303994 ] Prasad P. Pawar commented on ATLAS-4213: Added updated patch, some code optimize & for new-ui file replaced 0001-ATLAS-4213-V1-UIAtlas-UI-is-taking-lot-of-time-to-lo.patch > Atlas UI is taking lot of time to load. > --- > > Key: ATLAS-4213 > URL: https://issues.apache.org/jira/browse/ATLAS-4213 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4213-Atlas-UI-is-taking-lot-of-time-to-load.fi.patch, > 0001-ATLAS-4213-V1-UIAtlas-UI-is-taking-lot-of-time-to-lo.patch > > > Description- > Atlas UI is taking a lot of time to load, after metadata creation part of > scale testing, a large number of classifications & entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3693) [Business Metadata] Unable to add negative values in multi-valued attributes for byte, short, int, long, float, double
[
https://issues.apache.org/jira/browse/ATLAS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-3693:
---
Affects Version/s: 3.0.0
> [Business Metadata] Unable to add negative values in multi-valued attributes
> for byte, short, int, long, float, double
> ---
>
> Key: ATLAS-3693
> URL: https://issues.apache.org/jira/browse/ATLAS-3693
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-3693-UI-Business-Metadata-Unable-to-add-negati.patch
>
>
> byte, short, int, long, float, double data types can have values ranging from
> - to +, but when the attribute is defined as multi valued, unable to add
> negative values for these attributes. Entering a - sign, does nothing. The
> same works fine if the attribute is defined to be non multi-valued.
> Also, this works fine via the REST API.
> {code:java}
> curl -X POST \
> 'https://:31443/api/atlas/v2/entity/guid/ab29815d-6d20-44ee-b426-8fba946b72a5/businessmetata?isOverwrite=true'
> \ -H 'cache-control: no-cache' \ -H 'content-type: application/json' \ -H
> 'postman-token: 43107e84-a29c-b1b9-b628-4e0cf4645158' \ -H 'x-xsrf-header:
> \"\"' \ -d '{"Test Multi":{"int":["1221","121222",
> "-99162"]},"Test":{"long":"922337203685477"}}' {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3693) [Business Metadata] Unable to add negative values in multi-valued attributes for byte, short, int, long, float, double
[
https://issues.apache.org/jira/browse/ATLAS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-3693:
---
Fix Version/s: 2.2.0
> [Business Metadata] Unable to add negative values in multi-valued attributes
> for byte, short, int, long, float, double
> ---
>
> Key: ATLAS-3693
> URL: https://issues.apache.org/jira/browse/ATLAS-3693
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 3.0.0
>Reporter: Umesh Padashetty
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 2.2.0
>
> Attachments:
> 0001-ATLAS-3693-UI-Business-Metadata-Unable-to-add-negati.patch
>
>
> byte, short, int, long, float, double data types can have values ranging from
> - to +, but when the attribute is defined as multi valued, unable to add
> negative values for these attributes. Entering a - sign, does nothing. The
> same works fine if the attribute is defined to be non multi-valued.
> Also, this works fine via the REST API.
> {code:java}
> curl -X POST \
> 'https://:31443/api/atlas/v2/entity/guid/ab29815d-6d20-44ee-b426-8fba946b72a5/businessmetata?isOverwrite=true'
> \ -H 'cache-control: no-cache' \ -H 'content-type: application/json' \ -H
> 'postman-token: 43107e84-a29c-b1b9-b628-4e0cf4645158' \ -H 'x-xsrf-header:
> \"\"' \ -d '{"Test Multi":{"int":["1221","121222",
> "-99162"]},"Test":{"long":"922337203685477"}}' {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4214) UI: expand/collapse Technical properies of entity audits' tab not working properly
[ https://issues.apache.org/jira/browse/ATLAS-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4214: -- Assignee: Prasad P. Pawar > UI: expand/collapse Technical properies of entity audits' tab not working > properly > -- > > Key: ATLAS-4214 > URL: https://issues.apache.org/jira/browse/ATLAS-4214 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Nikhil Bonte >Assignee: Prasad P. Pawar >Priority: Major > > An entity that has at least 2 audit entries has the following issues with > expanding/collapsing Technical properties- > Expand both audit entries, Technical properties are expanded by default, > # Clicking on 1st audit record's Technical properties will collapse > it(expected) along with changing the icon for 2nd audit record's Technical > properties (it will be still in an expanded state but icon gives feel that it > is collapsed) > # Clicking on the 2nd audit record's Technical properties will > expand/collapse the 1st audit record's Technical properties while it itself > remains expanded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4213) Atlas UI is taking lot of time to load.
[ https://issues.apache.org/jira/browse/ATLAS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4213: --- Attachment: 0001-ATLAS-4213-V2-Atlas-UI-is-taking-lot-of-time-to-load.patch > Atlas UI is taking lot of time to load. > --- > > Key: ATLAS-4213 > URL: https://issues.apache.org/jira/browse/ATLAS-4213 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0 >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4213-Atlas-UI-is-taking-lot-of-time-to-load.fi.patch, > 0001-ATLAS-4213-V1-UIAtlas-UI-is-taking-lot-of-time-to-lo.patch, > 0001-ATLAS-4213-V2-Atlas-UI-is-taking-lot-of-time-to-load.patch > > > Description- > Atlas UI is taking a lot of time to load, after metadata creation part of > scale testing, a large number of classifications & entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4178) [UI] Save and Cancel buttons do not disappear after closing their respective sections in Entity Details page
[ https://issues.apache.org/jira/browse/ATLAS-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4178: --- Fix Version/s: (was: 3.0.0) 2.2.0 > [UI] Save and Cancel buttons do not disappear after closing their respective > sections in Entity Details page > > > Key: ATLAS-4178 > URL: https://issues.apache.org/jira/browse/ATLAS-4178 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4178-UI-Save-and-Cancel-buttons-do-not-disappe.patch, > 0001-ATLAS-4178-UI-V1-Save-and-Cancel-buttons-do-not-disa.patch, > save_cancel_entity_details_page.webm > > > Steps: > 1. Open any section like "User Defined Properties", "Labels" and "Business > Metadata" > 2. Click on Add button > 3.Save and Cancel button should show up > 4. Close the section > You will see the Save and Cancel buttons still remains on the page, and in > certain browser resolutions appear to be misaligned with other elements of > the page. The whole process can be seen in the attached video. They remain on > the page and are clickable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4178) [UI] Save and Cancel buttons do not disappear after closing their respective sections in Entity Details page
[ https://issues.apache.org/jira/browse/ATLAS-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4178: --- Affects Version/s: 3.0.0 > [UI] Save and Cancel buttons do not disappear after closing their respective > sections in Entity Details page > > > Key: ATLAS-4178 > URL: https://issues.apache.org/jira/browse/ATLAS-4178 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 2.2.0 > > Attachments: > 0001-ATLAS-4178-UI-Save-and-Cancel-buttons-do-not-disappe.patch, > 0001-ATLAS-4178-UI-V1-Save-and-Cancel-buttons-do-not-disa.patch, > save_cancel_entity_details_page.webm > > > Steps: > 1. Open any section like "User Defined Properties", "Labels" and "Business > Metadata" > 2. Click on Add button > 3.Save and Cancel button should show up > 4. Close the section > You will see the Save and Cancel buttons still remains on the page, and in > certain browser resolutions appear to be misaligned with other elements of > the page. The whole process can be seen in the attached video. They remain on > the page and are clickable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4202) [Atlas: Audits] When there are no much data to display, it is better to hide in UI instead of displaying no records found
[ https://issues.apache.org/jira/browse/ATLAS-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-4202. Fix Version/s: 3.0.0 Resolution: Won't Fix To maintain the UI consistency, as discuss with [~aman02deep], this bug won't fix. > [Atlas: Audits] When there are no much data to display, it is better to hide > in UI instead of displaying no records found > - > > Key: ATLAS-4202 > URL: https://issues.apache.org/jira/browse/ATLAS-4202 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0 > > Attachments: Screenshot 2021-03-12 at 5.47.52 PM.png, > image-2021-03-12-17-51-44-307.png > > > When a tag is added or updated, there are no much technical details to > display. In such cases, it is better to hide those details in UI instead of > displaying *"No records found"* > *!image-2021-03-12-17-51-44-307.png|width=1187,height=181!* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3887) Consistency and highlighting issues while switching between old and new UI
[ https://issues.apache.org/jira/browse/ATLAS-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-3887: -- Assignee: Prasad P. Pawar (was: Keval Bhatt) > Consistency and highlighting issues while switching between old and new UI > -- > > Key: ATLAS-3887 > URL: https://issues.apache.org/jira/browse/ATLAS-3887 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: classification and glossari does not highlight also > glossary does not show title when switched to new UI.mkv > > > Description:: > When switched from old to new UI, > # Classification and Glossary does not highlight the content, also > # Glossary does not show the title. > PFA video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4229) [Regression] [DSL-Advanced search] If the search query does not match any results, then Atlas UI keep loading forever
[
https://issues.apache.org/jira/browse/ATLAS-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar reassigned ATLAS-4229:
--
Assignee: Prasad P. Pawar
> [Regression] [DSL-Advanced search] If the search query does not match any
> results, then Atlas UI keep loading forever
> --
>
> Key: ATLAS-4229
> URL: https://issues.apache.org/jira/browse/ATLAS-4229
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Prasad P. Pawar
>Priority: Blocker
>
> Observing an issue in DSL (Advanced search), if the search query does not
> match any results, then Atlas UI takes forever to return the results. It just
> wont stop loading.
>
> Whereas if there is a match, the results are returned almost immediately and
> displayed on the UI.
> On further checking, observed the below error in Console tab when the UI
> keeps loading (when there is no match)
> {code:java}
> Uncaught TypeError: Cannot convert undefined or null to object
> at Function.keys ()
> at N.d.tableRender (SearchResultLayoutView.js?bust=1615290982036:332)
> at SearchResultLayoutView.js?bust=1615290982036:365
> at Object.execCb (require.js?bust=1615290982036:1)
> at t.check (require.js?bust=1615290982036:1)
> at t. (require.js?bust=1615290982036:1)
> at require.js?bust=1615290982036:1
> at require.js?bust=1615290982036:1
> at each (require.js?bust=1615290982036:1)
> at t.emit (require.js?bust=1615290982036:1) {code}
> Checked the CURL call directly (case where there are no match)
> Response:
> {code:java}
> {
> "queryType": "DSL",
> "queryText": "`hive_db` where name=\"some_invalid_db\"",
> "approximateCount": -1
> } {code}
> Hence the issue is in UI alone and seems like a regression.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4229) [Regression] [DSL-Advanced search] If the search query does not match any results, then Atlas UI keep loading forever
[
https://issues.apache.org/jira/browse/ATLAS-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4229:
---
Attachment: ATLAS_4229_1.png
> [Regression] [DSL-Advanced search] If the search query does not match any
> results, then Atlas UI keep loading forever
> --
>
> Key: ATLAS-4229
> URL: https://issues.apache.org/jira/browse/ATLAS-4229
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Prasad P. Pawar
>Priority: Blocker
> Attachments:
> 0001-ATLAS-4229-UI-DSL-Advanced-search-If-the-search-quer.patch,
> ATLAS_4229_1.png
>
>
> Observing an issue in DSL (Advanced search), if the search query does not
> match any results, then Atlas UI takes forever to return the results. It just
> wont stop loading.
>
> Whereas if there is a match, the results are returned almost immediately and
> displayed on the UI.
> On further checking, observed the below error in Console tab when the UI
> keeps loading (when there is no match)
> {code:java}
> Uncaught TypeError: Cannot convert undefined or null to object
> at Function.keys ()
> at N.d.tableRender (SearchResultLayoutView.js?bust=1615290982036:332)
> at SearchResultLayoutView.js?bust=1615290982036:365
> at Object.execCb (require.js?bust=1615290982036:1)
> at t.check (require.js?bust=1615290982036:1)
> at t. (require.js?bust=1615290982036:1)
> at require.js?bust=1615290982036:1
> at require.js?bust=1615290982036:1
> at each (require.js?bust=1615290982036:1)
> at t.emit (require.js?bust=1615290982036:1) {code}
> Checked the CURL call directly (case where there are no match)
> Response:
> {code:java}
> {
> "queryType": "DSL",
> "queryText": "`hive_db` where name=\"some_invalid_db\"",
> "approximateCount": -1
> } {code}
> Hence the issue is in UI alone and seems like a regression.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4229) [Regression] [DSL-Advanced search] If the search query does not match any results, then Atlas UI keep loading forever
[
https://issues.apache.org/jira/browse/ATLAS-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4229:
---
Labels: DSL (was: )
> [Regression] [DSL-Advanced search] If the search query does not match any
> results, then Atlas UI keep loading forever
> --
>
> Key: ATLAS-4229
> URL: https://issues.apache.org/jira/browse/ATLAS-4229
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Prasad P. Pawar
>Priority: Blocker
> Labels: DSL
> Attachments:
> 0001-ATLAS-4229-UI-DSL-Advanced-search-If-the-search-quer.patch,
> ATLAS_4229_1.png
>
>
> Observing an issue in DSL (Advanced search), if the search query does not
> match any results, then Atlas UI takes forever to return the results. It just
> wont stop loading.
>
> Whereas if there is a match, the results are returned almost immediately and
> displayed on the UI.
> On further checking, observed the below error in Console tab when the UI
> keeps loading (when there is no match)
> {code:java}
> Uncaught TypeError: Cannot convert undefined or null to object
> at Function.keys ()
> at N.d.tableRender (SearchResultLayoutView.js?bust=1615290982036:332)
> at SearchResultLayoutView.js?bust=1615290982036:365
> at Object.execCb (require.js?bust=1615290982036:1)
> at t.check (require.js?bust=1615290982036:1)
> at t. (require.js?bust=1615290982036:1)
> at require.js?bust=1615290982036:1
> at require.js?bust=1615290982036:1
> at each (require.js?bust=1615290982036:1)
> at t.emit (require.js?bust=1615290982036:1) {code}
> Checked the CURL call directly (case where there are no match)
> Response:
> {code:java}
> {
> "queryType": "DSL",
> "queryText": "`hive_db` where name=\"some_invalid_db\"",
> "approximateCount": -1
> } {code}
> Hence the issue is in UI alone and seems like a regression.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4224) UI : Redirect Atlas UI to login/index page when session is expired in backend.
[ https://issues.apache.org/jira/browse/ATLAS-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4224: --- Fix Version/s: 3.0.0 > UI : Redirect Atlas UI to login/index page when session is expired in backend. > -- > > Key: ATLAS-4224 > URL: https://issues.apache.org/jira/browse/ATLAS-4224 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4224-UI-Redirect-Atlas-UI-to-login-index-page-.patch > > > Redirect Atlas UI to login/index page when session is expired in backend when > cookie is expired or deleted instead of showing notification in Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4224) UI : Redirect Atlas UI to login/index page when session is expired in backend.
[ https://issues.apache.org/jira/browse/ATLAS-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4224: --- Fix Version/s: 2.2.0 > UI : Redirect Atlas UI to login/index page when session is expired in backend. > -- > > Key: ATLAS-4224 > URL: https://issues.apache.org/jira/browse/ATLAS-4224 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4224-UI-Redirect-Atlas-UI-to-login-index-page-.patch > > > Redirect Atlas UI to login/index page when session is expired in backend when > cookie is expired or deleted instead of showing notification in Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4224) UI : Redirect Atlas UI to login/index page when session is expired in backend.
[ https://issues.apache.org/jira/browse/ATLAS-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4224: --- Affects Version/s: 2.1.0 > UI : Redirect Atlas UI to login/index page when session is expired in backend. > -- > > Key: ATLAS-4224 > URL: https://issues.apache.org/jira/browse/ATLAS-4224 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4224-UI-Redirect-Atlas-UI-to-login-index-page-.patch > > > Redirect Atlas UI to login/index page when session is expired in backend when > cookie is expired or deleted instead of showing notification in Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4214) UI: expand/collapse Technical properies of entity audits' tab not working properly
[ https://issues.apache.org/jira/browse/ATLAS-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4214: --- Fix Version/s: 2.0.0 3.0.0 > UI: expand/collapse Technical properies of entity audits' tab not working > properly > -- > > Key: ATLAS-4214 > URL: https://issues.apache.org/jira/browse/ATLAS-4214 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 2.0.0, 3.0.0 > > Attachments: > 0001-ATLAS-4214-UI-expand-collapse-Technical-properies-of.patch > > > An entity that has at least 2 audit entries has the following issues with > expanding/collapsing Technical properties- > Expand both audit entries, Technical properties are expanded by default, > # Clicking on 1st audit record's Technical properties will collapse > it(expected) along with changing the icon for 2nd audit record's Technical > properties (it will be still in an expanded state but icon gives feel that it > is collapsed) > # Clicking on the 2nd audit record's Technical properties will > expand/collapse the 1st audit record's Technical properties while it itself > remains expanded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4214) UI: expand/collapse Technical properies of entity audits' tab not working properly
[ https://issues.apache.org/jira/browse/ATLAS-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4214: --- Affects Version/s: 2.1.0 > UI: expand/collapse Technical properies of entity audits' tab not working > properly > -- > > Key: ATLAS-4214 > URL: https://issues.apache.org/jira/browse/ATLAS-4214 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4214-UI-expand-collapse-Technical-properies-of.patch > > > An entity that has at least 2 audit entries has the following issues with > expanding/collapsing Technical properties- > Expand both audit entries, Technical properties are expanded by default, > # Clicking on 1st audit record's Technical properties will collapse > it(expected) along with changing the icon for 2nd audit record's Technical > properties (it will be still in an expanded state but icon gives feel that it > is collapsed) > # Clicking on the 2nd audit record's Technical properties will > expand/collapse the 1st audit record's Technical properties while it itself > remains expanded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4214) UI: expand/collapse Technical properies of entity audits' tab not working properly
[ https://issues.apache.org/jira/browse/ATLAS-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4214: --- Fix Version/s: (was: 2.0.0) 2.2.0 > UI: expand/collapse Technical properies of entity audits' tab not working > properly > -- > > Key: ATLAS-4214 > URL: https://issues.apache.org/jira/browse/ATLAS-4214 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-4214-UI-expand-collapse-Technical-properies-of.patch > > > An entity that has at least 2 audit entries has the following issues with > expanding/collapsing Technical properties- > Expand both audit entries, Technical properties are expanded by default, > # Clicking on 1st audit record's Technical properties will collapse > it(expected) along with changing the icon for 2nd audit record's Technical > properties (it will be still in an expanded state but icon gives feel that it > is collapsed) > # Clicking on the 2nd audit record's Technical properties will > expand/collapse the 1st audit record's Technical properties while it itself > remains expanded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4201) UI: Add attributes modal api hits when no attributes are added on Classification detail page.
[ https://issues.apache.org/jira/browse/ATLAS-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4201: --- Affects Version/s: 2.1.0 > UI: Add attributes modal api hits when no attributes are added on > Classification detail page. > - > > Key: ATLAS-4201 > URL: https://issues.apache.org/jira/browse/ATLAS-4201 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Labels: attributes, classification > Attachments: > 0001-ATLAS-4201-UI-Add-attributes-modal-api-hits-when-no-.patch, > AddAttributesField.png, AddButtonEnabled.png, Api_SuccessMessage.png > > > Steps: > 1) Add attributes by clicking on the attribute + button on the classification > detail page. > Add Attribute modal opens with default 1 attribute field, "Add" button of the > modal is disabled. > 2) Click on the "Add New Attributes" button. > Additional attribute field is added, with remove attribute field buttons. > 3) Remove all the attributes fields by clicking on the remove buttons. > 4) Add button gets enable (should be disabled), refer to the attached image. > 5) Click on Add button, API is hit, an Attribute added success message is > shown, refer to the attached image. > Expectation: > Show Validation message on "Add" Button click of the modal: "No attribute is > added" or Disable the "Add" Button of modal or At least keep one Attribute > field in the modal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4168) Overlapping "Switch to Beta UI" link on pagination
[ https://issues.apache.org/jira/browse/ATLAS-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4168: --- Attachment: 0001-ATLAS-4168-v1-Overlapping-Switch-to-Beta-UI-link-on-.patch > Overlapping "Switch to Beta UI" link on pagination > -- > > Key: ATLAS-4168 > URL: https://issues.apache.org/jira/browse/ATLAS-4168 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Labels: Atlas-UI > Attachments: > 0001-ATLAS-4168-Overlapping-Switch-to-Beta-UI-link-on-pag.patch, > 0001-ATLAS-4168-v1-Overlapping-Switch-to-Beta-UI-link-on-.patch, > 4168_1fix.png, 4168_2Fixed.png, screenshot-newtab-2021.02.18-18_42_14.png > > > “Switch to Beta UI” link at the bottom right of the page overlaps pagination > links in search results page . > PFA -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space
[ https://issues.apache.org/jira/browse/ATLAS-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-3891: -- Assignee: Prasad P. Pawar (was: Keval Bhatt) > UI: Quick search cards for ease of search and utilization of white space > > > Key: ATLAS-3891 > URL: https://issues.apache.org/jira/browse/ATLAS-3891 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Keval Bhatt >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0 > > Attachments: search_dashboard_roun...@2x.png > > > Example: > > !search_dashboard_roun...@2x.png|width=591,height=332! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space
[ https://issues.apache.org/jira/browse/ATLAS-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3891: --- Priority: Minor (was: Major) > UI: Quick search cards for ease of search and utilization of white space > > > Key: ATLAS-3891 > URL: https://issues.apache.org/jira/browse/ATLAS-3891 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Keval Bhatt >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0 > > Attachments: search_dashboard_roun...@2x.png > > > Example: > > !search_dashboard_roun...@2x.png|width=591,height=332! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space
[ https://issues.apache.org/jira/browse/ATLAS-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315929#comment-17315929 ] Prasad P. Pawar commented on ATLAS-3891: As this is an improvement on the Home page of ATLAS UI, changing the priority to a minor. > UI: Quick search cards for ease of search and utilization of white space > > > Key: ATLAS-3891 > URL: https://issues.apache.org/jira/browse/ATLAS-3891 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Keval Bhatt >Assignee: Prasad P. Pawar >Priority: Minor > Fix For: 3.0.0 > > Attachments: search_dashboard_roun...@2x.png > > > Example: > > !search_dashboard_roun...@2x.png|width=591,height=332! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space
[ https://issues.apache.org/jira/browse/ATLAS-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3891: --- Comment: was deleted (was: As this is an improvement on the Home page of ATLAS UI, changing the priority to a minor.) > UI: Quick search cards for ease of search and utilization of white space > > > Key: ATLAS-3891 > URL: https://issues.apache.org/jira/browse/ATLAS-3891 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Keval Bhatt >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0 > > Attachments: search_dashboard_roun...@2x.png > > > Example: > > !search_dashboard_roun...@2x.png|width=591,height=332! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space
[ https://issues.apache.org/jira/browse/ATLAS-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3891: --- Priority: Major (was: Minor) > UI: Quick search cards for ease of search and utilization of white space > > > Key: ATLAS-3891 > URL: https://issues.apache.org/jira/browse/ATLAS-3891 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Keval Bhatt >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0 > > Attachments: search_dashboard_roun...@2x.png > > > Example: > > !search_dashboard_roun...@2x.png|width=591,height=332! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4238) Quick Search: handle special characters to get correct results
[
https://issues.apache.org/jira/browse/ATLAS-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4238:
---
Attachment: 0001-ATLAS-4238-UI-Quick-Search-handle-special-characters.patch
> Quick Search: handle special characters to get correct results
> --
>
> Key: ATLAS-4238
> URL: https://issues.apache.org/jira/browse/ATLAS-4238
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Labels: quicksearch
> Attachments:
> 0001-ATLAS-4238-UI-Quick-Search-handle-special-characters.patch
>
>
> During freetext/quick search,
> wildcard '*' is appended after the search string from UI.
> But if attribute search value has "+-&|!(){}[]^"~?:" special characters,
> then '*' will not be appended to get the correct result.
> ('*' is removed because for TEXT type attribute tokenize the value on special
> characters)
> We need to handle all the special characters which tokenize the string
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4238) Quick Search: handle special characters to get correct results
[
https://issues.apache.org/jira/browse/ATLAS-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316900#comment-17316900
]
Prasad P. Pawar commented on ATLAS-4238:
Hi,
>From UI end, we are not handling any special characters check, also not
>appending any "*" with the quick search string. This change is present in the
>uploaded 0001-ATLAS-4238-UI-Quick-Search-handle-special-characters.patch file.
> Quick Search: handle special characters to get correct results
> --
>
> Key: ATLAS-4238
> URL: https://issues.apache.org/jira/browse/ATLAS-4238
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
> Labels: quicksearch
> Attachments:
> 0001-ATLAS-4238-UI-Quick-Search-handle-special-characters.patch
>
>
> During freetext/quick search,
> wildcard '*' is appended after the search string from UI.
> But if attribute search value has "+-&|!(){}[]^"~?:" special characters,
> then '*' will not be appended to get the correct result.
> ('*' is removed because for TEXT type attribute tokenize the value on special
> characters)
> We need to handle all the special characters which tokenize the string
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3887) Consistency and highlighting issues while switching between old and new UI
[ https://issues.apache.org/jira/browse/ATLAS-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3887: --- Description: Description:: When switched from old to new UI, # Classification and Glossary does not highlight the content, also # Glossary does not show the title. # On Old UI, glossary tab, click on term category toggle button, on click - button gets toggled to Category - Import/Download glossary button gets disabled. Now switch to New-UI on left side Glossary panel shows Category tree - button dosent toggled to Category (bug) - import/Download Glossary options is enabled (bug) PFA video was: Description:: When switched from old to new UI, # Classification and Glossary does not highlight the content, also # Glossary does not show the title. PFA video > Consistency and highlighting issues while switching between old and new UI > -- > > Key: ATLAS-3887 > URL: https://issues.apache.org/jira/browse/ATLAS-3887 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Durga Kadam >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: classification and glossari does not highlight also > glossary does not show title when switched to new UI.mkv > > > Description:: > When switched from old to new UI, > # Classification and Glossary does not highlight the content, also > # Glossary does not show the title. > # On Old UI, glossary tab, click on term category toggle button, > on click > - button gets toggled to Category > - Import/Download glossary button gets disabled. > Now switch to New-UI > on left side Glossary panel shows Category tree > - button dosent toggled to Category (bug) > - import/Download Glossary options is enabled (bug) > PFA video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4240) UI: Some Categories are not shown in the tree that matches the search string of search bar.
Prasad P. Pawar created ATLAS-4240: -- Summary: 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: Bug Reporter: Prasad P. Pawar 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] [Assigned] (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 reassigned ATLAS-4240: -- Assignee: Prasad P. Pawar > 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: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: 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-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: --- Attachment: CategoryList.png Old-ui_Category_Bug.png Old-ui_Category_bug_2.png > 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: Bug >Reporter: Prasad P. Pawar >Priority: Major > Attachments: 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-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: --- Labels: categories (was: ) > 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: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: categories > Attachments: 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-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: --- Component/s: atlas-webui > 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: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: categories > Attachments: 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-3903) New UI: Glossary category not reflected in the tree after creation.
[ https://issues.apache.org/jira/browse/ATLAS-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3903: --- Component/s: atlas-webui > New UI: Glossary category not reflected in the tree after creation. > --- > > Key: ATLAS-3903 > URL: https://issues.apache.org/jira/browse/ATLAS-3903 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Keval Bhatt >Assignee: Prasad P. Pawar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: Category_does_not_reflect_in_dropdown.mkv > > > Steps reproduce the issue: > * Create the glossary > * Click on "..." to create the category > * After adding category details click on save > Due to regression newly created category is not rendered in the tree view. if > a user clicks on the refresh button then it is visible. > Please check the attached video for a better understanding. > [^Category_does_not_reflect_in_dropdown.mkv] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.
[ https://issues.apache.org/jira/browse/ATLAS-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3903: --- Labels: categories (was: ) > New UI: Glossary category not reflected in the tree after creation. > --- > > Key: ATLAS-3903 > URL: https://issues.apache.org/jira/browse/ATLAS-3903 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Keval Bhatt >Assignee: Prasad P. Pawar >Priority: Major > Labels: categories > Fix For: 3.0.0, 2.2.0 > > Attachments: Category_does_not_reflect_in_dropdown.mkv > > > Steps reproduce the issue: > * Create the glossary > * Click on "..." to create the category > * After adding category details click on save > Due to regression newly created category is not rendered in the tree view. if > a user clicks on the refresh button then it is visible. > Please check the attached video for a better understanding. > [^Category_does_not_reflect_in_dropdown.mkv] -- 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: --- Parent: ATLAS-3903 Issue Type: Sub-task (was: Bug) > 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 > Attachments: 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] [Comment Edited] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.
[ https://issues.apache.org/jira/browse/ATLAS-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318026#comment-17318026 ] Prasad P. Pawar edited comment on ATLAS-3903 at 4/9/21, 2:20 PM: - Hi, This fix is provided in the uploaded patch, also [ ATLAS-4240] is merged in this patch. was (Author: prasadpp13): Hi, This fix is provided in the uploaded patch, also [ ATLAS-4240|https://issues.apache.org/jira/browse/ATLAS-4240] is merged in this patch. > New UI: Glossary category not reflected in the tree after creation. > --- > > Key: ATLAS-3903 > URL: https://issues.apache.org/jira/browse/ATLAS-3903 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Keval Bhatt >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, > Category_does_not_reflect_in_dropdown.mkv > > > Steps reproduce the issue: > * Create the glossary > * Click on "..." to create the category > * After adding category details click on save > Due to regression newly created category is not rendered in the tree view. if > a user clicks on the refresh button then it is visible. > Please check the attached video for a better understanding. > [^Category_does_not_reflect_in_dropdown.mkv] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.
[ https://issues.apache.org/jira/browse/ATLAS-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318026#comment-17318026 ] Prasad P. Pawar edited comment on ATLAS-3903 at 4/9/21, 2:20 PM: - Hi, This fix is provided in the uploaded patch, also [ ATLAS-4240|https://issues.apache.org/jira/browse/ATLAS-4240] is merged in this patch. was (Author: prasadpp13): Hi, This fix is provided in the uploaded patch, also [ ATLAS-4240 |https://issues.apache.org/jira/browse/ATLAS-4240] is merged in this patch. > New UI: Glossary category not reflected in the tree after creation. > --- > > Key: ATLAS-3903 > URL: https://issues.apache.org/jira/browse/ATLAS-3903 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Keval Bhatt >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, > Category_does_not_reflect_in_dropdown.mkv > > > Steps reproduce the issue: > * Create the glossary > * Click on "..." to create the category > * After adding category details click on save > Due to regression newly created category is not rendered in the tree view. if > a user clicks on the refresh button then it is visible. > Please check the attached video for a better understanding. > [^Category_does_not_reflect_in_dropdown.mkv] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.
[ https://issues.apache.org/jira/browse/ATLAS-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318026#comment-17318026 ] Prasad P. Pawar commented on ATLAS-3903: Hi, This fix is provided in the uploaded patch, also [ ATLAS-4240 |https://issues.apache.org/jira/browse/ATLAS-4240] is merged in this patch. > New UI: Glossary category not reflected in the tree after creation. > --- > > Key: ATLAS-3903 > URL: https://issues.apache.org/jira/browse/ATLAS-3903 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Keval Bhatt >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, > Category_does_not_reflect_in_dropdown.mkv > > > Steps reproduce the issue: > * Create the glossary > * Click on "..." to create the category > * After adding category details click on save > Due to regression newly created category is not rendered in the tree view. if > a user clicks on the refresh button then it is visible. > Please check the attached video for a better understanding. > [^Category_does_not_reflect_in_dropdown.mkv] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17318028#comment-17318028 ] Prasad P. Pawar commented on ATLAS-4240: this fix is merged in [ATLAS-3903| https://issues.apache.org/jira/browse/ATLAS-3903] > 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 > 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-3903) New UI: Glossary category not reflected in the tree after creation.
[ https://issues.apache.org/jira/browse/ATLAS-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-3903: --- Attachment: 0001-ATLAS-3903-UI-v1-Glossary-category-not-reflected-in-.patch > New UI: Glossary category not reflected in the tree after creation. > --- > > Key: ATLAS-3903 > URL: https://issues.apache.org/jira/browse/ATLAS-3903 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Keval Bhatt >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, > 0001-ATLAS-3903-UI-v1-Glossary-category-not-reflected-in-.patch, > Category_does_not_reflect_in_dropdown.mkv > > > Steps reproduce the issue: > * Create the glossary > * Click on "..." to create the category > * After adding category details click on save > Due to regression newly created category is not rendered in the tree view. if > a user clicks on the refresh button then it is visible. > Please check the attached video for a better understanding. > [^Category_does_not_reflect_in_dropdown.mkv] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
Prasad P. Pawar created ATLAS-4244: -- Summary: Atlas: UI Lineage tab gives Uncaught TypeError Key: ATLAS-4244 URL: https://issues.apache.org/jira/browse/ATLAS-4244 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar 1) The lineage tab gives Uncaught TypeError in the console panel. LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) 2) createTime & modifiedTime show incorrect date value of entity detail page, when default values are "0" (ENGESC-3036-manulife branch). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Description: 1) The lineage tab gives Uncaught TypeError in the console panel. (ENGESC-3036-manulife branch, HDP-3.1-maint branch, cdpd master branch & CDH-7.1-maint branch) LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) 2) createTime & modifiedTime show incorrect date value of entity detail page, when default values are "0" (ENGESC-3036-manulife branch). was: 1) The lineage tab gives Uncaught TypeError in the console panel. LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) 2) createTime & modifiedTime show incorrect date value of entity detail page, when default values are "0" (ENGESC-3036-manulife branch). > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ENGESC-3036-manulife-ATLAS-UI-Lineage-without-displa.patch, > 0001-HDP-3.1-maint-ATLAS-UI-Lineage-without-displayText-k.patch > > > 1) The lineage tab gives Uncaught TypeError in the console panel. > (ENGESC-3036-manulife branch, HDP-3.1-maint branch, cdpd master branch & > CDH-7.1-maint branch) > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) > 2) createTime & modifiedTime show incorrect date value of entity detail page, > when default values are "0" (ENGESC-3036-manulife branch). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Attachment: 0001-HDP-3.1-maint-ATLAS-UI-Lineage-without-displayText-k.patch > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ENGESC-3036-manulife-ATLAS-UI-Lineage-without-displa.patch, > 0001-HDP-3.1-maint-ATLAS-UI-Lineage-without-displayText-k.patch > > > 1) The lineage tab gives Uncaught TypeError in the console panel. > (ENGESC-3036-manulife branch, HDP-3.1-maint branch, cdpd master branch & > CDH-7.1-maint branch) > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) > 2) createTime & modifiedTime show incorrect date value of entity detail page, > when default values are "0" (ENGESC-3036-manulife branch). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Attachment: 0001-ENGESC-3036-manulife-ATLAS-UI-Lineage-without-displa.patch > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ENGESC-3036-manulife-ATLAS-UI-Lineage-without-displa.patch, > 0001-HDP-3.1-maint-ATLAS-UI-Lineage-without-displayText-k.patch > > > 1) The lineage tab gives Uncaught TypeError in the console panel. > (ENGESC-3036-manulife branch, HDP-3.1-maint branch, cdpd master branch & > CDH-7.1-maint branch) > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) > 2) createTime & modifiedTime show incorrect date value of entity detail page, > when default values are "0" (ENGESC-3036-manulife branch). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Attachment: 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch, > 0001-ENGESC-3036-manulife-ATLAS-UI-Lineage-without-displa.patch, > 0001-HDP-3.1-maint-ATLAS-UI-Lineage-without-displayText-k.patch > > > 1) The lineage tab gives Uncaught TypeError in the console panel. > (ENGESC-3036-manulife branch, HDP-3.1-maint branch, cdpd master branch & > CDH-7.1-maint branch) > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) > 2) createTime & modifiedTime show incorrect date value of entity detail page, > when default values are "0" (ENGESC-3036-manulife branch). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Attachment: (was: 0001-HDP-3.1-maint-ATLAS-UI-Lineage-without-displayText-k.patch) > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch > > > 1) The lineage tab gives Uncaught TypeError in the console panel. > (ENGESC-3036-manulife branch, HDP-3.1-maint branch, cdpd master branch & > CDH-7.1-maint branch) > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) > 2) createTime & modifiedTime show incorrect date value of entity detail page, > when default values are "0" (ENGESC-3036-manulife branch). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Description: 1) The lineage tab gives Uncaught TypeError in the console panel. LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) was: 1) The lineage tab gives Uncaught TypeError in the console panel. (ENGESC-3036-manulife branch, HDP-3.1-maint branch, cdpd master branch & CDH-7.1-maint branch) LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) 2) createTime & modifiedTime show incorrect date value of entity detail page, when default values are "0" (ENGESC-3036-manulife branch). > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch > > > 1) The lineage tab gives Uncaught TypeError in the console panel. > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Attachment: (was: 0001-ENGESC-3036-manulife-ATLAS-UI-Lineage-without-displa.patch) > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch > > > 1) The lineage tab gives Uncaught TypeError in the console panel. > (ENGESC-3036-manulife branch, HDP-3.1-maint branch, cdpd master branch & > CDH-7.1-maint branch) > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) > 2) createTime & modifiedTime show incorrect date value of entity detail page, > when default values are "0" (ENGESC-3036-manulife branch). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320771#comment-17320771 ] Prasad P. Pawar commented on ATLAS-4244: Hi, The uploaded patch has this Lineage fix > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch > > > 1) The lineage tab gives Uncaught TypeError in the console panel. > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Description: 1) The lineage tab gives Uncaught TypeError in the console panel, when lineage without displayText & attribute keys. LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) was: 1) The lineage tab gives Uncaught TypeError in the console panel. LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch, 4244_bug.png > > > 1) The lineage tab gives Uncaught TypeError in the console panel, when > lineage without displayText & attribute keys. > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Attachment: 4244_bug.png > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch, 4244_bug.png > > > 1) The lineage tab gives Uncaught TypeError in the console panel, when > lineage without displayText & attribute keys. > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4244) Atlas: UI Lineage tab gives Uncaught TypeError
[ https://issues.apache.org/jira/browse/ATLAS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4244: --- Description: 1) The lineage tab gives Uncaught TypeError in the console panel, when lineage without displayText & attribute keys. (refer 4244_bug.png) LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) was: 1) The lineage tab gives Uncaught TypeError in the console panel, when lineage without displayText & attribute keys. LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read property 'trunc' of undefined at N.d. (LineageLayoutView.js?bust=1576185031805:208) at LineageLayoutView.js?bust=1576185031805:222 at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) at N.d.crateLineageRelationshipHashMap (LineageLayoutView.js?bust=1576185031805:221) at Object.success (LineageLayoutView.js?bust=1576185031805:147) at k (jquery.min.js?bust=1576185031805:2) at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) at d (jquery.min.js?bust=1576185031805:3) at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) > Atlas: UI Lineage tab gives Uncaught TypeError > -- > > Key: ATLAS-4244 > URL: https://issues.apache.org/jira/browse/ATLAS-4244 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-UI-Lineage-without-displayText-key-fixed.patch, 4244_bug.png > > > 1) The lineage tab gives Uncaught TypeError in the console panel, when > lineage without displayText & attribute keys. (refer 4244_bug.png) > LineageLayoutView.js?bust=1576185031805:208 Uncaught TypeError: Cannot read > property 'trunc' of undefined > at N.d. (LineageLayoutView.js?bust=1576185031805:208) > at LineageLayoutView.js?bust=1576185031805:222 > at Function.s.each.s.forEach (underscore-min.js?bust=1576185031805:1) > at N.d.crateLineageRelationshipHashMap > (LineageLayoutView.js?bust=1576185031805:221) > at Object.success (LineageLayoutView.js?bust=1576185031805:147) > at k (jquery.min.js?bust=1576185031805:2) > at Object.fireWith [as resolveWith] (jquery.min.js?bust=1576185031805:2) > at d (jquery.min.js?bust=1576185031805:3) > at XMLHttpRequest. (jquery.min.js?bust=1576185031805:3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4243) UI: Legend in lineage gets duplicated
[ https://issues.apache.org/jira/browse/ATLAS-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4243: -- Assignee: Prasad P. Pawar > 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: 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)
