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

Nikhil Bonte commented on ATLAS-3175:
-------------------------------------

[~umesh.padashetty]


For 0.8 It is valid scenario as we have cashing mechanism for getting entity 
count. This is causing UI to not update count immediately after refreshing page.
Default cache is 900 seconds which is configurable by using property 
"atlas.metric.query.cache.ttlInSecs".


I tried to reproduce on 2.0, I could not reproduce it as cashing is not the 
part of this branch. See ATLAS-3052.
After refreshing page I can see updated count in "Search by Type" dropdown.

> UI: Incorrect count shown beside the Type and Classification dropdown list in 
> search
> ------------------------------------------------------------------------------------
>
>                 Key: ATLAS-3175
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3175
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Umesh Padashetty
>            Assignee: Keval Bhatt
>            Priority: Major
>             Fix For: 0.8.4, 1.2.0, 2.0.0
>
>         Attachments: Screenshot 2019-04-26 at 3.19.27 PM.png, Screenshot 
> 2019-04-26 at 3.20.13 PM.png
>
>
> Steps for reproduction:
>  # Login to Atlas UI
>  # Click on Advanced Search
>  # Click on "Search By Type"
>  # Check the count against kafka_topic
>  # Create a new kafka_topic entity
>  # Refresh the page
>  # Again check the count against kafka_topic under "Search By Type"
> It is taking a long time for the count to be updated in the UI. Browser clear 
> cache and incognito mode did not help
>  # The type count under "Search By Type" drop-down should be updated when a 
> new entity type is created. This is happening for entities created via UI as 
> well as via HOOK
>  # Classification count under "Search By Classification" should be updated 
> when an entity is classified. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to