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

["Ayub Khan (JIRA)" <ji...@apache.org>]

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

Ayub Khan edited comment on ATLAS-735 at 6/27/16 2:35 PM:
----------------------------------------------------------

[~yhemanth] This seems to be not happening on new UI, not sure what changed. I have tried with 3000 hive tables and search query taking more than 30 seconds.


was (Author: ayubkhan):
[~yhemanth] This seems to be not happening on new UI, not sure what changed. I have tried with 3000 hive tables and search query taking more than 1 minute.

> 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: ATLAS-735.patch, 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)