Skip to content

Added hashed index, a bit more of geo-indexes, possibility to give _cls #994

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 11, 2015

Conversation

MRigal
Copy link
Member

@MRigal MRigal commented May 7, 2015

This PR is also not a "full strike" PR. It will first need #946 to be merged, since it needs some Warning raising that are inside it.

I would like to add more serious warnings for the dropDups version, as some people may be surprised it is not supported anymore by MongoDB.

It also implements the remaining indexes types used with the shortcut +/-/$, by adding # for hashed, ( for geo2dsphere indexes and ) for geohaystack. [I've tried to use earth curve representation by the parenthesis for these geo-indexes, they were no other obvious symbols IMHO...]

Also, it allows to specify where one wants to have the "cls" index, by allowing something like ("field1", "cls", "field2"). We were forcing "cls" to be the first part of a compound key and this can be bad, for example when one has a compound shard key, but wants some compound indexes using only the first part of the shard key

Review on Reviewable

@landscape-bot
Copy link

Code Health
Code quality remained the same when pulling d830638 on MRigal:fix/cls-index-at-desired-position into d6b2d8d on MongoEngine:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.01%) to 91.7% when pulling d830638 on MRigal:fix/cls-index-at-desired-position into d6b2d8d on MongoEngine:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.01%) to 91.7% when pulling d830638 on MRigal:fix/cls-index-at-desired-position into d6b2d8d on MongoEngine:master.

@MRigal MRigal added this to the 0.10 milestone May 7, 2015
@MRigal MRigal force-pushed the fix/cls-index-at-desired-position branch from d830638 to f35d0b2 Compare June 1, 2015 21:13
@MRigal
Copy link
Member Author

MRigal commented Jun 1, 2015

The tests should pass, @seglberg @thedrow @DavidBord I'd be happy about a review (and eventually a merge)

@landscape-bot
Copy link

Code Health
Code quality remained the same when pulling f35d0b2 on MRigal:fix/cls-index-at-desired-position into 94eac1e on MongoEngine:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.07%) to 91.11% when pulling f35d0b2 on MRigal:fix/cls-index-at-desired-position into 94eac1e on MongoEngine:master.

@landscape-bot
Copy link

Code Health
Code quality remained the same when pulling a0257ed on MRigal:fix/cls-index-at-desired-position into 94eac1e on MongoEngine:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.07%) to 91.11% when pulling a0257ed on MRigal:fix/cls-index-at-desired-position into 94eac1e on MongoEngine:master.

@MRigal MRigal removed the In Progress label Jun 2, 2015
@MRigal
Copy link
Member Author

MRigal commented Jun 11, 2015

OK, since nobody is reacting on it, I'll merge it also

MRigal added a commit that referenced this pull request Jun 11, 2015
Added hashed index, a bit more of geo-indexes, possibility to give _cls
@MRigal MRigal merged commit 548a552 into MongoEngine:master Jun 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants