Skip to content

DATAMONGO-1824 - Assert compatibility with MongoDB 3.6 #515

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

Closed
wants to merge 4 commits into from

Conversation

christophstrobl
Copy link
Member

We now use the driver native option for aggregate instead of a plain command execution. This is necessary as of MongoDB 3.6 the cursor option is required for aggregations changing the return and execution model.

Still we maintain the raw values of AggregationResult as we used to do before. However, relying on executeCommand to change aggregation behavior in custom code will no longer work.

Along the the way we opened up Aggregation itself to expose the AggregationOptions in use und deprecated the $pushAll option on Update since it has been removed in MongoDB 3.6.


Tested against MongoDB: 3.6.RC3, 3.4.9 and 3.2.6

christophstrobl and others added 4 commits November 15, 2017 13:16
…driver call to support MongoDB 3.6.

We now use the driver native option for aggregate instead of a plain command execution. This is necessary as of MongoDB 3.6 the cursor option is required for aggregations changing the return and execution model.

Still we maintain the raw values of AggregationResult as we used to do before. However, relying on executeCommand to change aggregation behavior in custom code will no longer work.

Tested against MongoDB: 3.6.RC3, 3.4.9 and 3.2.6

Along the the way we opened up Aggregation itself to expose the AggregationOptions in use und deprecated the $pushAll option on Update since it has been removed in MongoDB 3.6.
Introduce Aggregation.toPipeline(…) method to render the aggregation pipeline directly. Adapt code using aggregation pipelines. Consider allowDiskUse and batchSize cursor options. Move introduction versions to 2.1. Mention migration to cursor-based aggregation in reference docs.
mp911de pushed a commit that referenced this pull request Nov 17, 2017
…llection.aggregate(…) to support MongoDB 3.6.

We now use the driver native option for aggregate instead of a plain command execution. This is necessary as of MongoDB 3.6 the cursor option is required for aggregations changing the return and execution model.

Still we maintain the raw values of AggregationResult as we used to do before. However, relying on executeCommand to change aggregation behavior in custom code will no longer work.

Tested against MongoDB: 3.6.RC3, 3.4.9 and 3.2.6

Along the the way we opened up Aggregation itself to expose the AggregationOptions in use und deprecated the $pushAll option on Update since it has been removed in MongoDB 3.6.

Original pull request: #515.
mp911de pushed a commit that referenced this pull request Nov 17, 2017
mp911de added a commit that referenced this pull request Nov 17, 2017
Introduce Aggregation.toPipeline(…) method to render the aggregation pipeline directly. Adapt code using aggregation pipelines. Consider allowDiskUse and batchSize cursor options. Move introduction versions to 2.1. Mention migration to cursor-based aggregation in reference docs.

Original pull request: #515.
@mp911de
Copy link
Member

mp911de commented Nov 17, 2017

That's merged and polished now.

@mp911de mp911de closed this Nov 17, 2017
@mp911de mp911de deleted the issue/DATAMONGO-1824 branch November 17, 2017 12:40
@chengbinTechnology
Copy link

But The Project is Compiler by jdk 1.7, Version 2.0+ not supported

@chengbinTechnology
Copy link

Can you release a version that supports jdk 1. 7

@mp911de
Copy link
Member

mp911de commented May 22, 2018

These changes are also shipped with Spring Data MongoDB version 1.10.10 and higher requiring Java 6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants