Fix bug when calling aggregateByGeometry after a mapper is set#473
Merged
Conversation
joker234
force-pushed
the
bug_autoaggregation
branch
from
022be16 to
47699eb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes a crash caused by the autoaggregation code which is triggered when
aggregateByGeometryis called after specifying amapfunction in a query. It's solved by just re-applying the mappers (or flatMappers) after the geometry splitting phase.See also #451
Checklist
I have commented my codeI have written javadoc (required for public classes and methods)I have made corresponding changes to the documentationI have updated the CHANGELOG.mdI have adjusted the examples or created an issue in the corresponding repositoryI have adjusted the benchmark or created an issue in the corresponding repository