[
https://issues.apache.org/jira/browse/USERGRID-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696254#comment-14696254
]
Michael Russo commented on USERGRID-906:
----------------------------------------
Plugin specific migrations were exposed. To get around this, PUT
/system/migrate/run/appinfo-migration can be ran to again migrate appinfos.
Closing.
> 2.1 Unable to read previous version app info
> --------------------------------------------
>
> Key: USERGRID-906
> URL: https://issues.apache.org/jira/browse/USERGRID-906
> Project: Usergrid
> Issue Type: Bug
> Reporter: Michael Russo
>
> In 2.1 application info is moved from management collection 'appinfos' to
> 'application_info'. Consequently, 2.1 always reads/writes to
> 'application_info' for new application/orgs.
> When running data migration, this prevents 2.0 and 2.1 being fully functional
> side by side. Example:
> 1. Have 2.0 running.
> 2. Run data migration / re-index on 2.1 box pointing to same cluster as 2.0
> 3. Everything is good and 2.1 and read everything from 2.0 and 2.0 still
> functions as normal.
> 4. Now add a new app via 2.0.
> 5. 2.1 cannot see this new app added via 2.0. Also causes re-index via 2.1
> to not see this app.
> The only way to make the app from legacy app infos visible is to run another
> data migration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
