[
https://issues.apache.org/jira/browse/USERGRID-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627260#comment-14627260
]
Todd Nine commented on USERGRID-559:
------------------------------------
Since there was no way to do this via a "modified time" in our storage system,
we have to iterate all entities, and filter them by updated date. The system
will filter any entity with an update < the specified update time. To create a
new job with an updated time, you must specify the following payload when
creating a job
{code}
{ "updated": < last updated epoch in millis> }
{code}
> [FIXED?] Add re-index resume
> ----------------------------
>
> Key: USERGRID-559
> URL: https://issues.apache.org/jira/browse/USERGRID-559
> Project: Usergrid
> Issue Type: Story
> Reporter: Todd Nine
> Assignee: Todd Nine
> Labels: Fixed?
> Fix For: 2.1.0
>
>
> We need the ability to resume re-indexing. To do this, we should make the
> AllEntitiesObservable allow for resume by default. This way if the node
> performing the migration fails, it can be restarted on another node.
> Note that we also need a way to clear state via REST, so that we can restart
> our indexing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
