Skip to content

Do not get sorting configuration repeatedly when calling mapReduce method #3960

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 1 commit into from

Conversation

blu10ph
Copy link
Contributor

@blu10ph blu10ph commented Feb 10, 2022

When calling the mapReduce method, when the operation determines whether there is a sorting operation, the sorting configuration will be obtained. When setting the MapReduce sorting configuration, if there is repeated acquisition, it is modified to use the obtained sorting configuration.

When calling the mapReduce method, when the operation determines whether there is a sorting operation, the sorting configuration will be obtained. When setting the MapReduce sorting configuration, if there is repeated acquisition, it is modified to use the obtained sorting configuration.
@pivotal-cla
Copy link

@blu10ph Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 10, 2022
@pivotal-cla
Copy link

@blu10ph Thank you for signing the Contributor License Agreement!

@christophstrobl
Copy link
Member

Thank you - good catch!

@christophstrobl christophstrobl removed the status: waiting-for-triage An issue we've not yet triaged label Feb 10, 2022
@christophstrobl christophstrobl self-assigned this Feb 10, 2022
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 10, 2022
@blu10ph
Copy link
Contributor Author

blu10ph commented Feb 10, 2022

You're welcome. Same problem with branch 4.0.x.

christophstrobl pushed a commit that referenced this pull request Feb 11, 2022
Apply already mapped sort for map reduce instead of running the source document through the mapping layer again.

Closes: #3960
christophstrobl pushed a commit that referenced this pull request Feb 11, 2022
Apply already mapped sort for map reduce instead of running the source document through the mapping layer again.

Closes: #3960
@christophstrobl
Copy link
Member

Thank you @blu10ph for your contribution! Merged to main development line and back ported to 3.3.x and 3.2.x.

@christophstrobl christophstrobl removed the status: waiting-for-triage An issue we've not yet triaged label Feb 11, 2022
@christophstrobl christophstrobl added this to the 3.2.9 (2021.0.9) milestone Feb 11, 2022
christophstrobl pushed a commit that referenced this pull request Feb 17, 2022
Apply already mapped sort for map reduce instead of running the source document through the mapping layer again.

Closes: #3960
@blu10ph blu10ph deleted the patch-3 branch February 22, 2022 00:42
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.

4 participants