[jira] [Commented] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.

2021-02-22 Thread Nixon Rodrigues (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288917#comment-17288917
 ] 

Nixon Rodrigues commented on ATLAS-3376:


+1 for the patch. Thanks [~prasadpp13] for the patch.

> UI: When no Catalogs are present, user should be presented with an 
> appropriate message when trying to associate Category to Term.
> -
>
> Key: ATLAS-3376
> URL: https://issues.apache.org/jira/browse/ATLAS-3376
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3376-UI-V1-When-no-Catalogs-are-present-user-s.patch, 
> 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, 
> ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 
> 22-25-05.png, screenshot-newtab-2021.02.22-22_31_06.png
>
>
> If a user tries to associate a Category to a Term, and if not a single 
> Category has been created for any of the Glossaries, the user is presented 
> with the Category association screen but with no Categories for the user to 
> assign to the term. 
> This could create a confusion that there might be a Catalog present somewhere 
> but is not visible to the user, when actually no Catalogs exist. A 
> notification should be fired in this scenario, informing the user that no 
> Catalog exists that can be assigned to the term. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3186) UI: Background navigation is possible when "Advanced Search Queries" popup is active.

2021-02-22 Thread Nixon Rodrigues (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288916#comment-17288916
 ] 

Nixon Rodrigues commented on ATLAS-3186:


+1 for the patch. Thanks [~prasadpp13] for the patch.

> 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
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3186-UI-Background-navigation-is-possible-when.patch
>
>
> Steps:
>  # From Atlas UI, navigate as follows: Search–>Classification–>Change button 
> from Flat to Tree->Glossary–>Search
>  #  Click on "?" icon in Search.
>  # Click the back button of your browser
> You will see that as you go on pressing the back button, navigation will 
> occur in the background in the reverse order of menus mentioned in step 1 
> (and the button selection will be reversed from Tree to Flat).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4167) Large no. of calls are getting generated while rendering search results

2021-02-22 Thread Nixon Rodrigues (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288915#comment-17288915
 ] 

Nixon Rodrigues commented on ATLAS-4167:


+1 for the patch. Thanks [~prasadpp13] for the patch.

> Large no. of calls are getting generated while rendering search results
> ---
>
> Key: ATLAS-4167
> URL: https://issues.apache.org/jira/browse/ATLAS-4167
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4167-UI-Large-no.-of-calls-are-getting-generat.patch, 
> ATLAS-4167Bug.png, ATLAS-4167fix.png
>
>
> While rendering search-results, there are large number of calls to Atlas 
> server to retrieve entity-icon.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (ATLAS-3306) UI: When creating 'hdfs_path' entity through UI, it is possible to specify incorrect 'ModifiedTime' attribute value

2021-02-22 Thread Prasad P. Pawar (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288912#comment-17288912
 ] 

Prasad P. Pawar edited comment on ATLAS-3306 at 2/23/21, 7:28 AM:
--

This fix is provided on the uploaded patch.
now the date selection for the modified date field will be >= current date set.



was (Author: prasadpp13):
This fix is provided on the uploaded patch.


> 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
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-3306-UI-When-creating-hdfs_path-entity-through.patch, 
> Atlas-3306_fix.png
>
>
> 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
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3306) UI: When creating 'hdfs_path' entity through UI, it is possible to specify incorrect 'ModifiedTime' attribute value

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-3306:
---
Attachment: Atlas-3306_fix.png

> 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
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-3306-UI-When-creating-hdfs_path-entity-through.patch, 
> Atlas-3306_fix.png
>
>
> 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
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3306) UI: When creating 'hdfs_path' entity through UI, it is possible to specify incorrect 'ModifiedTime' attribute value

2021-02-22 Thread Prasad P. Pawar (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288912#comment-17288912
 ] 

Prasad P. Pawar commented on ATLAS-3306:


This fix is provided on the uploaded patch.


> 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
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-3306-UI-When-creating-hdfs_path-entity-through.patch
>
>
> 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
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3306) UI: When creating 'hdfs_path' entity through UI, it is possible to specify incorrect 'ModifiedTime' attribute value

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-3306:
---
Fix Version/s: 2.2.0
   3.0.0

> 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
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-3306-UI-When-creating-hdfs_path-entity-through.patch
>
>
> 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
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-3306) UI: When creating 'hdfs_path' entity through UI, it is possible to specify incorrect 'ModifiedTime' attribute value

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar reassigned ATLAS-3306:
--

Assignee: Prasad P. Pawar  (was: Keval Bhatt)

> 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
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments: 
> 0001-ATLAS-3306-UI-When-creating-hdfs_path-entity-through.patch
>
>
> 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
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4102) UI - DSL Search: UI hangs When Executing Certain Queries

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-4102:
---
Fix Version/s: 2.2.0
   3.0.0

> UI - DSL Search:  UI hangs When Executing Certain Queries
> -
>
> Key: ATLAS-4102
> URL: https://issues.apache.org/jira/browse/ATLAS-4102
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-Atlas-4102-UI-DSL-Search-UI-hangs-When-Executing-Cer.patch, 
> Atlas-4102.png
>
>
> *Background*
> Certain types of Advanced Search (DSL) queries within Atlas return 
> _AtlasSearchResult_ in a slightly different format.
> The current UI is not able to render the search results.
> The REST APIs however, return the output successfully.
> *Steps to Duplicate*
>  # Within Atlas web UI, Advanced Search, execute: _hive_table groupby (owner) 
> select min(name)_ _URL: 
> http://:31000/index.html#!/search/searchResult?query=hive_table%20groupby%20(owner)%20select%20min(name)=dsl=true_
> _Expected result:_ Search results should be displayed.
> Actual result: Web UI freezes. Upon inspecting using Developer tools, a JS 
> exception is displayed.
> Additional info:
> Query: _hive_table groupby(owner) select owner, max(name)_
> Output json:
> {code:java}
> {
> "attributes": {
> "name": [
> "owner",
> "max(name)"
> ],
> "values": [
> [
> "hive",
> "tuarp_uarmt_pmtreq_h"
> ],
> [
> "iadetldev",
> "video_analytics_log_id"
> ],
> [
> "atsacoli",
> "aj_psync_test_h"
> ]
> ]
> },
> "approximateCount": -1
> }{code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-3597) Incorrect error message when attempting to update Namespacedef

2021-02-22 Thread Mandar Ambawane (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mandar Ambawane resolved ATLAS-3597.

Resolution: Fixed

> Incorrect error message when attempting to update Namespacedef
> --
>
> Key: ATLAS-3597
> URL: https://issues.apache.org/jira/browse/ATLAS-3597
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
>
> # Create a new namespaceDef:
>  
> {code:java}
> curl --location --request POST 
> 'http://localhost:21000/api/atlas/v2/types/typedefs' \
> --header 'Content-Type: application/json' \
> --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
> --data-raw '{
> "namespaceDefs": [
> {
> "name": "namespace1",
> "description": "Sample namespace1",
> "serviceType": "NAMESPACES",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "namespaceAttr1",
> "typeName": "string",
> "options": {
> "applicableEntityTypes": "[\"hive_db\", 
> \"hive_table\"]",
> "maxStrLength": "50"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> },
> {
> "name": "namespaceAttr2",
> "typeName": "int",
> "options": {
> "applicableEntityTypes": "[\"hive_db\", 
> \"hive_column\"]"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> }
> ]
> }
> ]
> }'{code}
>  
> 2. Update the namespaceDef to remove an entry from applicable entityTypes in 
> 'namespaceAttr1': 
>  
> {code:java}
> curl --location --request PUT 
> 'http://localhost:21000/api/atlas/v2/types/typedefs' \
> --header 'Content-Type: application/json' \
> --header 'Authorization: Basic YWRtaW46YWRtaW4=' \
> --data-raw '{
> "namespaceDefs": [
> {
> "name": "namespace1",
> "description": "Sample namespace1",
> "serviceType": "NAMESPACES",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "namespaceAttr1",
> "typeName": "string",
> "options": {
> "applicableEntityTypes": "[\"hive_db\"]",
> "maxStrLength": "50"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> },
> {
> "name": "namespaceAttr2",
> "typeName": "int",
> "options": {
> "applicableEntityTypes": "[\"hive_db\", 
> \"hive_column\"]"
> },
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "includeInNotification": true,
> "isUnique": false
> }
> ]
> }
> ]
> }'{code}
>  
>  
> The following error message is thrown: 
>  
> {code:java}
> { "errorCode": "ATLAS-400-00-095", "errorMessage": "Cannot remove 
> applicableEntityTypes in Attribute Def: namespace1, defined in namespace: 
> {2}" }{code}
> error message should be: "Updating '*applicableEntityTypes*' in namespace: 
> \{namespace_name}, attribute: \{namespace_attribute} is not allowed."
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4074) [UI] Image download in Typesystem and Lineage has issue

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-4074:
---
Parent: ATLAS-4113
Issue Type: Sub-task  (was: Bug)

