[jira] [Commented] (ATLAS-735) UI showing incorrect results if two queries are executed.(first query succeeds but second should fail)

["Keval Bhatt (JIRA)" <ji...@apache.org>]

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

Keval Bhatt commented on ATLAS-735:
-----------------------------------

[~ayubkhan]  / [~yhemanth] / [~madhan.neethiraj] This could be a issue with new UI as well: 
There are 2 simple solutions from UI to this : 
1) We can disable search button till the time we get the search results from API - this way there won't be 2 consecutive requests for  searching entities. 

2) If user searches for a DSL / fulltext query and even before getting the response from API, if user sends another request. In this case we can abort the first request from client side and then send the second request (Note: even if we abort the first request from client side, processing might still continue on server side).   
This way we will see search results only for the latest request sent by the user. 


> UI showing incorrect results if two queries are executed.(first query succeeds but second should fail)
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-735
>                 URL: https://issues.apache.org/jira/browse/ATLAS-735
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.7-incubating
>            Reporter: Ayub Khan
>            Assignee: Keval Bhatt
>         Attachments: DSL-query.gif
>
>
> Steps to repro:
> 1. Through search tab, fire a valid dsl search query(eg: hive_table) and make sure this query response takes time(~30 seconds)
> 2. Before the response comes for the first query, search for another invalid query.(this will fail with 400 error).
> 3. Now when the response for first query returns, the UI still renders the first query's response as if it is a response to second query which seems incorrect. And this might lead to a confusion from a customer's perspective.
> This can be an issue from a customer's perspective and the probability of happening in production is pretty high.
> If the above steps are not clear, I am attaching a GIF which captures the steps to repro. Please take a look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)