Sharmadha Sainath created ATLAS-1816:
----------------------------------------
Summary: UI,excludeDeletedEntities : Next button in Basic query
result view is not working if result query has DELETED entities
Key: ATLAS-1816
URL: https://issues.apache.org/jira/browse/ATLAS-1816
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
1. Created 50 tables
2. Deleted 5 tables which are shown in the first page of the basic query search.
3. Fired a basic query : type name = hive_table
4. Page showed only 20 results. Because there were only 20 results , Next
button used to navigate to next page was disabled.
5. Checked the "Include historical entities" check box. 25 results displayed
but still Next button was disabled.
6. Hence even if one DELETED entity is returned in the basic query , navigation
to next table becomes impossible.
If all returned entities in the limit 25 are ACTIVE , Next button is enabled.
For example out of 150 entities , 5 entities are DELETED . Those DELETED
entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is
possible . From there on , even though "Include Historical entities" is
checked and 25 results are returned for the page , next button is disabled.
[ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the
reasons for this bug.
Advanced(DSL) query result window is not suffering from this issue probably
because excludeDeletedEntities parameter is not honored.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