> [UI] Image download in Typesystem and Lineage has issue
> ---
>
> Key: ATLAS-4074
> URL: https://issues.apache.org/jira/browse/ATLAS-4074
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> Lineage_issue_shows_black_background_if_downloaded_image_with_search_applied.png,
>  Typesystem_issue_overlapped_entity_names_in_exported_image.png
>
>
> # In TypeSystem, downloaded image shows overlapped names of hosts/nodes if 
> the name length is too large.
>  # When user downloads the lineage with the search result shows highlighted 
> image with black background, also label is not properly visible due to black 
> background.
> PFA evidence files



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-3534) EntityREST changes to allow namespace attributes to be added to an entity instance

2021-02-22 Thread Mandar Ambawane (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mandar Ambawane resolved ATLAS-3534.

Resolution: Fixed

> EntityREST changes to allow namespace attributes to be added to an entity 
> instance
> --
>
> Key: ATLAS-3534
> URL: https://issues.apache.org/jira/browse/ATLAS-3534
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Aadarsh Jajodia
>Assignee: Mandar Ambawane
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4074) [UI] Image download in Typesystem and Lineage has issue

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar resolved ATLAS-4074.

Resolution: Resolved

This issue is fixed in ATLAS-4113

> [UI] Image download in Typesystem and Lineage has issue
> ---
>
> Key: ATLAS-4074
> URL: https://issues.apache.org/jira/browse/ATLAS-4074
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> Lineage_issue_shows_black_background_if_downloaded_image_with_search_applied.png,
>  Typesystem_issue_overlapped_entity_names_in_exported_image.png
>
>
> # In TypeSystem, downloaded image shows overlapped names of hosts/nodes if 
> the name length is too large.
>  # When user downloads the lineage with the search result shows highlighted 
> image with black background, also label is not properly visible due to black 
> background.
> PFA evidence files



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4056) [UI] While searching nodes in Lineage, previously searched/highlighted labels does not get clear

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar resolved ATLAS-4056.

Resolution: Resolved

This issue is fixed in ATLAS-4113

> [UI] While searching nodes in Lineage, previously searched/highlighted labels 
> does not get clear
> 
>
> Key: ATLAS-4056
> URL: https://issues.apache.org/jira/browse/ATLAS-4056
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: lineage_search_selection_issue.mkv
>
>
> When User searches a node in lineage, the node label get highlighted and also 
> a rectangle appears(expected), as soon as user searches another node, current 
> search selection works fine but the previous search selection remains 
> highlighted.
> PFA evidence file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4056) [UI] While searching nodes in Lineage, previously searched/highlighted labels does not get clear

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-4056:
---
Parent: ATLAS-4113
Issue Type: Sub-task  (was: Bug)

> [UI] While searching nodes in Lineage, previously searched/highlighted labels 
> does not get clear
> 
>
> Key: ATLAS-4056
> URL: https://issues.apache.org/jira/browse/ATLAS-4056
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: lineage_search_selection_issue.mkv
>
>
> When User searches a node in lineage, the node label get highlighted and also 
> a rectangle appears(expected), as soon as user searches another node, current 
> search selection works fine but the previous search selection remains 
> highlighted.
> PFA evidence file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-3376:
---
Attachment: 0001-ATLAS-3376-UI-V1-When-no-Catalogs-are-present-user-s.patch

