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

Robomongo closes cursor when reaching batch size (by default 101) #1139

Closed
cristian-vertiz-tierconnect-com opened this Issue Jul 22, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@cristian-vertiz-tierconnect-com

Robomongo closes cursor when reaching batch size (by default 101)

by example:
var a = db.myCollection1.find({"field": "value"}).forEach(function(x){
print(x.serialNumber)
});
var b = db.myCollection2.find({"field": "value"}).forEach(function(x){
print(x.serialNumber)
});

prints 101 docs for each query

NOTE: It works as expected in RC7 but not in RC9 (not tested in RC8)

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Jul 22, 2016

Collaborator

@cristian-vertiz-tierconnect-com thank you for reporting! Let us try to reproduce the issue and we will get you back on any updates.

Collaborator

juliashibalko commented Jul 22, 2016

@cristian-vertiz-tierconnect-com thank you for reporting! Let us try to reproduce the issue and we will get you back on any updates.

@juliashibalko juliashibalko self-assigned this Jul 22, 2016

@giannicic

This comment has been minimized.

Show comment
Hide comment
@giannicic

giannicic Jul 26, 2016

Just experienced the same issue now.
It's related to the shellTimeoutSec #1106 (comment)

giannicic commented Jul 26, 2016

Just experienced the same issue now.
It's related to the shellTimeoutSec #1106 (comment)

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Aug 23, 2016

Collaborator

@cristian-vertiz-tierconnect-com I can confirm that workaround from #1106 (comment) will solve the problem. So let me suggest to track issue progress with #1106 (comment). I will close this one but please feel free to reopen or create new ticket.
Hope workaround will help you, thanks!

Collaborator

juliashibalko commented Aug 23, 2016

@cristian-vertiz-tierconnect-com I can confirm that workaround from #1106 (comment) will solve the problem. So let me suggest to track issue progress with #1106 (comment). I will close this one but please feel free to reopen or create new ticket.
Hope workaround will help you, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment