-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add unique indexing * Add unique indexing for username/email * WIP * Finish unique indexes * Notes on how to upgrade to 2.3.0 safely * index on unique-indexes: c454180 Revert "Log objects rather than JSON stringified objects (#1922)" * reconfigure username/email tests * Start dealing with test shittyness * Remove tests for files that we are removing * most tests passing * fix failing test * Make specific server config for tests async * Fix more tests * fix more tests * Fix another test * fix more tests * Fix email validation * move some stuff around * Destroy server to ensure all connections are gone * Fix broken cloud code * Save callback to variable * no need to delete non existant cloud * undo * Fix all tests where connections are left open after server closes. * Fix issues caused by missing gridstore adapter * Update guide for 2.3.0 and fix final tests * use strict * don't use features that won't work in node 4 * Fix syntax error * Fix typos * Add duplicate finding command * Update 2.3.0.md
- Loading branch information
1 parent
6415a35
commit 7e868b2
Showing
37 changed files
with
1,738 additions
and
1,528 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,82 @@ | ||
# Upgrading Parse Server to version 2.3.0 | ||
|
||
Parse Server version 2.3.0 begins using unique indexes to ensure User's username and email are unique. This is not a backwards incompatable change, but it may in some cases cause a significant performance regression until the index finishes building. Building the unique index before upgrading your Parse Server version will eliminate the performance impact, and is a recommended step before upgrading any app to Parse Server 2.3.0. New apps starting with version 2.3.0 do not need to take any steps before beginning their project. | ||
|
||
If you are using MongoDB in Cluster or Replica Set mode, we recommend reading Mongo's [documentation on index building](https://docs.mongodb.com/v3.0/tutorial/build-indexes-on-replica-sets/) first. If you are not using these features, you can execute the following commands from the Mongo shell to build the unique index. You may also want to create a backup first. | ||
|
||
```js | ||
// Select the database that your Parse App uses | ||
use parse; | ||
|
||
// Select the collection your Parse App uses for users. For migrated apps, this probably includes a collectionPrefix. | ||
var coll = db['your_prefix:_User']; | ||
|
||
// You can check if the indexes already exists by running coll.getIndexes() | ||
coll.getIndexes(); | ||
|
||
// The indexes you want should look like this. If they already exist, you can skip creating them. | ||
{ | ||
"v" : 1, | ||
"unique" : true, | ||
"key" : { | ||
"username" : 1 | ||
}, | ||
"name" : "username_1", | ||
"ns" : "parse.your_prefix:_User", | ||
"background" : true, | ||
"sparse" : true | ||
} | ||
|
||
{ | ||
"v" : 1, | ||
"unique" : true, | ||
"key" : { | ||
"email" : 1 | ||
}, | ||
"name" : "email_1", | ||
"ns" : "parse.your_prefix:_User", | ||
"background" : true, | ||
"sparse" : true | ||
} | ||
|
||
// Create the username index. | ||
// "background: true" is mandatory and avoids downtime while the index builds. | ||
// "sparse: true" is also mandatory because Parse Server uses sparse indexes. | ||
coll.ensureIndex({ username: 1 }, { background: true, unique: true, sparse: true }); | ||
|
||
// Create the email index. | ||
// "background: true" is still mandatory. | ||
// "sparse: true" is also mandatory both because Parse Server uses sparse indexes, and because email addresses are not required by the Parse API. | ||
coll.ensureIndex({ email: 1 }, { background: true, unique: true, sparse: true }); | ||
``` | ||
|
||
There are some issues you may run into during this process: | ||
|
||
## Mongo complains that the index already exists, but with different options | ||
|
||
In this case, you will need to remove the incorrect index. If your app relies on the existence of the index in order to be performant, you can create a new index, with "-1" for the direction of the field, so that it counts as different options. Then, drop the conflicting index, and create the unique index. | ||
|
||
## There is already non-unique data in the username or email field | ||
|
||
This is possible if you have explicitly set some user's emails to null. If this is bogus data, and those null fields shoud be unset, you can unset the null emails with this command. If your app relies on the difference between null and unset emails, you will need to upgrade your app to treat null and unset emails the same before building the index and upgrading to Parse Server 2.3.0. | ||
|
||
```js | ||
coll.update({ email: { $exists: true, $eq: null } }, { $unset: { email: '' } }, { multi: true }) | ||
``` | ||
|
||
## There is already non-unique data in the username or email field, and it's not nulls | ||
|
||
This is possible due to a race condition in previous versions of Parse Server. If you have this problem, it is unlikely that you have a lot of rows with duplicate data. We recommend you clean up the data manually, by removing or modifying the offending rows. | ||
|
||
This command, can be used to find the duplicate data: | ||
|
||
```js | ||
coll.aggregate([ | ||
{$match: {"username": {"$ne": null}}}, | ||
{$group: {_id: "$username", uniqueIds: {$addToSet: "$_id"}, count: {$sum: 1}}}, | ||
{$match: {count: {"$gt": 1}}}, | ||
{$project: {id: "$uniqueIds", username: "$_id", _id : 0} }, | ||
{$unwind: "$id" }, | ||
{$out: '_duplicates'} // Save the list of duplicates to a new, "_duplicates collection. Remove this line to just output the list. | ||
], {allowDiskUse:true}) | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.