You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The folks at ResearchGate are having an issue with find commands encountering errors from mongos due to the adapter defaulting the batchSize option to 0. Relevant code is:
Is there a particular reason that Alcaeus\MongoDbAdapter\AbstractCursor::$batchSize defaults to zero? Would leaving the property uninitialized (i.e. null) break compatibility for ODM or other dependent libraries?
The text was updated successfully, but these errors were encountered:
The folks at ResearchGate are having an issue with find commands encountering errors from mongos due to the adapter defaulting the
batchSize
option to0
. Relevant code is:Alcaeus\MongoDbAdapter\AbstractCursor::$batchSize
defaults to zero.Alcaeus\MongoDbAdapter\AbstractCursor::getOptions()
returns that property because it is non-null.MongoCursor::doQuery()
includes all cursor options when invokingMongoDB\Collection::find()
.See this comment in SERVER-28019 for more information.
Is there a particular reason that
Alcaeus\MongoDbAdapter\AbstractCursor::$batchSize
defaults to zero? Would leaving the property uninitialized (i.e.null
) break compatibility for ODM or other dependent libraries?The text was updated successfully, but these errors were encountered: