You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "Michael Russo (JIRA)" <ji...@apache.org> on 2016/05/11 06:11:12 UTC
[jira] [Closed] (USERGRID-447) Fix data migration format lifecycle
on initial setup
[ https://issues.apache.org/jira/browse/USERGRID-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Russo closed USERGRID-447.
----------------------------------
> Fix data migration format lifecycle on initial setup
> ----------------------------------------------------
>
> Key: USERGRID-447
> URL: https://issues.apache.org/jira/browse/USERGRID-447
> Project: Usergrid
> Issue Type: Story
> Affects Versions: 2.1.0
> Reporter: Todd Nine
> Assignee: Michael Russo
> Priority: Minor
> Fix For: 2.1.1
>
>
> During our initial setup, we perform the following phases.
> # Setup keyspaces and column families
> # Set up the root application
> Admins then have to run the migration via PUT /system/migrate/run
> This causes an unnecessary migration from V0 to current. Instead, on our initial setup in CPSetup.java, we should perform the following.
> # Create keyspaces and column families
> # Perform the data migration, which will simply set the current max version BEFORE data is written
> # Write the initial root application state
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)