[jira] [Created] (ATLAS-3154) UI - Lineage PNG export not working on Firefox
Rahul Kurup created ATLAS-3154: -- Summary: UI - Lineage PNG export not working on Firefox Key: ATLAS-3154 URL: https://issues.apache.org/jira/browse/ATLAS-3154 Project: Atlas Issue Type: Sub-task Reporter: Rahul Kurup Fix For: 2.0.0 When we click the PNG export button in Firefox (66.0.3), the message prompt "Lineage will be downloaded in a moment." appears but nothing happens. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3155) UI - IE-11 - Name entry not clickable
Rahul Kurup created ATLAS-3155: -- Summary: UI - IE-11 - Name entry not clickable Key: ATLAS-3155 URL: https://issues.apache.org/jira/browse/ATLAS-3155 Project: Atlas Issue Type: Sub-task Reporter: Rahul Kurup Fix For: 2.0.0 In the search results page, when we try to click the 'Name' column value of any entry, nothing happens. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3156) No loading animation while creating or deleting a Classification
Rahul Kurup created ATLAS-3156: -- Summary: No loading animation while creating or deleting a Classification Key: ATLAS-3156 URL: https://issues.apache.org/jira/browse/ATLAS-3156 Project: Atlas Issue Type: Improvement Reporter: Rahul Kurup While creating a Classification, there is no loading animation or any indication to the user that the creation process is underway. The user only gets a notification that the creation process is complete. If for some reason the creation process takes a long while, then this lack of indication might confuse the user into thinking that nothing is happening on clicking the 'Create' button. This same issue exists when trying to delete a classification. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3155) UI - IE-11 - Name entry not clickable
[ https://issues.apache.org/jira/browse/ATLAS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3155: --- Attachment: ie11_name_issue.jpg > UI - IE-11 - Name entry not clickable > - > > Key: ATLAS-3155 > URL: https://issues.apache.org/jira/browse/ATLAS-3155 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Priority: Major > Fix For: 2.0.0 > > Attachments: ie11_name_issue.jpg > > > In the search results page, when we try to click the 'Name' column value of > any entry, nothing happens. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3159) UI : Add Reset button for Lienage
[ https://issues.apache.org/jira/browse/ATLAS-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825148#comment-16825148 ] Rahul Kurup commented on ATLAS-3159: +1 for the patch. > UI : Add Reset button for Lienage > - > > Key: ATLAS-3159 > URL: https://issues.apache.org/jira/browse/ATLAS-3159 > Project: Atlas > Issue Type: Sub-task >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3159.patch, ATLAS-3159_1.patch, Screen Shot > 2019-04-24 at 12.34.54 PM.png > > > After moving node if user want to reset the Lineage they click on reset > button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3170) Advanced Search does not allow saving of searcher unless search is performed once.
Rahul Kurup created ATLAS-3170: -- Summary: Advanced Search does not allow saving of searcher unless search is performed once. Key: ATLAS-3170 URL: https://issues.apache.org/jira/browse/ATLAS-3170 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Fix For: 1.2.0, 2.0.0 Steps: In Advanced Search column # Enter value for "Search By Type" # Enter value for "Search By Query" # Click on "Save As" Expected result: The "Create your favorite search" should appear. Actual result : We get the message "Please select at least one filter" However, if you execute the search with the values from steps 1 and 2, and then click on "Save As" the expected result is achieved. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3170) Advanced Search does not allow saving of searches unless search is performed once.
[ https://issues.apache.org/jira/browse/ATLAS-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3170: --- Summary: Advanced Search does not allow saving of searches unless search is performed once. (was: Advanced Search does not allow saving of searcher unless search is performed once.) > Advanced Search does not allow saving of searches unless search is performed > once. > -- > > Key: ATLAS-3170 > URL: https://issues.apache.org/jira/browse/ATLAS-3170 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > Fix For: 1.2.0, 2.0.0 > > > Steps: > In Advanced Search column > # Enter value for "Search By Type" > # Enter value for "Search By Query" > # Click on "Save As" > Expected result: The "Create your favorite search" should appear. > Actual result : We get the message "Please select at least one filter" > However, if you execute the search with the values from steps 1 and 2, and > then click on "Save As" the expected result is achieved. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3186) UI: Background navigation is possible when "Advanced Search Queries" popup is active.
Rahul Kurup created ATLAS-3186: -- Summary: UI: Background navigation is possible when "Advanced Search Queries" popup is active. Key: ATLAS-3186 URL: https://issues.apache.org/jira/browse/ATLAS-3186 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup 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 (v7.6.3#76005)
[jira] [Updated] (ATLAS-3170) UI: Advanced Search does not allow saving of searches unless search is performed once.
[ https://issues.apache.org/jira/browse/ATLAS-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3170: --- Summary: UI: Advanced Search does not allow saving of searches unless search is performed once. (was: Advanced Search does not allow saving of searches unless search is performed once.) > UI: Advanced Search does not allow saving of searches unless search is > performed once. > -- > > Key: ATLAS-3170 > URL: https://issues.apache.org/jira/browse/ATLAS-3170 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > Fix For: 1.2.0, 2.0.0 > > > Steps: > In Advanced Search column > # Enter value for "Search By Type" > # Enter value for "Search By Query" > # Click on "Save As" > Expected result: The "Create your favorite search" should appear. > Actual result : We get the message "Please select at least one filter" > However, if you execute the search with the values from steps 1 and 2, and > then click on "Save As" the expected result is achieved. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3156) UI:No loading animation while creating or deleting a Classification
[ https://issues.apache.org/jira/browse/ATLAS-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3156: --- Summary: UI:No loading animation while creating or deleting a Classification (was: No loading animation while creating or deleting a Classification) > UI:No loading animation while creating or deleting a Classification > --- > > Key: ATLAS-3156 > URL: https://issues.apache.org/jira/browse/ATLAS-3156 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Priority: Minor > > While creating a Classification, there is no loading animation or any > indication to the user that the creation process is underway. The user only > gets a notification that the creation process is complete. If for some reason > the creation process takes a long while, then this lack of indication might > confuse the user into thinking that nothing is happening on clicking the > 'Create' button. > > This same issue exists when trying to delete a classification. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3191) UI: Improvement Suggestions for Glossary, Classification Validity and Search page Results display header.
Rahul Kurup created ATLAS-3191: -- Summary: UI: Improvement Suggestions for Glossary, Classification Validity and Search page Results display header. Key: ATLAS-3191 URL: https://issues.apache.org/jira/browse/ATLAS-3191 Project: Atlas Issue Type: Improvement Reporter: Rahul Kurup Attachments: dupterms.jpg, dyntextquery.jpg 1. Glossary: It is possible to create duplicate terms for a Glossary by using spacing in the beginning (see attached screenshot !dupterms.jpg! ). This should be removed. 2. Classification Validity Period: In UI, there should be an indicator/disclaimer that says it is only enforced by other plugins (Ranger etc) or at least a help icon linking to a page that explains the functioning of the validity period just like Advanced Search. 3. Search page Results display header: Dynamic text expansion should be implemented for large queries in entity Search page. For example, in the attached screenshot ( !dyntextquery.jpg! ) the large query can be compressed using dynamic text. On click or hover, we should see the whole query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3191) UI: Improvement Suggestions for Glossary, Classification Validity and Search page Results display header.
[ https://issues.apache.org/jira/browse/ATLAS-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3191: --- Description: 1. Glossary: It is possible to create duplicate terms for a Glossary by using spacing in the beginning (see attached screenshot !dupterms.jpg|height=250,width=250! ). This should be removed. 2. Classification Validity Period: In UI, there should be an indicator/disclaimer that says it is only enforced by other plugins (Ranger etc) or at least a help icon linking to a page that explains the functioning of the validity period just like Advanced Search. 3. Search page Results display header: Dynamic text expansion should be implemented for large queries in entity Search page. For example, in the attached screenshot ( !dyntextquery.jpg|height=250,width=250! ) the large query can be compressed using dynamic text. On click or hover, we should see the whole query. was: 1. Glossary: It is possible to create duplicate terms for a Glossary by using spacing in the beginning (see attached screenshot !dupterms.jpg! ). This should be removed. 2. Classification Validity Period: In UI, there should be an indicator/disclaimer that says it is only enforced by other plugins (Ranger etc) or at least a help icon linking to a page that explains the functioning of the validity period just like Advanced Search. 3. Search page Results display header: Dynamic text expansion should be implemented for large queries in entity Search page. For example, in the attached screenshot ( !dyntextquery.jpg! ) the large query can be compressed using dynamic text. On click or hover, we should see the whole query. > UI: Improvement Suggestions for Glossary, Classification Validity and Search > page Results display header. > - > > Key: ATLAS-3191 > URL: https://issues.apache.org/jira/browse/ATLAS-3191 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Priority: Minor > Attachments: dupterms.jpg, dyntextquery.jpg > > > 1. Glossary: It is possible to create duplicate terms for a Glossary by using > spacing in the beginning (see attached screenshot > !dupterms.jpg|height=250,width=250! ). This should be removed. > 2. Classification Validity Period: In UI, there should be an > indicator/disclaimer that says it is only enforced by other plugins (Ranger > etc) or at least a help icon linking to a page that explains the functioning > of the validity period just like Advanced Search. > 3. Search page Results display header: Dynamic text expansion should be > implemented for large queries in entity Search page. For example, in the > attached screenshot ( !dyntextquery.jpg|height=250,width=250! ) the large > query can be compressed using dynamic text. On click or hover, we should see > the whole query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3191) UI: Improvement Suggestions for Glossary, Classification Validity and Search page Results display header.
[ https://issues.apache.org/jira/browse/ATLAS-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3191: --- Description: 1. Glossary: It is possible to create duplicate terms for a Glossary by using spacing in the beginning (see screenshot below). This should be removed. !dupterms.jpg|height=250,width=500! 2. Classification Validity Period: In UI, there should be an indicator/disclaimer that says it is only enforced by other plugins (Ranger etc) or at least a help icon linking to a page that explains the functioning of the validity period just like Advanced Search. 3. Search page Results display header: Dynamic text expansion should be implemented for large queries in entity Search page. For example, in the screenshot below, the large query can be compressed using dynamic text. On click or hover, we should see the whole query. !dyntextquery.jpg|height=250,width=500! was: 1. Glossary: It is possible to create duplicate terms for a Glossary by using spacing in the beginning (see attached screenshot !dupterms.jpg|height=250,width=250! ). This should be removed. 2. Classification Validity Period: In UI, there should be an indicator/disclaimer that says it is only enforced by other plugins (Ranger etc) or at least a help icon linking to a page that explains the functioning of the validity period just like Advanced Search. 3. Search page Results display header: Dynamic text expansion should be implemented for large queries in entity Search page. For example, in the attached screenshot ( !dyntextquery.jpg|height=250,width=250! ) the large query can be compressed using dynamic text. On click or hover, we should see the whole query. > UI: Improvement Suggestions for Glossary, Classification Validity and Search > page Results display header. > - > > Key: ATLAS-3191 > URL: https://issues.apache.org/jira/browse/ATLAS-3191 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Priority: Minor > Attachments: dupterms.jpg, dyntextquery.jpg > > > 1. Glossary: It is possible to create duplicate terms for a Glossary by using > spacing in the beginning (see screenshot below). This should be removed. > !dupterms.jpg|height=250,width=500! > 2. Classification Validity Period: In UI, there should be an > indicator/disclaimer that says it is only enforced by other plugins (Ranger > etc) or at least a help icon linking to a page that explains the functioning > of the validity period just like Advanced Search. > 3. Search page Results display header: Dynamic text expansion should be > implemented for large queries in entity Search page. For example, in the > screenshot below, the large query can be compressed using dynamic text. On > click or hover, we should see the whole query. > !dyntextquery.jpg|height=250,width=500! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3192) UI: Search results page should have a frozen horizontal scroll bar
Rahul Kurup created ATLAS-3192: -- Summary: UI: Search results page should have a frozen horizontal scroll bar Key: ATLAS-3192 URL: https://issues.apache.org/jira/browse/ATLAS-3192 Project: Atlas Issue Type: Improvement Reporter: Rahul Kurup If we have a large number of results in the Search results page, and if at the same time we have a large number of columns selected from the "Columns" button, we have to scroll all the way to the end of the Search Results page in order to use the horizontal scroll bar. This is very cumbersome for navigating horizontally and the only work around here is to use arrow keys after clicking inside the table space. It would be better to have the horizontal scroll bar of the search results table frozen in view so that it is easier to use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3205) UI: Confusion over Depth setting in Lineage
[ https://issues.apache.org/jira/browse/ATLAS-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3205: --- Description: Doubt: In the lineage UI Filter options, the behaviour of the depth setting seems to be confusing to the user when we select the “Hide process” option. If a new user selects, say ‘2’ as the depth while the “Hide process” setting is active, then the depth traversal is depth_test-->depth_test_4–>depth_test_4_8 which is 2, which matches the depth setting as per screenshot below. !depthwithoutprocess.png|height=250,width=650! However when the Hide Process option is unchecked, the depth setting does not seem to match. As the depth traversal is now depth_test-->create table dept...-->depth_test_4-->create table dept..-->depth_test_4_8 which is 4. !depthwithprocess.png|height=250,width=650! If the behaviour of depth is as per expectations, should there be a indicator or note in the Filters setting indicating how the depth matches the setting? was: Doubt: In the lineage UI Filter options, the behaviour of the depth setting seems to be confusing to the user when we select the “Hide process” option. If a new user selects, say ‘2’ as the depth while the “Hide process” setting is active, then the depth traversal is depth_test-->depth_test_4–>depth_test_4_8 which is 2, which matches the depth setting as per screenshot below. > UI: Confusion over Depth setting in Lineage > --- > > Key: ATLAS-3205 > URL: https://issues.apache.org/jira/browse/ATLAS-3205 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Priority: Minor > Attachments: depthwithoutprocess.png, depthwithprocess.png > > > Doubt: In the lineage UI Filter options, the behaviour of the depth setting > seems to be confusing to the user when we select the “Hide process” option. > If a new user selects, say ‘2’ as the depth while the “Hide process” setting > is active, then the depth traversal is > depth_test-->depth_test_4–>depth_test_4_8 > which is 2, which matches the depth setting as per screenshot below. > !depthwithoutprocess.png|height=250,width=650! > However when the Hide Process option is unchecked, the depth setting does > not seem to match. As > the depth traversal is now > depth_test-->create table dept...-->depth_test_4-->create table > dept..-->depth_test_4_8 > which is 4. > !depthwithprocess.png|height=250,width=650! > If the behaviour of depth is as per expectations, should there be a indicator > or note in the Filters > setting indicating how the depth matches the setting? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3205) UI: Confusion over Depth setting in Lineage
[
https://issues.apache.org/jira/browse/ATLAS-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Kurup updated ATLAS-3205:
---
Description:
Doubt: In the lineage UI Filter options, the behaviour of the depth setting
seems to be confusing to the user when we select the “Hide process” option.
If a new user selects, say ‘2’ as the depth while the “Hide process” setting is
active, then the depth traversal is
{noformat}
depth_test-->depth_test_4–>depth_test_4_8
{noformat}
which is 2, which matches the depth setting as per screenshot below.
!depthwithoutprocess.png|height=250,width=650!
However when the Hide Process option is unchecked, the depth setting does not
seem to match. As
the depth traversal is now
{noformat}
depth_test->>"create table dept"->>depth_test_4->>"create table
dept"->>depth_test_4_8
{noformat}
which is 4.
!depthwithprocess.png|height=250,width=650!
If the behaviour of depth is as per expectations, should there be a indicator
or note in the Filters
setting indicating how the depth matches the setting?
was:
Doubt: In the lineage UI Filter options, the behaviour of the depth setting
seems to be confusing to the user when we select the “Hide process” option.
If a new user selects, say ‘2’ as the depth while the “Hide process” setting is
active, then the depth traversal is
depth_test-->depth_test_4–>depth_test_4_8
which is 2, which matches the depth setting as per screenshot below.
!depthwithoutprocess.png|height=250,width=650!
However when the Hide Process option is unchecked, the depth setting does not
seem to match. As
the depth traversal is now
depth_test-->create table dept...-->depth_test_4-->create table
dept..-->depth_test_4_8
which is 4.
!depthwithprocess.png|height=250,width=650!
If the behaviour of depth is as per expectations, should there be a indicator
or note in the Filters
setting indicating how the depth matches the setting?
> UI: Confusion over Depth setting in Lineage
> ---
>
> Key: ATLAS-3205
> URL: https://issues.apache.org/jira/browse/ATLAS-3205
> Project: Atlas
> Issue Type: Improvement
>Reporter: Rahul Kurup
>Priority: Minor
> Attachments: depthwithoutprocess.png, depthwithprocess.png
>
>
> Doubt: In the lineage UI Filter options, the behaviour of the depth setting
> seems to be confusing to the user when we select the “Hide process” option.
> If a new user selects, say ‘2’ as the depth while the “Hide process” setting
> is active, then the depth traversal is
> {noformat}
> depth_test-->depth_test_4–>depth_test_4_8
> {noformat}
> which is 2, which matches the depth setting as per screenshot below.
> !depthwithoutprocess.png|height=250,width=650!
> However when the Hide Process option is unchecked, the depth setting does
> not seem to match. As
> the depth traversal is now
> {noformat}
> depth_test->>"create table dept"->>depth_test_4->>"create table
> dept"->>depth_test_4_8
> {noformat}
> which is 4.
> !depthwithprocess.png|height=250,width=650!
> If the behaviour of depth is as per expectations, should there be a indicator
> or note in the Filters
> setting indicating how the depth matches the setting?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-3205) UI: Confusion over Depth setting in Lineage
[ https://issues.apache.org/jira/browse/ATLAS-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3205: --- Attachment: depthwithoutprocess.png depthwithprocess.png > UI: Confusion over Depth setting in Lineage > --- > > Key: ATLAS-3205 > URL: https://issues.apache.org/jira/browse/ATLAS-3205 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Priority: Minor > Attachments: depthwithoutprocess.png, depthwithprocess.png > > > Doubt: In the lineage UI Filter options, the behaviour of the depth setting > seems to be confusing to the user when we select the “Hide process” option. > If a new user selects, say ‘2’ as the depth while the “Hide process” setting > is active, then the depth traversal is > depth_test-->depth_test_4–>depth_test_4_8 > which is 2, which matches the depth setting as per screenshot below. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3205) UI: Confusion over Depth setting in Lineage
Rahul Kurup created ATLAS-3205: -- Summary: UI: Confusion over Depth setting in Lineage Key: ATLAS-3205 URL: https://issues.apache.org/jira/browse/ATLAS-3205 Project: Atlas Issue Type: Improvement Reporter: Rahul Kurup Doubt: In the lineage UI Filter options, the behaviour of the depth setting seems to be confusing to the user when we select the “Hide process” option. If a new user selects, say ‘2’ as the depth while the “Hide process” setting is active, then the depth traversal is depth_test-->depth_test_4–>depth_test_4_8 which is 2, which matches the depth setting as per screenshot below. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3210) UI: Deleted relationship not appearing as expected in Relationships and Lineage
Rahul Kurup created ATLAS-3210: -- Summary: UI: Deleted relationship not appearing as expected in Relationships and Lineage Key: ATLAS-3210 URL: https://issues.apache.org/jira/browse/ATLAS-3210 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: deleterelationship_scenario1.png, deleterelationship_scenario1_2.png, deleterelationship_scenario1_3.png Consider the following scenario: !deleterelationship_scenario1.png! empView has an input relationship as well as an output relationship with TestProcess. We go and edit TestProcess and delete "empView" from Inputs: !deleterelationship_scenario1_2.png! 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! 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 (v7.6.3#76005)
[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 ] Rahul Kurup updated ATLAS-3210: --- Description: Consider the following scenario: !deleterelationship_scenario1.png!height=250,width=650! empView has an input relationship as well as an output relationship with TestProcess. We go and edit TestProcess and delete "empView" from Inputs: !deleterelationship_scenario1_2.png!height=250,width=650! 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!height=250,width=650! 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 was: Consider the following scenario: !deleterelationship_scenario1.png! empView has an input relationship as well as an output relationship with TestProcess. We go and edit TestProcess and delete "empView" from Inputs: !deleterelationship_scenario1_2.png! 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! 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 Summary: UI: Deleted relationship not appearing as expected in Edit Entity and Lineage (was: UI: Deleted relationship not appearing as expected in Relationships and Lineage) > 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 >Priority: Major > Attachments: deleterelationship_scenario1.png, > deleterelationship_scenario1_2.png, deleterelationship_scenario1_3.png > > > Consider the following scenario: > > !deleterelationship_scenario1.png!height=250,width=650! > > empView has an input relationship as well as an output relationship with > TestProcess. > We go and edit TestProcess and delete "empView" from Inputs: > > !deleterelationship_scenario1_2.png!height=250,width=650! > > 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!height=250,width=650! > 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 (v7.6.3#76005)
[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 ] Rahul Kurup updated ATLAS-3210: --- Description: Consider the following scenario: !deleterelationship_scenario1.png|height=250,width=650! empView has an input relationship as well as an output relationship with TestProcess. We go and edit TestProcess and delete "empView" from Inputs: !deleterelationship_scenario1_2.png|height=250,width=650! 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|height=250,width=650! 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 was: Consider the following scenario: !deleterelationship_scenario1.png!height=250,width=650! empView has an input relationship as well as an output relationship with TestProcess. We go and edit TestProcess and delete "empView" from Inputs: !deleterelationship_scenario1_2.png!height=250,width=650! 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!height=250,width=650! 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 > 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 >Priority: Major > Attachments: deleterelationship_scenario1.png, > deleterelationship_scenario1_2.png, deleterelationship_scenario1_3.png > > > Consider the following scenario: > > !deleterelationship_scenario1.png|height=250,width=650! > > empView has an input relationship as well as an output relationship with > TestProcess. > We go and edit TestProcess and delete "empView" from Inputs: > > !deleterelationship_scenario1_2.png|height=250,width=650! > > 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|height=250,width=650! > 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 (v7.6.3#76005)
[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 ] Rahul Kurup updated ATLAS-3210: --- Description: Consider the following scenario: !deleterelationship_scenario1.png|width=650,height=250! empView has an input relationship as well as an output relationship with TestProcess. 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 was: Consider the following scenario: !deleterelationship_scenario1.png|height=250,width=650! empView has an input relationship as well as an output relationship with TestProcess. We go and edit TestProcess and delete "empView" from Inputs: !deleterelationship_scenario1_2.png|height=250,width=650! 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|height=250,width=650! 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 > 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 >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. > 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 (v7.6.3#76005)
[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 ] Rahul Kurup updated ATLAS-3210: --- Description: 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 relationships were all created with AtlasUI 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 was: Consider the following scenario: !deleterelationship_scenario1.png|width=650,height=250! empView has an input relationship as well as an output relationship with TestProcess. 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 > 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 >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 relationships were > all created with AtlasUI 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 (v7.6.3#76005)
[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 ] Rahul Kurup updated ATLAS-3210: --- Description: 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 was: 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 relationships were all created with AtlasUI 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 > 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 >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 (v7.6.3#76005)
[jira] [Created] (ATLAS-3224) UI : 'Create Entity' link should be accessible outside 'Search' page.
Rahul Kurup created ATLAS-3224: -- Summary: UI : 'Create Entity' link should be accessible outside 'Search' page. Key: ATLAS-3224 URL: https://issues.apache.org/jira/browse/ATLAS-3224 Project: Atlas Issue Type: Improvement Reporter: Rahul Kurup Attachments: create_entity_improve.png Currently the only way to access "Create Entity" page is to navigate to the Search page and to click on the "create entity" text link. Going to a search page just to create an entity feels awkward, and it would be better to have this major functionality accessible from other pages. It could be better placed in the right hand side panel as shown in this mock below: !create_entity_improve.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3225) UI: 'Name' Column size gets affected after changing sorting of column
Rahul Kurup created ATLAS-3225: -- Summary: UI: 'Name' Column size gets affected after changing sorting of column Key: ATLAS-3225 URL: https://issues.apache.org/jira/browse/ATLAS-3225 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: image (1).png, image (2).png, image.png When sorting for a column is changed, it affects the width of the Name column as shown in the attached screenshots. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3228) UI: Dots appearing in select column in Search page
Rahul Kurup created ATLAS-3228: -- Summary: UI: Dots appearing in select column in Search page Key: ATLAS-3228 URL: https://issues.apache.org/jira/browse/ATLAS-3228 Project: Atlas Issue Type: Sub-task Reporter: Rahul Kurup Attachments: dotsieselectcolumn.png In IE 10 and 11, dots are visible after applying patch. Please see attached screenshot. !dotsieselectcolumn.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3247) UI:Search page showing unnecessary UI elements when no records are found.
[ https://issues.apache.org/jira/browse/ATLAS-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3247: --- Summary: UI:Search page showing unnecessary UI elements when no records are found. (was: Search page showing unnecessary UI elements when no records are found.) > UI:Search page showing unnecessary UI elements when no records are found. > - > > Key: ATLAS-3247 > URL: https://issues.apache.org/jira/browse/ATLAS-3247 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > Attachments: emptysearchdisplay.png > > > As seen in the attached screenshot, the search results page displays the > following unnecessary UI elements: > 1. Columns and Column selector. > 2. Check-boxes > 3. Page Limit. > 4. "Showing 0 records From 1 - 25 " > The above should not appear when no results are found for a query. > !emptysearchdisplay.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3247) Search page showing unnecessary UI elements when no records are found.
Rahul Kurup created ATLAS-3247: -- Summary: Search page showing unnecessary UI elements when no records are found. Key: ATLAS-3247 URL: https://issues.apache.org/jira/browse/ATLAS-3247 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: emptysearchdisplay.png As seen in the attached screenshot, the search results page displays the following unnecessary UI elements: 1. Columns and Column selector. 2. Check-boxes 3. Page Limit. 4. "Showing 0 records From 1 - 25 " The above should not appear when no results are found for a query. !emptysearchdisplay.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3248) UI: Number of Search Page results not matching set Page limit
Rahul Kurup created ATLAS-3248: -- Summary: UI: Number of Search Page results not matching set Page limit Key: ATLAS-3248 URL: https://issues.apache.org/jira/browse/ATLAS-3248 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup The number of results being displayed does not match the Page Limit option if Page Limit option is set to any value other than 25. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3249) UI: "Show more"/"Show less" button for columns with multiple entries within a cell
Rahul Kurup created ATLAS-3249: -- Summary: UI: "Show more"/"Show less" button for columns with multiple entries within a cell Key: ATLAS-3249 URL: https://issues.apache.org/jira/browse/ATLAS-3249 Project: Atlas Issue Type: Improvement Reporter: Rahul Kurup Attachments: showmoreshowless.png There should be a "Show more/Show less" button in a scenario where there are a lot of entries within a cell. For example, in the attached screenshot below, if the user searches for a hive_table and selects "Columns" as one of the displayed parameters, you can see that one search result may have multiple entries within the "Columns" column that increases the width of the search result and disrupts the UI alignment. A Show More/Show Less button that expands or compresses the displayed entries of the "Columns" table similar to the Classification would fix this alignment issue. !showmoreshowless.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3255) UI: IE 10 - Page Limit button gets displaced after clicking it.
Rahul Kurup created ATLAS-3255: -- Summary: UI: IE 10 - Page Limit button gets displaced after clicking it. Key: ATLAS-3255 URL: https://issues.apache.org/jira/browse/ATLAS-3255 Project: Atlas Issue Type: Sub-task Reporter: Rahul Kurup In IE 10, the Page Limit button position gets displaced and moves to the middle of the search results page after clicking it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3263) UI: Assign button (Create Term) should be blocked while an API call is in progress
Rahul Kurup created ATLAS-3263: -- Summary: UI: Assign button (Create Term) should be blocked while an API call is in progress Key: ATLAS-3263 URL: https://issues.apache.org/jira/browse/ATLAS-3263 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: disableassignbutton.jpg It is possible that if the user clicks the Assign button in the Create Term window multiple times rapidly, the UI detects and acknowledges the same as displayed in the screenshot below. !disableassignbutton.jpg|width=200,height=200! The side-effect of this behaviour is that these clicks are recognized in the Audit Log of the entity (to whom term is assigned) and we have multiple "Term Created" entries even though it refers to only one term being created. To avoid such behaviour, it would be better to lock the Assign button while the API call is in progress. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3294) UI: Quick-search UI visual appearance enhancement
[ https://issues.apache.org/jira/browse/ATLAS-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-3294: --- Attachment: singlecharactersearch.jpg > UI: Quick-search UI visual appearance enhancement > - > > Key: ATLAS-3294 > URL: https://issues.apache.org/jira/browse/ATLAS-3294 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3294.patch, Screen Shot 2019-06-21 at 5.15.41 > PM.png, Screen Shot 2019-06-21 at 5.19.31 PM.png, singlecharactersearch.jpg > > > * The search result would show highlighted suggestions. >!Screen Shot 2019-06-21 at 5.15.41 PM.png|width=500,height=300! > * The details page would show yellow color in property table when search > string matches. > !Screen Shot 2019-06-21 at 5.19.31 PM.png|width=500,height=300! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3294) UI: Quick-search UI visual appearance enhancement
[ https://issues.apache.org/jira/browse/ATLAS-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869447#comment-16869447 ] Rahul Kurup commented on ATLAS-3294: When we input single characters in the new search bar, the values in the Property page field appear strangely as seen in the screenshot below. !singlecharactersearch.jpg| width=200,400! > UI: Quick-search UI visual appearance enhancement > - > > Key: ATLAS-3294 > URL: https://issues.apache.org/jira/browse/ATLAS-3294 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3294.patch, Screen Shot 2019-06-21 at 5.15.41 > PM.png, Screen Shot 2019-06-21 at 5.19.31 PM.png, singlecharactersearch.jpg > > > * The search result would show highlighted suggestions. >!Screen Shot 2019-06-21 at 5.15.41 PM.png|width=500,height=300! > * The details page would show yellow color in property table when search > string matches. > !Screen Shot 2019-06-21 at 5.19.31 PM.png|width=500,height=300! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-3294) UI: Quick-search UI visual appearance enhancement
[ https://issues.apache.org/jira/browse/ATLAS-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869447#comment-16869447 ] Rahul Kurup edited comment on ATLAS-3294 at 6/21/19 12:38 PM: -- When we input single characters in the new search bar, the values in the Property page field appear strangely as seen in the screenshot below. !singlecharactersearch.jpg| width=400,800! was (Author: rahul_fi): When we input single characters in the new search bar, the values in the Property page field appear strangely as seen in the screenshot below. !singlecharactersearch.jpg| width=200,800! > UI: Quick-search UI visual appearance enhancement > - > > Key: ATLAS-3294 > URL: https://issues.apache.org/jira/browse/ATLAS-3294 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3294.patch, Screen Shot 2019-06-21 at 5.15.41 > PM.png, Screen Shot 2019-06-21 at 5.19.31 PM.png, singlecharactersearch.jpg > > > * The search result would show highlighted suggestions. >!Screen Shot 2019-06-21 at 5.15.41 PM.png|width=500,height=300! > * The details page would show yellow color in property table when search > string matches. > !Screen Shot 2019-06-21 at 5.19.31 PM.png|width=500,height=300! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-3294) UI: Quick-search UI visual appearance enhancement
[ https://issues.apache.org/jira/browse/ATLAS-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869447#comment-16869447 ] Rahul Kurup edited comment on ATLAS-3294 at 6/21/19 12:38 PM: -- When we input single characters in the new search bar, the values in the Property page field appear strangely as seen in the screenshot below. !singlecharactersearch.jpg| width=200,800! was (Author: rahul_fi): When we input single characters in the new search bar, the values in the Property page field appear strangely as seen in the screenshot below. !singlecharactersearch.jpg| width=200,400! > UI: Quick-search UI visual appearance enhancement > - > > Key: ATLAS-3294 > URL: https://issues.apache.org/jira/browse/ATLAS-3294 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3294.patch, Screen Shot 2019-06-21 at 5.15.41 > PM.png, Screen Shot 2019-06-21 at 5.19.31 PM.png, singlecharactersearch.jpg > > > * The search result would show highlighted suggestions. >!Screen Shot 2019-06-21 at 5.15.41 PM.png|width=500,height=300! > * The details page would show yellow color in property table when search > string matches. > !Screen Shot 2019-06-21 at 5.19.31 PM.png|width=500,height=300! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-3294) UI: Quick-search UI visual appearance enhancement
[ https://issues.apache.org/jira/browse/ATLAS-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869447#comment-16869447 ] Rahul Kurup edited comment on ATLAS-3294 at 6/21/19 12:38 PM: -- When we input single characters in the new search bar, the values in the Property page appear strangely as seen in the screenshot below. !singlecharactersearch.jpg| width=400,800! was (Author: rahul_fi): When we input single characters in the new search bar, the values in the Property page field appear strangely as seen in the screenshot below. !singlecharactersearch.jpg| width=400,800! > UI: Quick-search UI visual appearance enhancement > - > > Key: ATLAS-3294 > URL: https://issues.apache.org/jira/browse/ATLAS-3294 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3294.patch, Screen Shot 2019-06-21 at 5.15.41 > PM.png, Screen Shot 2019-06-21 at 5.19.31 PM.png, singlecharactersearch.jpg > > > * The search result would show highlighted suggestions. >!Screen Shot 2019-06-21 at 5.15.41 PM.png|width=500,height=300! > * The details page would show yellow color in property table when search > string matches. > !Screen Shot 2019-06-21 at 5.19.31 PM.png|width=500,height=300! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3294) UI: Quick-search UI visual appearance enhancement
[ https://issues.apache.org/jira/browse/ATLAS-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871233#comment-16871233 ] Rahul Kurup commented on ATLAS-3294: +1 > UI: Quick-search UI visual appearance enhancement > - > > Key: ATLAS-3294 > URL: https://issues.apache.org/jira/browse/ATLAS-3294 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3294-1.patch, ATLAS-3294.patch, Screen Shot > 2019-06-21 at 5.15.41 PM.png, Screen Shot 2019-06-21 at 5.19.31 PM.png, > singlecharactersearch.jpg > > > * The search result would show highlighted suggestions. >!Screen Shot 2019-06-21 at 5.15.41 PM.png|width=500,height=300! > * The details page would show yellow color in property table when search > string matches. > !Screen Shot 2019-06-21 at 5.19.31 PM.png|width=500,height=300! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3306) UI: When creating 'hdfs_path' entity through UI, it is possible to specify incorrect 'ModifiedTime' attribute value
Rahul Kurup created ATLAS-3306: -- Summary: UI: When creating 'hdfs_path' entity through UI, it is possible to specify incorrect 'ModifiedTime' attribute value Key: ATLAS-3306 URL: https://issues.apache.org/jira/browse/ATLAS-3306 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps 1. Click on 'create new entity' button. 2. Select hdfs_path 3. Select the "All" slider option. 4. Provide data for the required fields (Name,Path,QualifiedName) 5. Assuming that value for "CreateTime" is set a default value, set 'ModifiedTime' one day before the "CreateTime" value. 6. Click Update. You will see that the value is accepted even though "ModifiedTime" having a date older than "CreateTime" does not make sense. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-4150) UI : __AtlasAuditEntry, AtlasGlossary and AtlasGlossaryTerm appearing in metrics window
Rahul Kurup created ATLAS-4150: -- Summary: UI : __AtlasAuditEntry, AtlasGlossary and AtlasGlossaryTerm appearing in metrics window Key: ATLAS-4150 URL: https://issues.apache.org/jira/browse/ATLAS-4150 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: Screenshot from 2021-02-09 10-38-46.png !Screenshot from 2021-02-09 10-38-46.png|width=584,height=432! As seen in the above screenshot, entries for AtlasAuditEntry, AtlasGlossary, AtlasGlossaryTerm and AtlasGlossaryCategory are visible. These are system internal entities and should ideally not be visible in the metrics UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4150) UI : __AtlasAuditEntry appearing in metrics window
[ https://issues.apache.org/jira/browse/ATLAS-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4150: --- Summary: UI : __AtlasAuditEntry appearing in metrics window (was: UI : __AtlasAuditEntry, AtlasGlossary and AtlasGlossaryTerm appearing in metrics window) > UI : __AtlasAuditEntry appearing in metrics window > -- > > Key: ATLAS-4150 > URL: https://issues.apache.org/jira/browse/ATLAS-4150 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > Attachments: Screenshot from 2021-02-09 10-38-46.png > > > !Screenshot from 2021-02-09 10-38-46.png|width=584,height=432! > As seen in the above screenshot, entries for AtlasAuditEntry, AtlasGlossary, > AtlasGlossaryTerm and AtlasGlossaryCategory are visible. These are system > internal entities and should ideally not be visible in the metrics UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4150) UI : __AtlasAuditEntry appearing in metrics window
[ https://issues.apache.org/jira/browse/ATLAS-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4150: --- Description: !Screenshot from 2021-02-09 10-38-46.png|width=584,height=432! As seen in the above screenshot, entries for AtlasAuditEntry are visible. That is an system internal entity and should ideally not be visible in the metrics UI. was: !Screenshot from 2021-02-09 10-38-46.png|width=584,height=432! As seen in the above screenshot, entries for AtlasAuditEntry, AtlasGlossary, AtlasGlossaryTerm and AtlasGlossaryCategory are visible. These are system internal entities and should ideally not be visible in the metrics UI. > UI : __AtlasAuditEntry appearing in metrics window > -- > > Key: ATLAS-4150 > URL: https://issues.apache.org/jira/browse/ATLAS-4150 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > Attachments: Screenshot from 2021-02-09 10-38-46.png > > > !Screenshot from 2021-02-09 10-38-46.png|width=584,height=432! > As seen in the above screenshot, entries for AtlasAuditEntry are visible. > That is an system internal entity and should ideally not be visible in the > metrics UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4157) UI: 'Assign' button in 'Related Terms' window should be disabled once it is clicked.
Rahul Kurup created ATLAS-4157: -- Summary: 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: Bug Reporter: Rahul Kurup 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] [Created] (ATLAS-4178) [UI] Save and Cancel buttons do not disappear after closing their respective sections in Entity Details page
Rahul Kurup created ATLAS-4178: -- Summary: [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 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] [Commented] (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:comment-tabpanel&focusedCommentId=17297069#comment-17297069 ] Rahul Kurup commented on ATLAS-4166: +1 > 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 >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] [Commented] (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:comment-tabpanel&focusedCommentId=17312375#comment-17312375
]
Rahul Kurup commented on ATLAS-4229:
+1
> [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] [Created] (ATLAS-4242) (New UI) Single click of glossary doesn't work after clicking on Atlas logo.
Rahul Kurup created ATLAS-4242: -- Summary: (New UI) Single click of glossary doesn't work after clicking on Atlas logo. Key: ATLAS-4242 URL: https://issues.apache.org/jira/browse/ATLAS-4242 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Assignee: Prasad P. Pawar Steps: # Select any one existing glossary and single click it. # Then click on Atlas logo # Then once again single click the same glossary You will see that the glossary does not get selected as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4243) UI: Legend in lineage gets duplicated
Rahul Kurup created ATLAS-4243: -- Summary: 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 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)
[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=17320866#comment-17320866 ] Rahul Kurup commented on ATLAS-3903: +1 > 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] [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=17320867#comment-17320867 ] Rahul Kurup commented on ATLAS-4240: +1 > 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] [Created] (ATLAS-4245) New UI: "Download import template" and "Import Glossary term" gets blocked on valid navigation.
Rahul Kurup created ATLAS-4245: -- Summary: New UI: "Download import template" and "Import Glossary term" gets blocked on valid navigation. Key: ATLAS-4245 URL: https://issues.apache.org/jira/browse/ATLAS-4245 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps: # In old UI, navigate to Classification tab # Switch to new UI # Scroll down to Glossary section # Click on the ellipsis menu When you hover over the "Download import template" and "Import Glossary term" options, you will be blocked from clicking them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4245) New UI: "Download import template" and "Import Glossary term" gets blocked on valid navigation.
[ https://issues.apache.org/jira/browse/ATLAS-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4245: --- Description: Steps: # In old UI, navigate to Classification tab # Switch to new UI # Scroll down to Glossary section # Click on the ellipsis menu When you hover over the "Download import template" and "Import Glossary term" options, you will be blocked from clicking them. This is because after switching from old UI to new UI, the glossary panel shows Category tree instead of Term tree. was: Steps: # In old UI, navigate to Classification tab # Switch to new UI # Scroll down to Glossary section # Click on the ellipsis menu When you hover over the "Download import template" and "Import Glossary term" options, you will be blocked from clicking them. > New UI: "Download import template" and "Import Glossary term" gets blocked on > valid navigation. > --- > > Key: ATLAS-4245 > URL: https://issues.apache.org/jira/browse/ATLAS-4245 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Major > > Steps: > # In old UI, navigate to Classification tab > # Switch to new UI > # Scroll down to Glossary section > # Click on the ellipsis menu > When you hover over the "Download import template" and "Import Glossary term" > options, you will be blocked from clicking them. This is because after > switching from old UI to new UI, the glossary panel shows Category tree > instead of Term tree. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4242) (New UI) Single click of glossary doesn't work after clicking on Atlas logo.
[ https://issues.apache.org/jira/browse/ATLAS-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17326289#comment-17326289 ] Rahul Kurup commented on ATLAS-4242: +1 > (New UI) Single click of glossary doesn't work after clicking on Atlas logo. > > > Key: ATLAS-4242 > URL: https://issues.apache.org/jira/browse/ATLAS-4242 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > > Steps: > # Select any one existing glossary and single click it. > # Then click on Atlas logo > # Then once again single click the same glossary > You will see that the glossary does not get selected as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17326288#comment-17326288 ] Rahul Kurup commented on ATLAS-3887: +1 > 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: > 0001-ATLAS-3887-ATLAS-4242-UI-Consistency-and-highlightin.patch, > 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-4252) UI (New): Deleting subclassifications results in endless loading
Rahul Kurup created ATLAS-4252: -- Summary: UI (New): Deleting subclassifications results in endless loading Key: ATLAS-4252 URL: https://issues.apache.org/jira/browse/ATLAS-4252 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps: # In new UI, create classification # Create sub-classification for that classification # Create sub-classification for that sub-classification # Start deleting sub-classifications from latest to upwards You will see that while deleting, the confirmation prompt for one of the sub-classifications shows endless loading. Only on browser refresh it goes away and we are able to delete it normally. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4245) New UI: "Download import template" and "Import Glossary term" gets blocked on valid navigation.
[ https://issues.apache.org/jira/browse/ATLAS-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330350#comment-17330350 ] Rahul Kurup commented on ATLAS-4245: +1 > New UI: "Download import template" and "Import Glossary term" gets blocked on > valid navigation. > --- > > Key: ATLAS-4245 > URL: https://issues.apache.org/jira/browse/ATLAS-4245 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4245-New-UI-Download-import-template-and-Impor.patch > > > Steps: > # In old UI, navigate to Classification tab > # Switch to new UI > # Scroll down to Glossary section > # Click on the ellipsis menu > When you hover over the "Download import template" and "Import Glossary term" > options, you will be blocked from clicking them. This is because after > switching from old UI to new UI, the glossary panel shows Category tree > instead of Term tree. -- 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=17330351#comment-17330351 ] Rahul Kurup commented on ATLAS-4244: +1 > 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] [Commented] (ATLAS-4252) UI (New): Deleting subclassifications results in endless loading
[ https://issues.apache.org/jira/browse/ATLAS-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333021#comment-17333021 ] Rahul Kurup commented on ATLAS-4252: +1 > UI (New): Deleting subclassifications results in endless loading > > > Key: ATLAS-4252 > URL: https://issues.apache.org/jira/browse/ATLAS-4252 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4252-UI-New-Deleting-subclassifications-result.patch > > > Steps: > # In new UI, create classification > # Create sub-classification for that classification > # Create sub-classification for that sub-classification > # Start deleting sub-classifications from latest to upwards > You will see that while deleting, the confirmation prompt for one of the > sub-classifications shows endless loading. Only on browser refresh it goes > away and we are able to delete it normally. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4243) UI: Legend in lineage gets duplicated
[ https://issues.apache.org/jira/browse/ATLAS-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17338757#comment-17338757 ] Rahul Kurup commented on ATLAS-4243: +1 > UI: Legend in lineage gets duplicated > - > > Key: ATLAS-4243 > URL: https://issues.apache.org/jira/browse/ATLAS-4243 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4243-UI-Legend-in-lineage-gets-duplicated-fixe.patch, > image-2021-04-14-10-21-12-123.png > > > The legend of the lineage gets duplicated whenever a value is selected from > the depth field in filters. > > !image-2021-04-14-10-21-12-123.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4280) Save button is enabled when Classification description is updated with original value.
Rahul Kurup created ATLAS-4280: -- Summary: Save button is enabled when Classification description is updated with original value. Key: ATLAS-4280 URL: https://issues.apache.org/jira/browse/ATLAS-4280 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Previously the Save button in the popup box for classification attribute would not show us enabled if the content of the description field is only updated with the original value of the description field. But now it is showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4280: --- Summary: UI: Save button is enabled when Classification description is updated with original value. (was: Save button is enabled when Classification description is updated with original value.) > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > > Previously the Save button in the popup box for classification attribute > would not show us enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4280: --- Description: Previously the Save button in the popup box for classification attribute would not show as enabled if the content of the description field is only updated with the original value of the description field. But now it is showing as enabled when the value is updated with the original value. (was: Previously the Save button in the popup box for classification attribute would not show us enabled if the content of the description field is only updated with the original value of the description field. But now it is showing as enabled when the value is updated with the original value.) > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > > Previously the Save button in the popup box for classification attribute > would not show as enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4283) UI: Description cannot be made blank for classification
Rahul Kurup created ATLAS-4283: -- Summary: UI: Description cannot be made blank for classification Key: ATLAS-4283 URL: https://issues.apache.org/jira/browse/ATLAS-4283 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup If there is an existing description for a classification, and if the user attempts to update it to blank, he will not be able to do so. The API response for when the user inputs a blank value shows that the updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4281) Atlas UI: Tasks tab refresh button is seen on other tabs of entity detail page.
[ https://issues.apache.org/jira/browse/ATLAS-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343688#comment-17343688 ] Rahul Kurup commented on ATLAS-4281: +1 > Atlas UI: Tasks tab refresh button is seen on other tabs of entity detail > page. > --- > > Key: ATLAS-4281 > URL: https://issues.apache.org/jira/browse/ATLAS-4281 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: deferred-actions > Attachments: > 0001-ATLAS-4281-Atlas-UI-Tasks-tab-refresh-button-is-seen.patch > > > The refresh button of Tasks tab is seen at the bottom of Properties tab, > Relationships tab, Classification tabs, Audit tab & schema tabs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343690#comment-17343690 ] Rahul Kurup commented on ATLAS-4280: +1 > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Labels: Atlas-UI, classification > Attachments: > 0001-ATLAS-4280-UI-Save-button-is-enabled-when-Classifica.patch > > > Previously the Save button in the popup box for classification attribute > would not show as enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4286) User is taken to incorrect page as you go one page back after reaching page limit.
Rahul Kurup created ATLAS-4286: -- Summary: User is taken to incorrect page as you go one page back after reaching page limit. Key: ATLAS-4286 URL: https://issues.apache.org/jira/browse/ATLAS-4286 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Video link: https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing Steps: 1. Make sure there are exactly 25 entries and the default page limit is 5 items displayed on a single page. 2. Go to the last page and you will see that the 'next' page button will be enabled 3. Click the 'next' page button and you will see a blank page along with notification that no record exists. This is expected. But the page no is still showing as page no 5. 4. Try to click the previous page You will be taken to page 4 whereas the expectation is that user will be taken to page 5. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4286) UI: User is taken to incorrect page as you go one page back after reaching page limit.
[ https://issues.apache.org/jira/browse/ATLAS-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4286: --- Summary: UI: User is taken to incorrect page as you go one page back after reaching page limit. (was: User is taken to incorrect page as you go one page back after reaching page limit.) > UI: User is taken to incorrect page as you go one page back after reaching > page limit. > -- > > Key: ATLAS-4286 > URL: https://issues.apache.org/jira/browse/ATLAS-4286 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > > Video link: > https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing > Steps: > 1. Make sure there are exactly 25 entries and the default page limit is 5 > items displayed on a single page. > 2. Go to the last page and you will see that the 'next' page button will be > enabled > 3. Click the 'next' page button and you will see a blank page along with > notification that no record exists. This is expected. But the page no is > still showing as page no 5. > 4. Try to click the previous page > You will be taken to page 4 whereas the expectation is that user will be > taken to page 5. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4295) UI: The short/long description of term & category doesnt get updated immediately when made blank
Rahul Kurup created ATLAS-4295: -- Summary: UI: The short/long description of term & category doesnt get updated immediately when made blank Key: ATLAS-4295 URL: https://issues.apache.org/jira/browse/ATLAS-4295 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup When one empties the the short and long description fields of term & category and saves, the UI doesn't get reflected immediately. But on refresh, it gets reflected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4283) UI: Description cannot be made blank for classification
[ https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349278#comment-17349278 ] Rahul Kurup commented on ATLAS-4283: +1 > UI: Description cannot be made blank for classification > --- > > Key: ATLAS-4283 > URL: https://issues.apache.org/jira/browse/ATLAS-4283 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch > > > If there is an existing description for a classification, and if the user > attempts to update it to blank, he will not be able to do so. > The API response for when the user inputs a blank value shows that the > updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4294) Atlas UI : Format long description of Glossary term and category UI
[ https://issues.apache.org/jira/browse/ATLAS-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349299#comment-17349299 ] Rahul Kurup commented on ATLAS-4294: +1 > Atlas UI : Format long description of Glossary term and category UI > --- > > Key: ATLAS-4294 > URL: https://issues.apache.org/jira/browse/ATLAS-4294 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4294-Atlas-UI-Format-long-description-of-Gloss.patch, > atlas_4294_fix.png > > > Currently the long description is render as long string and it all appears > as a single text string > It is hard to read multiple lines. > Makes to support newline character in rendering long description > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (ATLAS-4283) UI: Description cannot be made blank for classification
[ https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4283: --- Comment: was deleted (was: +1) > UI: Description cannot be made blank for classification > --- > > Key: ATLAS-4283 > URL: https://issues.apache.org/jira/browse/ATLAS-4283 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch > > > If there is an existing description for a classification, and if the user > attempts to update it to blank, he will not be able to do so. > The API response for when the user inputs a blank value shows that the > updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4299) [Atlas: Debug Metrics] Several UI Issues are seen when the total count crossed 25
[
https://issues.apache.org/jira/browse/ATLAS-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352461#comment-17352461
]
Rahul Kurup commented on ATLAS-4299:
+1
> [Atlas: Debug Metrics] Several UI Issues are seen when the total count
> crossed 25
> -
>
> Key: ATLAS-4299
> URL: https://issues.apache.org/jira/browse/ATLAS-4299
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch, Screenshot
> 2021-05-24 at 4.13.08 PM.png, Screenshot 2021-05-24 at 4.40.15 PM.png
>
>
> A list of UI issues are seen when the total issues crosses 25
> # The total number of data as per response is 29, but UI says 30
> # The data displayed are only 29 but one of them is a blank entry
> (Highlighted in screenshot)
> # Among the 29 entries present in api response, one of them is missing in
> the UI in this case [*TypesREST_getTypeDefHeaders*]
> # When all the data are made to display in same page, the UI shows page 1
> and 2
> # When the selection is made to display only 25, it still displays all the
> data [25+ entries are displayed]
> # Sorting does not work without refresh
> Response Data:
> {code:java}
> {
> "TypesREST_getTypeDefHeaders": {
> "name": "TypesREST_getTypeDefHeaders",
> "numops": 13,
> "minTime": 2,
> "maxTime": 37,
> "stdDevTime": 0,
> "avgTime": 2
> },
> "GlossaryREST_createGlossaryTerm": {
> "name": "GlossaryREST_createGlossaryTerm",
> "numops": 11,
> "minTime": 218,
> "maxTime": 308,
> "stdDevTime": 29.160475,
> "avgTime": 235.3
> },
> "GlossaryREST_deleteGlossaryCategory": {
> "name": "GlossaryREST_deleteGlossaryCategory",
> "numops": 2,
> "minTime": 197,
> "maxTime": 219,
> "stdDevTime": 0,
> "avgTime": 197
> },
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 3,
> "minTime": 165,
> "maxTime": 521,
> "stdDevTime": 251.73001,
> "avgTime": 343
> },
> "EntityREST_addClassifications": {
> "name": "EntityREST_addClassifications",
> "numops": 339,
> "minTime": 64,
> "maxTime": 430,
> "stdDevTime": 2.5495098,
> "avgTime": 101.5
> },
> "DiscoveryREST_getSavedSearches": {
> "name": "DiscoveryREST_getSavedSearches",
> "numops": 13,
> "minTime": 3,
> "maxTime": 38,
> "stdDevTime": 0,
> "avgTime": 3
> },
> "TypesREST_getClassificationDefByName": {
> "name": "TypesREST_getClassificationDefByName",
> "numops": 11,
> "minTime": 2,
> "maxTime": 2,
> "stdDevTime": 0,
> "avgTime": 1
> },
> "GlossaryREST_createGlossary": {
> "name": "GlossaryREST_createGlossary",
> "numops": 4,
> "minTime": 167,
> "maxTime": 197,
> "stdDevTime": 0,
> "avgTime": 179
> },
> "EntityREST_createOrUpdate": {
> "name": "EntityREST_createOrUpdate",
> "numops": 2,
> "minTime": 76,
> "maxTime": 133,
> "stdDevTime": 40.305088,
> "avgTime": 104.5
> },
> "GlossaryREST_getGlossaryCategory": {
> "name": "GlossaryREST_getGlossaryCategory",
> "numops": 14,
> "minTime": 5,
> "maxTime": 47,
> "stdDevTime": 18.384777,
> "avgTime": 25
> },
> "GlossaryREST_updateGlossaryTerm": {
> "name": "GlossaryREST_updateGlossaryTerm",
> "numops": 5,
> "minTime": 62,
> "maxTime": 559,
> "stdDevTime": 340.11835,
> "avgTime": 62
> },
> "DiscoveryREST_searchUsingBasic": {
> "name": "DiscoveryREST_searchUsingBasic",
> "numops": 2,
> "minTime": 25,
> "maxTime": 451,
> "stdDevTime": 0,
> "avgTime": 25
> },
> "EntityREST_getById": {
> "name": "EntityREST_getById",
> "numops": 5,
> "minTime": 37,
> "maxTime": 84,
> "stdDevTime": 20.067387,
> "avgTime": 52.8
> },
> "GlossaryREST_getGlossaries": {
> "name": "GlossaryREST_getGlossaries",
> "numops": 34,
> "minTime": 10,
> "maxTime": 291,
> "stdDevTime": 48.294235,
> "avgTime": 180
> },
> "TypesREST_getAllTypeDefs": {
> "name": "TypesREST_getAllTypeDefs",
> "numops": 44,
> "minTime": 0,
> "maxTime": 32,
> "stdDevTime": 0.5,
> "avgTime": 0.25
> },
> "DiscoveryREST_searchUsingDSL": {
> "name": "DiscoveryREST_searchUsingDSL",
> "numops": 4,
> "minTime": 13,
> "maxTime": 243,
> "stdDevTime": 155.56349,
> "avgTime": 16
> },
> "GlossaryREST_createGlossaryCategory": {
> "name": "GlossaryREST_createGlossaryCategory",
> "numops": 4,
> "minTime": 195,
> "maxTime": 293,
> "stdDevTime": 0,
>
[jira] [Commented] (ATLAS-4298) [Atlas: Debug Metrics][UI] When REST API Metric page has more than 25 entries, the page does not load unless manually refreshed
[
https://issues.apache.org/jira/browse/ATLAS-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352460#comment-17352460
]
Rahul Kurup commented on ATLAS-4298:
+1
> [Atlas: Debug Metrics][UI] When REST API Metric page has more than 25
> entries, the page does not load unless manually refreshed
> ---
>
> Key: ATLAS-4298
> URL: https://issues.apache.org/jira/browse/ATLAS-4298
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch
>
>
> When debug metrics is enabled by setting *atlas.debug.metrics.enabled=true*
> Debug metrics url page: :31443/index.html#!/debugMetrics displays the
> REST API Metrics.
> When the result page entry count crosses 25, the page does not load, unless
> refresh button is hit
> There are no error logs found in the cluster but console displays the
> following
> {code:java}
> backbone.paginator.min.js?bust=1621440039818:1
> Uncaught TypeError: Cannot read property 'add' of undefined
> at e (backbone.paginator.min.js?bust=1621440039818:1)
> at Object. (backbone.paginator.min.js?bust=1621440039818:1)
> at s (backbone-min.js?bust=1621440039818:1)
> at r (backbone-min.js?bust=1621440039818:1)
> at m (backbone-min.js?bust=1621440039818:1)
> at N.d.k.trigger (backbone-min.js?bust=1621440039818:1)
> at N.d._onModelEvent (backbone-min.js?bust=1621440039818:1)
> at s (backbone-min.js?bust=1621440039818:1)
> at r (backbone-min.js?bust=1621440039818:1)
> at m (backbone-min.js?bust=1621440039818:1){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4296) [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not matching the api response values
[
https://issues.apache.org/jira/browse/ATLAS-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352459#comment-17352459
]
Rahul Kurup commented on ATLAS-4296:
+1
> [Atlas: Debug Metrics] Min Time , Max Time and Average Time in UI are not
> matching the api response values
> --
>
> Key: ATLAS-4296
> URL: https://issues.apache.org/jira/browse/ATLAS-4296
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments:
> 0001-ATLAS-UI-ATLAS-4296-ATLAS-4298-ATLAS-4299-Debug-Metr.patch,
> ATLAS-4296-1.patch, Screenshot 2021-05-21 at 4.18.34 PM.png, Screenshot
> 2021-05-21 at 4.18.34 PM.png
>
>
> Scenario: Enable debug Metrics
> !Screenshot 2021-05-21 at 4.18.34 PM.png|width=646,height=322!
> Eg: Consider the above highlighted example. *GlossaryREST_deleteGlossary*
> Here
> Min Time : 1.920 (seconds)
> Max Time : 5.530 (seconds) and
> Average Time : 5.530 (seconds)
> *Api response:*
> {code:java}
> "GlossaryREST_deleteGlossary": {
> "name": "GlossaryREST_deleteGlossary",
> "numops": 6,
> "minTime": 192,
> "maxTime": 553,
> "stdDevTime": 21.556128,
> "avgTime": 532
> } {code}
>
> 1.92 (seconds) has to be 1920 if the value is response is stored in
> milliseconds but it appears as 192
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4304) [Business Metadata Bulk Import] [Beta UI] Bulk Import Business Metadata/Glossary options overlap
[ https://issues.apache.org/jira/browse/ATLAS-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352462#comment-17352462 ] Rahul Kurup commented on ATLAS-4304: +1 > [Business Metadata Bulk Import] [Beta UI] Bulk Import Business > Metadata/Glossary options overlap > > > Key: ATLAS-4304 > URL: https://issues.apache.org/jira/browse/ATLAS-4304 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4304-UI-Business-Metadata-Bulk-Import-Beta-UI-.patch, Screenshot > 2021-05-24 at 11.31.32 PM.png, Screenshot 2021-05-24 at 11.31.48 PM.png > > > As seen in the screenshot below, the sub drop downs overlap and the Business > Metadata/Glossary in almost 50% hidden > !Screenshot 2021-05-24 at 11.31.32 PM.png! > !Screenshot 2021-05-24 at 11.31.48 PM.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4314) Atlas UI: Make Tasks tab default as hidden on entity detail page.
[ https://issues.apache.org/jira/browse/ATLAS-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352464#comment-17352464 ] Rahul Kurup commented on ATLAS-4314: +1 > Atlas UI: Make Tasks tab default as hidden on entity detail page. > -- > > Key: ATLAS-4314 > URL: https://issues.apache.org/jira/browse/ATLAS-4314 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: Atlas-UI > Attachments: > 0001-ATLAS-4314-Atlas-UI-Make-Tasks-tab-default-as-hidden.patch > > > Task Tab is seen on the Entity detail page when session API doesn't have > atlas.tasks.enabled value. Tab should not be shown on Entity detail page UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4309) Atlas UI: After deleting the sub-classifications from Atlas UI, they still appear in UI.
[ https://issues.apache.org/jira/browse/ATLAS-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352463#comment-17352463 ] Rahul Kurup commented on ATLAS-4309: +1 > Atlas UI: After deleting the sub-classifications from Atlas UI, they still > appear in UI. > > > Key: ATLAS-4309 > URL: https://issues.apache.org/jira/browse/ATLAS-4309 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4309-Atlas-UI-After-deleting-the-sub-classific.patch > > > - After deleting the sub-classifications from Atlas UI, they still appear > super-classifications > - While the sub-classification is deleted successfully and does not appear > under parent classification available in flat/tree view, it does show up on > the main screen for classification. > - However, after refreshing the browser, the deleted sub-classification is > removed from the UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4308) ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting happens on the previous sorted results received from the server
[ https://issues.apache.org/jira/browse/ATLAS-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352465#comment-17352465 ] Rahul Kurup commented on ATLAS-4308: +1 > ATLAS UI Audit sorting : When consecutive Entity Audits are fired, sorting > happens on the previous sorted results received from the server > -- > > Key: ATLAS-4308 > URL: https://issues.apache.org/jira/browse/ATLAS-4308 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: Atlas-UI, audits > Attachments: > 0001-ATLAS-4308-ATLAS-UI-Audit-sorting-When-consecutive-E.patch > > > Attaching 2 screenshots where following was done > > 1)sort by action + sort by user (sort by action is done and on top of that > result , sort by user is done) > 2)sort by user (only sort by user is done) > > The results are different on UI. > > The query for : > 1) is > a) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc&offset=0&count=25&sortBy=action > > b) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc&offset=0&count=25&sortBy=user > > 2) is > a) > /api/atlas/v2/entity/0efb15b7-d4cc-4bcc-87d1-bee41d1baae5/audit?sortOrder=asc&offset=0&count=25&sortBy=user > > 1.b happens on the result of 1.a which is not expected. > > 1.b should be equal to 2.a -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4327) UI: Deleting all glossaries and then switching to new UI results in unexpected behaviour
Rahul Kurup created ATLAS-4327: -- Summary: UI: Deleting all glossaries and then switching to new UI results in unexpected behaviour Key: ATLAS-4327 URL: https://issues.apache.org/jira/browse/ATLAS-4327 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup As seen in the below video url, if the user deletes all glossaries from old UI and then switches over to new UI, the Glossary section is missing and a endless loader animation keeps playing. [^glossary_import_delete_new_ui.webm] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4327) UI: Deleting all glossaries and then switching to new UI results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4327: --- Description: As seen in the below video url, if the user deletes all glossaries from old UI and then switches over to new UI, the Glossary section is missing and a endless loader animation keeps playing. [[^glossary_import_delete_new_ui.webm]|https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing] was: As seen in the below video url, if the user deletes all glossaries from old UI and then switches over to new UI, the Glossary section is missing and a endless loader animation keeps playing. [^glossary_import_delete_new_ui.webm] > UI: Deleting all glossaries and then switching to new UI results in > unexpected behaviour > > > Key: ATLAS-4327 > URL: https://issues.apache.org/jira/browse/ATLAS-4327 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Major > > As seen in the below video url, if the user deletes all glossaries from old > UI and then switches over to new UI, the Glossary section is missing and a > endless loader animation keeps playing. > [[^glossary_import_delete_new_ui.webm]|https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4325) [Atlas: Glossary Term Bulk Import] [UI] Unable to perform bulk import glossary term via UI
[
https://issues.apache.org/jira/browse/ATLAS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357335#comment-17357335
]
Rahul Kurup commented on ATLAS-4325:
+1
> [Atlas: Glossary Term Bulk Import] [UI] Unable to perform bulk import
> glossary term via UI
> --
>
> Key: ATLAS-4325
> URL: https://issues.apache.org/jira/browse/ATLAS-4325
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4325-Atlas-Glossary-Term-Bulk-Import-UI-Unable.patch, Screenshot
> 2021-06-03 at 5.41.57 PM.png
>
>
> Bulk import is failing with "\{"msgDesc":"Missing header or invalid Header
> value for CSRF Vulnerability Protection"}" !Screenshot 2021-06-03 at 5.41.57
> PM.png|width=443,height=273!
> NOTE: the same succeeds via api
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4327) UI: Deleting all glossaries and then switching to new UI results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4327: --- Description: As seen in the below video url, if the user deletes all glossaries from old UI and then switches over to new UI, the Glossary section is missing and a endless loader animation keeps playing. [https://drive.google.com/file/d/1lXoFEGNNkC_49Zhc8Vb4rT47GT_YYPSq/view?usp=sharing|https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing] was: As seen in the below video url, if the user deletes all glossaries from old UI and then switches over to new UI, the Glossary section is missing and a endless loader animation keeps playing. [[^glossary_import_delete_new_ui.webm]|https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing] > UI: Deleting all glossaries and then switching to new UI results in > unexpected behaviour > > > Key: ATLAS-4327 > URL: https://issues.apache.org/jira/browse/ATLAS-4327 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > > As seen in the below video url, if the user deletes all glossaries from old > UI and then switches over to new UI, the Glossary section is missing and a > endless loader animation keeps playing. > [https://drive.google.com/file/d/1lXoFEGNNkC_49Zhc8Vb4rT47GT_YYPSq/view?usp=sharing|https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4326) Atlas UI: Multiple continuous space is accepted on Short description for Classifications, Gloassarys, Categorys & Terms .
[ https://issues.apache.org/jira/browse/ATLAS-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359811#comment-17359811 ] Rahul Kurup commented on ATLAS-4326: +1 > Atlas UI: Multiple continuous space is accepted on Short description for > Classifications, Gloassarys, Categorys & Terms . > - > > Key: ATLAS-4326 > URL: https://issues.apache.org/jira/browse/ATLAS-4326 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4326-1-Atlas-UI-Multiple-continuous-space-is-a.patch, > 0001-ATLAS-4326-2-Atlas-UI-Multiple-continuous-space-is-a.patch > > > Add multiple continuous spaces in the short description field, this value is > accepted on UI by clicking the Save/Update button. > After updating the values, the Detail page doesn't show the entered value of > Short description files. eg: " This is Term1 " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4295) UI: The short/long description of term & category doesnt get updated immediately when made blank
[ https://issues.apache.org/jira/browse/ATLAS-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359809#comment-17359809 ] Rahul Kurup commented on ATLAS-4295: +1 > UI: The short/long description of term & category doesnt get updated > immediately when made blank > > > Key: ATLAS-4295 > URL: https://issues.apache.org/jira/browse/ATLAS-4295 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4295-UI-UI-The-short-long-description-of-term-.patch > > > When one empties the the short and long description fields of term & category > and saves, > the UI doesn't get reflected immediately. But on refresh, it gets reflected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4283) UI: Description cannot be made blank for classification
[ https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359903#comment-17359903 ] Rahul Kurup commented on ATLAS-4283: +1 > UI: Description cannot be made blank for classification > --- > > Key: ATLAS-4283 > URL: https://issues.apache.org/jira/browse/ATLAS-4283 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch > > > If there is an existing description for a classification, and if the user > attempts to update it to blank, he will not be able to do so. > The API response for when the user inputs a blank value shows that the > updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4327) UI: Deleting all glossaries and then switching to new UI results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4327: --- Description: As seen in the below video url, if the user deletes all glossaries from old UI and then switches over to new UI, the Glossary section is missing and a endless loader animation keeps playing. https://drive.google.com/file/d/1lXoFEGNNkC_49Zhc8Vb4rT47GT_YYPSq/view?usp=sharing was: As seen in the below video url, if the user deletes all glossaries from old UI and then switches over to new UI, the Glossary section is missing and a endless loader animation keeps playing. [https://drive.google.com/file/d/1lXoFEGNNkC_49Zhc8Vb4rT47GT_YYPSq/view?usp=sharing|https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing] > UI: Deleting all glossaries and then switching to new UI results in > unexpected behaviour > > > Key: ATLAS-4327 > URL: https://issues.apache.org/jira/browse/ATLAS-4327 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > > As seen in the below video url, if the user deletes all glossaries from old > UI and then switches over to new UI, the Glossary section is missing and a > endless loader animation keeps playing. > https://drive.google.com/file/d/1lXoFEGNNkC_49Zhc8Vb4rT47GT_YYPSq/view?usp=sharing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4327) UI: Deleting all glossaries and then switching to new UI results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361516#comment-17361516 ] Rahul Kurup commented on ATLAS-4327: +1 > UI: Deleting all glossaries and then switching to new UI results in > unexpected behaviour > > > Key: ATLAS-4327 > URL: https://issues.apache.org/jira/browse/ATLAS-4327 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4327-1-UI-Deleting-all-glossaries-and-then-swi.patch > > > As seen in the below video url, if the user deletes all glossaries from old > UI and then switches over to new UI, the Glossary section is missing and a > endless loader animation keeps playing. > https://drive.google.com/file/d/1lXoFEGNNkC_49Zhc8Vb4rT47GT_YYPSq/view?usp=sharing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4316) UI : When lineage contains shell entities, the image couldn't be downloaded.
[ https://issues.apache.org/jira/browse/ATLAS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366640#comment-17366640 ] Rahul Kurup commented on ATLAS-4316: +1 > UI : When lineage contains shell entities, the image couldn't be downloaded. > > > Key: ATLAS-4316 > URL: https://issues.apache.org/jira/browse/ATLAS-4316 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4316-UI-1-When-lineage-contains-shell-entities.patch > > > Added a screen recording where the lineage contains shell entities so the > image is not downloaded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4286) UI: User is taken to incorrect page as you go one page back after reaching page limit.
[ https://issues.apache.org/jira/browse/ATLAS-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367990#comment-17367990 ] Rahul Kurup commented on ATLAS-4286: +1 > UI: User is taken to incorrect page as you go one page back after reaching > page limit. > -- > > Key: ATLAS-4286 > URL: https://issues.apache.org/jira/browse/ATLAS-4286 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4286-UI-1-User-is-taken-to-incorrect-page-as-y.patch > > > Video link: > https://drive.google.com/file/d/1-5KgEdMVwDkr9DAS78TNMNqtP-F0B2q0/view?usp=sharing > Steps: > 1. Make sure there are exactly 25 entries and the default page limit is 5 > items displayed on a single page. > 2. Go to the last page and you will see that the 'next' page button will be > enabled > 3. Click the 'next' page button and you will see a blank page along with > notification that no record exists. This is expected. But the page no is > still showing as page no 5. > 4. Try to click the previous page > You will be taken to page 4 whereas the expectation is that user will be > taken to page 5. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4345) UI: Lineage issues for when entities are greater than 9k in a given lineage.
Rahul Kurup created ATLAS-4345: -- Summary: UI: Lineage issues for when entities are greater than 9k in a given lineage. Key: ATLAS-4345 URL: https://issues.apache.org/jira/browse/ATLAS-4345 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup There are two issues that emerge when there are more than 9k entities in a given lineage: # It doesn't display all the entities in the given page, but there is no message saying why. # When I attempt to download image, it does nothing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4345) UI: Lineage issues for when entities are greater than 9k in a given lineage.
[ https://issues.apache.org/jira/browse/ATLAS-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375712#comment-17375712 ] Rahul Kurup commented on ATLAS-4345: +1 > UI: Lineage issues for when entities are greater than 9k in a given lineage. > > > Key: ATLAS-4345 > URL: https://issues.apache.org/jira/browse/ATLAS-4345 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4345-UI-Lineage-issues-for-when-entities-are-g.patch > > > There are two issues that emerge when there are more than 9k entities in a > given lineage: > > # It doesn't display all the entities in the given page, but there is no > message saying why. > # When I attempt to download image, it does nothing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4355) UI: Spelling mistake in message after editing Busines Metadata value
Rahul Kurup created ATLAS-4355: -- Summary: UI: Spelling mistake in message after editing Busines Metadata value Key: ATLAS-4355 URL: https://issues.apache.org/jira/browse/ATLAS-4355 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: Screenshot 2021-07-13 at 11-28-24 Atlas.png As per atttached screenshot, "One or more Business Metadada attributess were updated successfully" should be "One or more Business Metadata attributes were updated successfully" !Screenshot 2021-07-13 at 11-28-24 Atlas.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4356) UI: Unusual behaviour after clicking back button on business metadata
Rahul Kurup created ATLAS-4356: -- Summary: UI: Unusual behaviour after clicking back button on business metadata Key: ATLAS-4356 URL: https://issues.apache.org/jira/browse/ATLAS-4356 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup 1. Go to Admin->Administration 2. In Business Metadata, click on any existing Business metadata. 3. Click the (<) back button next to the title of the Business metadata 4. Perform a search in basic search 5. Click on Admin->Administration You will see that the details of the previous business metadata are still open. It goes away after clicking on Administration again. But it again comes back if you do another search and then click on Administration again. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4355) UI: Spelling mistake in message after editing Business Metadata value
[ https://issues.apache.org/jira/browse/ATLAS-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4355: --- Summary: UI: Spelling mistake in message after editing Business Metadata value (was: UI: Spelling mistake in message after editing Busines Metadata value) > UI: Spelling mistake in message after editing Business Metadata value > - > > Key: ATLAS-4355 > URL: https://issues.apache.org/jira/browse/ATLAS-4355 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Umesh Padashetty >Priority: Minor > Attachments: ATLAS-4355.patch, Screenshot 2021-07-13 at 11-28-24 > Atlas.png > > > As per atttached screenshot, > "One or more Business Metadada attributess were updated successfully" > should be > "One or more Business Metadata attributes were updated successfully" > !Screenshot 2021-07-13 at 11-28-24 Atlas.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4355) UI: Spelling mistake in message after editing Business Metadata value
[ https://issues.apache.org/jira/browse/ATLAS-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379745#comment-17379745 ] Rahul Kurup commented on ATLAS-4355: +1 > UI: Spelling mistake in message after editing Business Metadata value > - > > Key: ATLAS-4355 > URL: https://issues.apache.org/jira/browse/ATLAS-4355 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Umesh Padashetty >Priority: Minor > Attachments: ATLAS-4355.patch, Screenshot 2021-07-13 at 11-28-24 > Atlas.png > > > As per atttached screenshot, > "One or more Business Metadada attributess were updated successfully" > should be > "One or more Business Metadata attributes were updated successfully" > !Screenshot 2021-07-13 at 11-28-24 Atlas.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4359) UI: Misalignment in Searchweight tooltip text in business metadata
Rahul Kurup created ATLAS-4359: -- Summary: UI: Misalignment in Searchweight tooltip text in business metadata Key: ATLAS-4359 URL: https://issues.apache.org/jira/browse/ATLAS-4359 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup When you hover over the tooltip (?) for searchweight in the page for editing business metadata, there is misalignment in the text explaining the searchweight ranges. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4360) UI: Misalignment of placeholder text in labels, enum attributes and classification fields in Chrome
Rahul Kurup created ATLAS-4360: -- Summary: UI: Misalignment of placeholder text in labels, enum attributes and classification fields in Chrome Key: ATLAS-4360 URL: https://issues.apache.org/jira/browse/ATLAS-4360 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup While adding label in entity detail page, or while creating enumeration attributes and while selecting parent classification, if one erases all the values entered, then the placeholder text gets misaligned as in the attached video.[^Global_issue.webm] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4360) UI: Misalignment of placeholder text in labels, enum attributes and classification fields in Chrome
[ https://issues.apache.org/jira/browse/ATLAS-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381352#comment-17381352 ] Rahul Kurup commented on ATLAS-4360: +1 > UI: Misalignment of placeholder text in labels, enum attributes and > classification fields in Chrome > --- > > Key: ATLAS-4360 > URL: https://issues.apache.org/jira/browse/ATLAS-4360 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4360-UI-Misalignment-of-placeholder-text-in-la.patch > > > While adding label in entity detail page, or while creating enumeration > attributes and while selecting parent classification, if one erases all the > values entered, then the placeholder text gets misaligned as in the attached > video.[^Global_issue.webm] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4359) UI: Misalignment in Searchweight tooltip text in business metadata
[ https://issues.apache.org/jira/browse/ATLAS-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381351#comment-17381351 ] Rahul Kurup commented on ATLAS-4359: +1 > UI: Misalignment in Searchweight tooltip text in business metadata > -- > > Key: ATLAS-4359 > URL: https://issues.apache.org/jira/browse/ATLAS-4359 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4359-UI-Misalignment-in-Searchweight-tooltip-t.patch > > > When you hover over the tooltip (?) for searchweight in the page for editing > business metadata, there is misalignment in the text explaining the > searchweight ranges. -- This message was sent by Atlassian Jira (v8.3.4#803005)
