You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@usergrid.apache.org by "Jeffrey (JIRA)" <ji...@apache.org> on 2015/11/02 18:15:28 UTC

[jira] [Updated] (USERGRID-1082) Fix paging scheme for deletes to not make duplicate delete requests

     [ https://issues.apache.org/jira/browse/USERGRID-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey  updated USERGRID-1082:
-------------------------------
    Sprint: 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
>
> 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)