-
Notifications
You must be signed in to change notification settings - Fork 14
If streaming, don't compute result set size #370
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
base: master
Are you sure you want to change the base?
Conversation
@@ -85,7 +85,7 @@ public long find(CRUDOperationContext ctx, | |||
cursor.setReadPreference(readPreference); | |||
} | |||
|
|||
if (maxQueryTimeMS > 0) { | |||
if (maxQueryTimeMS > 0&&ctx.isLimitQueryTime()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this new isLimitQueryTime flag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added that thinking with streaming, there is no need, but that will still be useful if you submit a long running query, so it is there just in case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still don't know why maxQueryTimeMS is not enough in streaming context.
|
||
int numMatched=0; | ||
int nRetrieve=0; | ||
if(ctx.isComputeMatchCount()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we can rename this flag to computeCounts and use it for modifiedCount too? lightblue-platform/lightblue-core#789
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'll rename
It is enough. What I wanted to do is to not limit query times for
streaming, but then I have second thoughts about it. So, we're still
limiting long running queries, but we may consider disabling that for
streaming finds.
…On Thu, Jun 22, 2017 at 10:04 AM, Marek ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In mongo/src/main/java/com/redhat/lightblue/mongo/crud/BasicDocFinder.java
<#370 (comment)>
:
> @@ -85,7 +85,7 @@ public long find(CRUDOperationContext ctx,
cursor.setReadPreference(readPreference);
}
- if (maxQueryTimeMS > 0) {
+ if (maxQueryTimeMS > 0&&ctx.isLimitQueryTime()) {
Still don't know why maxQueryTimeMS is not enough in streaming context.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#370 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADgDDd-r8FGFQLIafS2VdWuXYZjOWY6Aks5sGpCrgaJpZM4OCVo5>
.
|
No description provided.