-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
With this change, the mapReduce command will no longer return execution statistics as part of the command response object. Instead users will be requested to run mapReduce via explain command with executionStats.
As discussed with Jeff Yemin, this will break a method used by the legacy Java driver API to retrieve stats. It is possible that other drivers will be affected as well.
Description of Linked Ticket
These will be replaced by support for mapReduce explain with executionStats
- depends on
-
CDRIVER-3444 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
CSHARP-2864 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
CXX-1884 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
GODRIVER-1425 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
MOTOR-469 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
NODE-2367 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
PHPLIB-515 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
PYTHON-2072 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
RUBY-2036 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
SERVER-44635 MR in Agg: Remove in-line mapReduce execution statistics
- Closed
-
JAVA-3522 Stop assuming presence of inline mapReduce execution statistics
- Closed