> UI: When no Catalogs are present, user should be presented with an 
> appropriate message when trying to associate Category to Term.
> -
>
> Key: ATLAS-3376
> URL: https://issues.apache.org/jira/browse/ATLAS-3376
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3376-UI-V1-When-no-Catalogs-are-present-user-s.patch, 
> 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, 
> ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 
> 22-25-05.png, screenshot-newtab-2021.02.22-22_31_06.png
>
>
> If a user tries to associate a Category to a Term, and if not a single 
> Category has been created for any of the Glossaries, the user is presented 
> with the Category association screen but with no Categories for the user to 
> assign to the term. 
> This could create a confusion that there might be a Catalog present somewhere 
> but is not visible to the user, when actually no Catalogs exist. A 
> notification should be fired in this scenario, informing the user that no 
> Catalog exists that can be assigned to the term. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4133) [Atlas: Glossary Term Bulk Import] Disable the option to download upload template when category is chosen in glossary page

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-4133:
---
Parent: ATLAS-4154
Issue Type: Sub-task  (was: Bug)

> [Atlas: Glossary Term Bulk Import] Disable the option to download upload 
> template when category is chosen in glossary page
> --
>
> Key: ATLAS-4133
> URL: https://issues.apache.org/jira/browse/ATLAS-4133
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments: 
> 0001-Atlas-4133-UI-Glossary-Term-Bulk-Import-Disable-the-.patch, 
> Atlas-4133_1.png, Atlas-4133_2.png, Screenshot 2021-02-03 at 5.27.03 PM.png
>
>
> Since we support only bulk import of glossary-terms, it will be good to 
> disable the option to download and import template in UI
> !Screenshot 2021-02-03 at 5.27.03 PM.png|width=389,height=225!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4157) UI: 'Assign' button in 'Related Terms' window should be disabled once it is clicked.

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-4157:
---
Parent: ATLAS-4154
Issue Type: Sub-task  (was: Bug)

> UI: 'Assign' button in 'Related Terms' window should be disabled once it is 
> clicked.
> 
>
> Key: ATLAS-4157
> URL: https://issues.apache.org/jira/browse/ATLAS-4157
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: glossary-terms-assign-button-issue.png
>
>
> When user tries to add 'Related Terms', the 'Assign' button in the popup 
> window for Related Terms should be disabled once it is clicked.
> Currently it is still enabled while the update call is going on. This results 
> in multiple duplicate 'Related terms' entries when user double clicks the 
> Assign button.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-4157) UI: 'Assign' button in 'Related Terms' window should be disabled once it is clicked.

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar reassigned ATLAS-4157:
--

Assignee: Prasad P. Pawar

> 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
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: glossary-terms-assign-button-issue.png
>
>
> When user tries to add 'Related Terms', the 'Assign' button in the popup 
> window for Related Terms should be disabled once it is clicked.
> Currently it is still enabled while the update call is going on. This results 
> in multiple duplicate 'Related terms' entries when user double clicks the 
> Assign button.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4171) Authorisation : Bulk entity DELETE API doesn't delete authorised entities

2021-02-22 Thread Umesh Padashetty (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Umesh Padashetty updated ATLAS-4171:

Description: 
Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised 
entities when the list of authorised and unauthorised entities list is passed.

Curl: 
{code:java}
curl --location --request DELETE 
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
 \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header 
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0'  {code}
We need to implement one of the flag ignoreUnauthorisedGuids, 
isSkipFailedEntities, skipFailedEntities similar to Bulk DELETE API 

  was:
Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised 
entities when the list of authorised and unauthorised entities list is passed.

Curl: 
{code:java}
curl --location --request DELETE 
'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
 \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header 
'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0'  {code}
We need to implement one of the flag ignoreUnauthorisedGuids, 
isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity 
POST API 


> Authorisation : Bulk entity DELETE API doesn't delete authorised entities
> -
>
> Key: ATLAS-4171
> URL: https://issues.apache.org/jira/browse/ATLAS-4171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Umesh Padashetty
>Assignee: chaitali borole
>Priority: Major
>
> Similar to ATLAS-4172, Bulk entity DELETE API doesn't delete authorised 
> entities when the list of authorised and unauthorised entities list is passed.
> Curl: 
> {code:java}
> curl --location --request DELETE 
> 'https://host:port/api/atlas/v2/entity/bulk?guid=84632cfc-54a4-4695-873e-45de31ae0612=ad0f349c-1fe6-46f0-be6d-98ca2e754e1c=True'
>  \--header 'Authorization: Basic aHJ0XzE2OlBhc3N3b3JkQDEyMw==' \--header 
> 'Cookie: ATLASSESSIONID=node017mq7noo0meqnce52l5e8pvz1206.node0'  {code}
> We need to implement one of the flag ignoreUnauthorisedGuids, 
> isSkipFailedEntities, skipFailedEntities similar to Bulk DELETE API 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.

2021-02-22 Thread Durga Kadam (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288487#comment-17288487
 ] 

Durga Kadam commented on ATLAS-3376:


+1 patch working fine.

If no terms or categories are available, then user will receive pop-up message.

 

> UI: When no Catalogs are present, user should be presented with an 
> appropriate message when trying to associate Category to Term.
> -
>
> Key: ATLAS-3376
> URL: https://issues.apache.org/jira/browse/ATLAS-3376
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, 
> ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 
> 22-25-05.png, screenshot-newtab-2021.02.22-22_31_06.png
>
>
> If a user tries to associate a Category to a Term, and if not a single 
> Category has been created for any of the Glossaries, the user is presented 
> with the Category association screen but with no Categories for the user to 
> assign to the term. 
> This could create a confusion that there might be a Catalog present somewhere 
> but is not visible to the user, when actually no Catalogs exist. A 
> notification should be fired in this scenario, informing the user that no 
> Catalog exists that can be assigned to the term. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.

2021-02-22 Thread Durga Kadam (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Durga Kadam updated ATLAS-3376:
---
Attachment: screenshot-newtab-2021.02.22-22_31_06.png

> UI: When no Catalogs are present, user should be presented with an 
> appropriate message when trying to associate Category to Term.
> -
>
> Key: ATLAS-3376
> URL: https://issues.apache.org/jira/browse/ATLAS-3376
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, 
> ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 
> 22-25-05.png, screenshot-newtab-2021.02.22-22_31_06.png
>
>
> If a user tries to associate a Category to a Term, and if not a single 
> Category has been created for any of the Glossaries, the user is presented 
> with the Category association screen but with no Categories for the user to 
> assign to the term. 
> This could create a confusion that there might be a Catalog present somewhere 
> but is not visible to the user, when actually no Catalogs exist. A 
> notification should be fired in this scenario, informing the user that no 
> Catalog exists that can be assigned to the term. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.

2021-02-22 Thread Durga Kadam (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Durga Kadam updated ATLAS-3376:
---
Attachment: Screenshot from 2021-02-22 22-25-05.png

> UI: When no Catalogs are present, user should be presented with an 
> appropriate message when trying to associate Category to Term.
> -
>
> Key: ATLAS-3376
> URL: https://issues.apache.org/jira/browse/ATLAS-3376
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, 
> ATLAS-3376bug.png, Atlas-3376Fix.png, Screenshot from 2021-02-22 22-25-05.png
>
>
> If a user tries to associate a Category to a Term, and if not a single 
> Category has been created for any of the Glossaries, the user is presented 
> with the Category association screen but with no Categories for the user to 
> assign to the term. 
> This could create a confusion that there might be a Catalog present somewhere 
> but is not visible to the user, when actually no Catalogs exist. A 
> notification should be fired in this scenario, informing the user that no 
> Catalog exists that can be assigned to the term. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Review Request 73197: ATLAS-4171 : Authorisation : Bulk entity DELETE API doesn't delete authorised entities

2021-02-22 Thread Madhan Neethiraj 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73197/#review222623
---




repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
Line 520 (original), 520 (patched)


For better clarity, consider narrowing 'try' block to  #533:
  AtlasEntityHeader entityHeader = 
entityRetriever.toAtlasEntityHeaderWithClassifications(vertex);

  try {
AtlasAuthorizationUtils.verifyAccess(new 
AtlasEntityAccessRequest(typeRegistry, AtlasPrivilege.ENTITY_DELETE, 
entityHeader), "delete entity: guid=", guid);
  } catch (AtlasBaseException e) {
if (RequestContext.get().isSkipFailedEntities()) {
  if (LOG.isDebugEnabled()) {
LOG.debug("deleteByIds(): ignoring failure for entity {}: error 
code={}, message={}", guid, e.getAtlasErrorCode(), e.getMessage());
  }
  
  continue;
}

throw e;
  }
  
  deletionCandidates.add(vertex);



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
Lines 539 (patched)


createOrUpdate => deleteByIds


- Madhan Neethiraj


On Feb. 22, 2021, 9:48 a.m., chaitali wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73197/
> ---
> 
> (Updated Feb. 22, 2021, 9:48 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
> Nikhil Bonte, Nixon Rodrigues, Pinal Shah, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4171
> https://issues.apache.org/jira/browse/ATLAS-4171
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> We need to implement one of the flag ignoreUnauthorisedGuids, 
> isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity 
> POST API
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
>  e6fe306e3 
> 
> 
> Diff: https://reviews.apache.org/r/73197/diff/1/
> 
> 
> Testing
> ---
> 
> When skipFailedEntities passed as a flag true only authorised entities get 
> deleted skipping unauthorised .
> 
> 
> Thanks,
> 
> chaitali
> 
>

[jira] [Commented] (ATLAS-4163) Upgrade elasticsearch version to 6.8.14

2021-02-22 Thread Kevin Risden (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288413#comment-17288413
 ] 

Kevin Risden commented on ATLAS-4163:
-

[~sarath] thanks for triggering the precommit. It looks like it failed, but 
with no error - just like it stopped.

The end of the log message is:

{code:java}
...
[INFO] <<< jetty-maven-plugin:9.3.14.v20161028:deploy-war (start-jetty) < 
validate @ hbase-bridge <<<
[INFO] 
[INFO] 
[INFO] --- jetty-maven-plugin:9.3.14.v20161028:deploy-war (start-jetty) @ 
hbase-bridge ---
[INFO] Logging initialized @5359609ms
[INFO] Configuring Jetty for project: Apache Atlas Hbase Bridge
[INFO] Context path = /
[INFO] Tmp directory = 
/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hbase-bridge/target/tmp
[INFO] Web defaults = org/eclipse/jetty/webapp/webdefault.xml
[INFO] Web overrides =  none
[INFO] jetty-9.3.14.v20161028
log4j:WARN No appenders could be found for logger 
(org.apache.curator.framework.state.ConnectionStateManager).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
{code}

I know ASF Jenkins had some issues a few days ago so maybe thats related? I 
didn't look too much closer. I didn't see a way to retrigger the build either.

> Upgrade elasticsearch version to 6.8.14
> ---
>
> Key: ATLAS-4163
> URL: https://issues.apache.org/jira/browse/ATLAS-4163
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 2.1.0
>Reporter: Kevin Risden
>Priority: Minor
> Attachments: ATLAS-4163.patch
>
>
> ATLAS-4052 upgraded to Elasticsearch 6.8.3 which isn't the latest. There are 
> some CVEs associated with Elasticsearch 6.8.3 and so should upgrade to 6.8.14 
> which is the latest as of Feb 2021.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.

2021-02-22 Thread Prasad P. Pawar (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288299#comment-17288299
 ] 

Prasad P. Pawar commented on ATLAS-3376:


Hi,
The uploaded patch has the following fix
1) show message when the category is empty while association.
2) show message when the term is empty while associating on the category page, 
search result page & entity detail page.

> UI: When no Catalogs are present, user should be presented with an 
> appropriate message when trying to associate Category to Term.
> -
>
> Key: ATLAS-3376
> URL: https://issues.apache.org/jira/browse/ATLAS-3376
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, 
> ATLAS-3376bug.png, Atlas-3376Fix.png
>
>
> If a user tries to associate a Category to a Term, and if not a single 
> Category has been created for any of the Glossaries, the user is presented 
> with the Category association screen but with no Categories for the user to 
> assign to the term. 
> This could create a confusion that there might be a Catalog present somewhere 
> but is not visible to the user, when actually no Catalogs exist. A 
> notification should be fired in this scenario, informing the user that no 
> Catalog exists that can be assigned to the term. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar reassigned ATLAS-3376:
--

Assignee: Prasad P. Pawar  (was: Keval Bhatt)

> UI: When no Catalogs are present, user should be presented with an 
> appropriate message when trying to associate Category to Term.
> -
>
> Key: ATLAS-3376
> URL: https://issues.apache.org/jira/browse/ATLAS-3376
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, 
> ATLAS-3376bug.png, Atlas-3376Fix.png
>
>
> If a user tries to associate a Category to a Term, and if not a single 
> Category has been created for any of the Glossaries, the user is presented 
> with the Category association screen but with no Categories for the user to 
> assign to the term. 
> This could create a confusion that there might be a Catalog present somewhere 
> but is not visible to the user, when actually no Catalogs exist. A 
> notification should be fired in this scenario, informing the user that no 
> Catalog exists that can be assigned to the term. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-3376) UI: When no Catalogs are present, user should be presented with an appropriate message when trying to associate Category to Term.

2021-02-22 Thread Prasad P. Pawar (Jira) 


 [ 
https://issues.apache.org/jira/browse/ATLAS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-3376:
---
Attachment: ATLAS-3376bug.png
Atlas-3376Fix.png

> UI: When no Catalogs are present, user should be presented with an 
> appropriate message when trying to associate Category to Term.
> -
>
> Key: ATLAS-3376
> URL: https://issues.apache.org/jira/browse/ATLAS-3376
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: 
> 0001-ATLAS-3376-UI-When-no-Catalogs-are-present-user-shou.patch, 
> ATLAS-3376bug.png, Atlas-3376Fix.png
>
>
> If a user tries to associate a Category to a Term, and if not a single 
> Category has been created for any of the Glossaries, the user is presented 
> with the Category association screen but with no Categories for the user to 
> assign to the term. 
> This could create a confusion that there might be a Catalog present somewhere 
> but is not visible to the user, when actually no Catalogs exist. A 
> notification should be fired in this scenario, informing the user that no 
> Catalog exists that can be assigned to the term. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Review Request 73197: ATLAS-4171 : Authorisation : Bulk entity DELETE API doesn't delete authorised entities

2021-02-22 Thread chaitali 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73197/
---

Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, 
Nikhil Bonte, Nixon Rodrigues, Pinal Shah, and Sarath Subramanian.


Bugs: ATLAS-4171
https://issues.apache.org/jira/browse/ATLAS-4171


Repository: atlas


Description
---

We need to implement one of the flag ignoreUnauthorisedGuids, 
isSkipFailedEntities, skipFailedEntities similar to Bulk create/update entity 
POST API


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
 e6fe306e3 


Diff: https://reviews.apache.org/r/73197/diff/1/


Testing
---

When skipFailedEntities passed as a flag true only authorised entities get 
deleted skipping unauthorised .


Thanks,

chaitali

[jira] [Commented] (ATLAS-4168) Overlapping "Switch to Beta UI" link on pagination

2021-02-22 Thread Durga Kadam (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288232#comment-17288232
 ] 

Durga Kadam commented on ATLAS-4168:


+1 

issue resolved.

Note: Link provided to switch the UI is listed in Admin drop-down(top right 
corner) now.

> Overlapping "Switch to Beta UI" link on pagination
> --
>
> Key: ATLAS-4168
> URL: https://issues.apache.org/jira/browse/ATLAS-4168
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
>  Labels: Atlas-UI
> Attachments: 
> 0001-ATLAS-4168-Overlapping-Switch-to-Beta-UI-link-on-pag.patch, 
> 4168_1fix.png, 4168_2Fixed.png, screenshot-newtab-2021.02.18-18_42_14.png
>
>
> “Switch to Beta UI” link at the bottom right of the page overlaps pagination 
> links in search results page .
> PFA



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (ATLAS-4168) Overlapping "Switch to Beta UI" link on pagination

2021-02-22 Thread Durga Kadam (Jira) 


[ 
https://issues.apache.org/jira/browse/ATLAS-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288232#comment-17288232
 ] 

Durga Kadam edited comment on ATLAS-4168 at 2/22/21, 8:04 AM:
--

+1 

issue resolved.

Note: Link provided to switch the UI is listed in Admin drop-down(top right 
corner) instead of showing at bottom side.


was (Author: durgak):
+1 

issue resolved.

Note: Link provided to switch the UI is listed in Admin drop-down(top right 
corner) now.

> Overlapping "Switch to Beta UI" link on pagination
> --
>
> Key: ATLAS-4168
> URL: https://issues.apache.org/jira/browse/ATLAS-4168
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
>  Labels: Atlas-UI
> Attachments: 
> 0001-ATLAS-4168-Overlapping-Switch-to-Beta-UI-link-on-pag.patch, 
> 4168_1fix.png, 4168_2Fixed.png, screenshot-newtab-2021.02.18-18_42_14.png
>
>
> “Switch to Beta UI” link at the bottom right of the page overlaps pagination 
> links in search results page .
> PFA



--
This message was sent by Atlassian Jira
(v8.3.4#803005)