-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Change on how to do $group on compound keys #292
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
Conversation
Thanks so much for this catch! I'd like to get this merged in, but if you could sign the 10gen/MongoDB contributor agreement, that would be really great. Cheers, |
Hey Sam, I've filled the agreement. Regards, |
Thanks so much! I've gone ahead and merged this. Cheers, On Wednesday, October 10 2012, 00:04:14, Mikael Koskinen wrote:
Sam Kleinman (@tychoish) |
* (DOCS-14993): Update WT Docs link to current version WIP * reset version-dev variable
* (DOCS-14993): Update WT Docs link to current version WIP * reset version-dev variable
* DOCSP-38149 Add documentation for mongosync cutover processs * DOCSP-38149 updates for feedback * DOCSP-38149 updates for feedback * DOCSP-38149 updates for JD's copy feedback
* (DOCSP-32609): mongosh 1.10.6 release notes * change ticket number * update snooty.toml * update snooty.toml * line breaks
…292) * DOP-1883: revised following convo with Andrew A. * adding the using-the-bi redirect back in
* (DOCSP-10561): Kubernetes Operator v1.5.3 release notes * Copy/tech review
* (DOCSP-10561): Kubernetes Operator v1.5.3 release notes * Copy/tech review
The currently documented example for creating a $group with compound keys doesn't work with 2.2. The change is based on this discussion: https://groups.google.com/forum/?fromgroups=#!topic/mongodb-user/1cYch580h0w