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/07/12 18:24:04 UTC

[jira] [Resolved] (USERGRID-445) Create an index merge operation

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

Jeffrey  resolved USERGRID-445.
-------------------------------
    Resolution: Won't Fix

Given the changes in the indexing approach this is no longer relevant.

> Create an index merge operation
> -------------------------------
>
>                 Key: USERGRID-445
>                 URL: https://issues.apache.org/jira/browse/USERGRID-445
>             Project: Usergrid
>          Issue Type: Story
>            Reporter: Todd Nine
>
> There is currently no way to remove older indexes and retain only a single index after allocating a new index. We can build this functionality out of our index rebuild, but by adding an upper bound to stop indexing.  This should perform the following high level operations.
> # Find the lowest entity version in the current write alias
> # Perform an index rebuild on all collections, stopping at the lowest version from the previous step
> # After a rebuild has been complete, remove all indexes that are not on the current write alias



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)