[
https://issues.apache.org/jira/browse/USERGRID-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey updated USERGRID-1082:
-------------------------------
Sprint: (was: Critical)
> Fix paging scheme for deletes to not make duplicate delete requests
> -------------------------------------------------------------------
>
> Key: USERGRID-1082
> URL: https://issues.apache.org/jira/browse/USERGRID-1082
> Project: Usergrid
> Issue Type: Story
> Reporter: Mike Dunker
> Priority: Critical
>
> For changes made in USERGRID-1080, we loop through the edges and entity to
> delete by successive queries. The query is ordered by timestamp, and each
> successive query only looks at data with a timestamp greater than or equal to
> the previously seen timestamps. The last entity/edge on the previous page,
> along with any entity/edges that have the same timestamp, will show up in the
> next page. We currently will attempt to delete those more than once (should
> be approximately 1 out of every 1000 edges).
> This ticket is to fix it by either not adding duplicates to the deIndex list
> or skipping duplicates when deindexing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
