Why do aggregating a filtered dataset lose the filters of it?
up vote
0
down vote
favorite
I have this collection:
// collection
[
{_id: 1, name: 'Luigi', childs: [{name: 'one'}, {name: 'two'}], dad_id: 9]},
{_id: 1, name: 'Mario', childs: [{name: 'four'}, {name: 'five'}], dad_id: 8]},
{_id: 1, name: 'Alessandro', childs: [{name: 'seven'}, {name: 'six'}], dad_id: 9]},
]
and apply this filter to it
result = collection.find({ dad_id: 9 })
Then I want to aggregate the results and get all the childs singularly, I start with unwinding them
(then I 'll make a projection, etc..) but I already encounter a behavior that I do not understand:
the result contains also the documents with dad_id
is 8, even if they were already excluded by my query.
result.aggregate([
{ "$unwind"=> "$childs" },
]).each do |e| ... end
// => [
{_id: 1, name: 'Luigi', childs: {name: 'one'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'two'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'five'}, dad_id: 8]},
{_id: 1, name: 'Luigi', childs: {name: 'four'}, dad_id: 8]},
{_id: 1, name: 'Luigi', childs: {name: 'seven'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'six'}, dad_id: 9]},
]
What am I missing?
ruby mongodb
|
show 1 more comment
up vote
0
down vote
favorite
I have this collection:
// collection
[
{_id: 1, name: 'Luigi', childs: [{name: 'one'}, {name: 'two'}], dad_id: 9]},
{_id: 1, name: 'Mario', childs: [{name: 'four'}, {name: 'five'}], dad_id: 8]},
{_id: 1, name: 'Alessandro', childs: [{name: 'seven'}, {name: 'six'}], dad_id: 9]},
]
and apply this filter to it
result = collection.find({ dad_id: 9 })
Then I want to aggregate the results and get all the childs singularly, I start with unwinding them
(then I 'll make a projection, etc..) but I already encounter a behavior that I do not understand:
the result contains also the documents with dad_id
is 8, even if they were already excluded by my query.
result.aggregate([
{ "$unwind"=> "$childs" },
]).each do |e| ... end
// => [
{_id: 1, name: 'Luigi', childs: {name: 'one'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'two'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'five'}, dad_id: 8]},
{_id: 1, name: 'Luigi', childs: {name: 'four'}, dad_id: 8]},
{_id: 1, name: 'Luigi', childs: {name: 'seven'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'six'}, dad_id: 9]},
]
What am I missing?
ruby mongodb
Which driver is this? You should not even be able to do that. It's certainly not standard with any other language driver and since it is not working, then this "feature" is not even implemented properly. You're supposed to use a$match
stage in the aggregation pipeline. And MongoDB "views" are something completely different.
– Neil Lunn
Nov 22 at 10:54
Yeah about the view your are right, I am calling them poorly. I will edit the question. The driver any way is ruby. My question remain the same but change the word view with "dataset"
– ciaoben
Nov 22 at 10:56
It's not a matter of what you are calling it, but rather that no officially supported driver has any such feature as you are claiming. So what you need to tell us is "where did you install this driver from?"
– Neil Lunn
Nov 22 at 10:58
@NeilLunn it is the official gem "mongo" version 2.3.0
– ciaoben
Nov 22 at 11:01
Yeah was just looking at it and it's pretty bad that this is exposed this way. As stated, you are not actually meant to even try and use it that way, and no other language driver even allows it. Instead you$match
in the pipeline itselfcollection.aggregate([{ "$match" => { dad_id: 9 } },{ "$unwind"=> "$childs" }])
. So the "bugginess" in the driver is thefind()
returns a "Collection View" which exposes anaggregate()
method which should not actually be there. Do it with theCollection
method like everyone else does.
– Neil Lunn
Nov 22 at 11:12
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have this collection:
// collection
[
{_id: 1, name: 'Luigi', childs: [{name: 'one'}, {name: 'two'}], dad_id: 9]},
{_id: 1, name: 'Mario', childs: [{name: 'four'}, {name: 'five'}], dad_id: 8]},
{_id: 1, name: 'Alessandro', childs: [{name: 'seven'}, {name: 'six'}], dad_id: 9]},
]
and apply this filter to it
result = collection.find({ dad_id: 9 })
Then I want to aggregate the results and get all the childs singularly, I start with unwinding them
(then I 'll make a projection, etc..) but I already encounter a behavior that I do not understand:
the result contains also the documents with dad_id
is 8, even if they were already excluded by my query.
result.aggregate([
{ "$unwind"=> "$childs" },
]).each do |e| ... end
// => [
{_id: 1, name: 'Luigi', childs: {name: 'one'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'two'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'five'}, dad_id: 8]},
{_id: 1, name: 'Luigi', childs: {name: 'four'}, dad_id: 8]},
{_id: 1, name: 'Luigi', childs: {name: 'seven'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'six'}, dad_id: 9]},
]
What am I missing?
ruby mongodb
I have this collection:
// collection
[
{_id: 1, name: 'Luigi', childs: [{name: 'one'}, {name: 'two'}], dad_id: 9]},
{_id: 1, name: 'Mario', childs: [{name: 'four'}, {name: 'five'}], dad_id: 8]},
{_id: 1, name: 'Alessandro', childs: [{name: 'seven'}, {name: 'six'}], dad_id: 9]},
]
and apply this filter to it
result = collection.find({ dad_id: 9 })
Then I want to aggregate the results and get all the childs singularly, I start with unwinding them
(then I 'll make a projection, etc..) but I already encounter a behavior that I do not understand:
the result contains also the documents with dad_id
is 8, even if they were already excluded by my query.
result.aggregate([
{ "$unwind"=> "$childs" },
]).each do |e| ... end
// => [
{_id: 1, name: 'Luigi', childs: {name: 'one'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'two'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'five'}, dad_id: 8]},
{_id: 1, name: 'Luigi', childs: {name: 'four'}, dad_id: 8]},
{_id: 1, name: 'Luigi', childs: {name: 'seven'}, dad_id: 9]},
{_id: 1, name: 'Luigi', childs: {name: 'six'}, dad_id: 9]},
]
What am I missing?
ruby mongodb
ruby mongodb
edited Nov 22 at 10:57
asked Nov 22 at 10:47
ciaoben
764919
764919
Which driver is this? You should not even be able to do that. It's certainly not standard with any other language driver and since it is not working, then this "feature" is not even implemented properly. You're supposed to use a$match
stage in the aggregation pipeline. And MongoDB "views" are something completely different.
– Neil Lunn
Nov 22 at 10:54
Yeah about the view your are right, I am calling them poorly. I will edit the question. The driver any way is ruby. My question remain the same but change the word view with "dataset"
– ciaoben
Nov 22 at 10:56
It's not a matter of what you are calling it, but rather that no officially supported driver has any such feature as you are claiming. So what you need to tell us is "where did you install this driver from?"
– Neil Lunn
Nov 22 at 10:58
@NeilLunn it is the official gem "mongo" version 2.3.0
– ciaoben
Nov 22 at 11:01
Yeah was just looking at it and it's pretty bad that this is exposed this way. As stated, you are not actually meant to even try and use it that way, and no other language driver even allows it. Instead you$match
in the pipeline itselfcollection.aggregate([{ "$match" => { dad_id: 9 } },{ "$unwind"=> "$childs" }])
. So the "bugginess" in the driver is thefind()
returns a "Collection View" which exposes anaggregate()
method which should not actually be there. Do it with theCollection
method like everyone else does.
– Neil Lunn
Nov 22 at 11:12
|
show 1 more comment
Which driver is this? You should not even be able to do that. It's certainly not standard with any other language driver and since it is not working, then this "feature" is not even implemented properly. You're supposed to use a$match
stage in the aggregation pipeline. And MongoDB "views" are something completely different.
– Neil Lunn
Nov 22 at 10:54
Yeah about the view your are right, I am calling them poorly. I will edit the question. The driver any way is ruby. My question remain the same but change the word view with "dataset"
– ciaoben
Nov 22 at 10:56
It's not a matter of what you are calling it, but rather that no officially supported driver has any such feature as you are claiming. So what you need to tell us is "where did you install this driver from?"
– Neil Lunn
Nov 22 at 10:58
@NeilLunn it is the official gem "mongo" version 2.3.0
– ciaoben
Nov 22 at 11:01
Yeah was just looking at it and it's pretty bad that this is exposed this way. As stated, you are not actually meant to even try and use it that way, and no other language driver even allows it. Instead you$match
in the pipeline itselfcollection.aggregate([{ "$match" => { dad_id: 9 } },{ "$unwind"=> "$childs" }])
. So the "bugginess" in the driver is thefind()
returns a "Collection View" which exposes anaggregate()
method which should not actually be there. Do it with theCollection
method like everyone else does.
– Neil Lunn
Nov 22 at 11:12
Which driver is this? You should not even be able to do that. It's certainly not standard with any other language driver and since it is not working, then this "feature" is not even implemented properly. You're supposed to use a
$match
stage in the aggregation pipeline. And MongoDB "views" are something completely different.– Neil Lunn
Nov 22 at 10:54
Which driver is this? You should not even be able to do that. It's certainly not standard with any other language driver and since it is not working, then this "feature" is not even implemented properly. You're supposed to use a
$match
stage in the aggregation pipeline. And MongoDB "views" are something completely different.– Neil Lunn
Nov 22 at 10:54
Yeah about the view your are right, I am calling them poorly. I will edit the question. The driver any way is ruby. My question remain the same but change the word view with "dataset"
– ciaoben
Nov 22 at 10:56
Yeah about the view your are right, I am calling them poorly. I will edit the question. The driver any way is ruby. My question remain the same but change the word view with "dataset"
– ciaoben
Nov 22 at 10:56
It's not a matter of what you are calling it, but rather that no officially supported driver has any such feature as you are claiming. So what you need to tell us is "where did you install this driver from?"
– Neil Lunn
Nov 22 at 10:58
It's not a matter of what you are calling it, but rather that no officially supported driver has any such feature as you are claiming. So what you need to tell us is "where did you install this driver from?"
– Neil Lunn
Nov 22 at 10:58
@NeilLunn it is the official gem "mongo" version 2.3.0
– ciaoben
Nov 22 at 11:01
@NeilLunn it is the official gem "mongo" version 2.3.0
– ciaoben
Nov 22 at 11:01
Yeah was just looking at it and it's pretty bad that this is exposed this way. As stated, you are not actually meant to even try and use it that way, and no other language driver even allows it. Instead you
$match
in the pipeline itself collection.aggregate([{ "$match" => { dad_id: 9 } },{ "$unwind"=> "$childs" }])
. So the "bugginess" in the driver is the find()
returns a "Collection View" which exposes an aggregate()
method which should not actually be there. Do it with the Collection
method like everyone else does.– Neil Lunn
Nov 22 at 11:12
Yeah was just looking at it and it's pretty bad that this is exposed this way. As stated, you are not actually meant to even try and use it that way, and no other language driver even allows it. Instead you
$match
in the pipeline itself collection.aggregate([{ "$match" => { dad_id: 9 } },{ "$unwind"=> "$childs" }])
. So the "bugginess" in the driver is the find()
returns a "Collection View" which exposes an aggregate()
method which should not actually be there. Do it with the Collection
method like everyone else does.– Neil Lunn
Nov 22 at 11:12
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
0
down vote
You can not chain input from one query to another query like that.
Either use search query ex. Model.find(id) or aggregation framework.
Aggregation framework provides you the functionality to create a pipeline (ex. match,unwind,lookup,project).
To utilize mongodb indexing always try to use "$match" first in the pipeline
match = { "$match" => { "dad_id" =>9} }
unwind = {"$uwind"=>"$childs"}
pipeline = [match,unwind]
collection.aggregate(pipeline).each do |obj|
end
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You can not chain input from one query to another query like that.
Either use search query ex. Model.find(id) or aggregation framework.
Aggregation framework provides you the functionality to create a pipeline (ex. match,unwind,lookup,project).
To utilize mongodb indexing always try to use "$match" first in the pipeline
match = { "$match" => { "dad_id" =>9} }
unwind = {"$uwind"=>"$childs"}
pipeline = [match,unwind]
collection.aggregate(pipeline).each do |obj|
end
add a comment |
up vote
0
down vote
You can not chain input from one query to another query like that.
Either use search query ex. Model.find(id) or aggregation framework.
Aggregation framework provides you the functionality to create a pipeline (ex. match,unwind,lookup,project).
To utilize mongodb indexing always try to use "$match" first in the pipeline
match = { "$match" => { "dad_id" =>9} }
unwind = {"$uwind"=>"$childs"}
pipeline = [match,unwind]
collection.aggregate(pipeline).each do |obj|
end
add a comment |
up vote
0
down vote
up vote
0
down vote
You can not chain input from one query to another query like that.
Either use search query ex. Model.find(id) or aggregation framework.
Aggregation framework provides you the functionality to create a pipeline (ex. match,unwind,lookup,project).
To utilize mongodb indexing always try to use "$match" first in the pipeline
match = { "$match" => { "dad_id" =>9} }
unwind = {"$uwind"=>"$childs"}
pipeline = [match,unwind]
collection.aggregate(pipeline).each do |obj|
end
You can not chain input from one query to another query like that.
Either use search query ex. Model.find(id) or aggregation framework.
Aggregation framework provides you the functionality to create a pipeline (ex. match,unwind,lookup,project).
To utilize mongodb indexing always try to use "$match" first in the pipeline
match = { "$match" => { "dad_id" =>9} }
unwind = {"$uwind"=>"$childs"}
pipeline = [match,unwind]
collection.aggregate(pipeline).each do |obj|
end
answered Nov 22 at 11:59
Mukul Dev
562
562
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429227%2fwhy-do-aggregating-a-filtered-dataset-lose-the-filters-of-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Which driver is this? You should not even be able to do that. It's certainly not standard with any other language driver and since it is not working, then this "feature" is not even implemented properly. You're supposed to use a
$match
stage in the aggregation pipeline. And MongoDB "views" are something completely different.– Neil Lunn
Nov 22 at 10:54
Yeah about the view your are right, I am calling them poorly. I will edit the question. The driver any way is ruby. My question remain the same but change the word view with "dataset"
– ciaoben
Nov 22 at 10:56
It's not a matter of what you are calling it, but rather that no officially supported driver has any such feature as you are claiming. So what you need to tell us is "where did you install this driver from?"
– Neil Lunn
Nov 22 at 10:58
@NeilLunn it is the official gem "mongo" version 2.3.0
– ciaoben
Nov 22 at 11:01
Yeah was just looking at it and it's pretty bad that this is exposed this way. As stated, you are not actually meant to even try and use it that way, and no other language driver even allows it. Instead you
$match
in the pipeline itselfcollection.aggregate([{ "$match" => { dad_id: 9 } },{ "$unwind"=> "$childs" }])
. So the "bugginess" in the driver is thefind()
returns a "Collection View" which exposes anaggregate()
method which should not actually be there. Do it with theCollection
method like everyone else does.– Neil Lunn
Nov 22 at 11:12