remove generate id for aggregation #240
Open
Conversation
This file contains 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
MXPOL
force-pushed
the
master
branch
2 times, most recently
from
46200f8 to
bf6d4e7
Compare
MXPOL
force-pushed
the
master
branch
9 times, most recently
from
949071c to
8ff9119
Compare
MXPOL
force-pushed
the
master
branch
4 times, most recently
from
9f52c5a to
a29fba4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Due to a problem we had in content manager, we added _id when returning a query result without _id.
This issue relevant only for find, and not for aggregate.
for aggregate, we get misleading information - because we are generating _id even though the query result shouldn't have _id
For example, group by 'field1' - the response should have only field1 as column, and the _id we are generating for them is not relevant.