[JAVA-3555] Work around changes to mapReduce implementation in the 4.4. server Created: 17/Dec/19 Updated: 28/Oct/23 Resolved: 18/Dec/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Query Operations |
| Affects Version/s: | None |
| Fix Version/s: | 3.12.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||
| Description |
|
MongoDB 4.4 introduces several changes to mapReduce implementation which break assumptions in both the driver's implementation of mapReduce and the tests. This ticket is to address those changes |
| Comments |
| Comment by Githook User [ 15/Jan/20 ] |
|
Author: {'name': 'Jeff Yemin', 'username': 'jyemin', 'email': 'jeff.yemin@10gen.com'}Message: Ensure collection exists prior to outputting mapReduce results to it This works around a behavioral change in the 4.4 server's mapReduce
|
| Comment by Githook User [ 15/Jan/20 ] |
|
Author: {'name': 'Jeff Yemin', 'username': 'jyemin', 'email': 'jeff.yemin@10gen.com'}Message: Make map and reduce functions more realistic in mapReduce collation test The functions that were used exposed a subtle difference in server behavior
|
| Comment by Githook User [ 15/Jan/20 ] |
|
Author: {'name': 'Jeff Yemin', 'username': 'jyemin', 'email': 'jeff.yemin@10gen.com'}Message: Remove assumptions about result order for mapReduce Several driver tests assume mapReduce results are returned in Remove those assumptions by comparing the results as a Set instead of a List
|
| Comment by Githook User [ 15/Jan/20 ] |
|
Author: {'name': 'Jeff Yemin', 'username': 'jyemin', 'email': 'jeff.yemin@10gen.com'}Message: Avoid including default or null values in mapReduceCommand
|
| Comment by Githook User [ 18/Dec/19 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@10gen.com', 'username': 'jyemin'}Message: Ensure collection exists prior to outputting mapReduce results to it This works around a behavioral change in the 4.4 server's mapReduce
|
| Comment by Githook User [ 18/Dec/19 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@10gen.com', 'username': 'jyemin'}Message: Make map and reduce functions more realistic in mapReduce collation test The functions that were used exposed a subtle difference in server behavior
|
| Comment by Githook User [ 18/Dec/19 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@10gen.com', 'username': 'jyemin'}Message: Remove assumptions about result order for mapReduce Several driver tests assume mapReduce results are returned in Remove those assumptions by comparing the results as a Set instead of a List
|
| Comment by Githook User [ 18/Dec/19 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@10gen.com', 'username': 'jyemin'}Message: Avoid including default or null values in mapReduceCommand
|