-
Notifications
You must be signed in to change notification settings - Fork 230
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
Allow partial results flag to be set #291
base: development
Are you sure you want to change the base?
Conversation
Hi @kahuang, Thanks for your contribution, but can you write some test that checks the functionality you just added? |
Happy to add tests, what kind of tests did you have in mind? As this is just allowing us to set a flag that already existed in code, and I don't see other tests for some of the other flags (or I might just be missing it?) I'm not sure how to proceed |
Hi @kahuang , The test I had in mind was one that proofed that you can actually obtain partial results. |
Hi @kahuang, The testing harness should allow you to setup a test with multiple shards where you can have a query with partial results enabled, so you can make sure the function you've added works as expected. Please do target development branch instead of master. Thanks! |
the presence of downstream mongoD failures
a522af2
to
97e7054
Compare
I've added a separate sharded cluster to the The test then connects to this sharded cluster via a mongos and confirms that it gets the partial results |
Any concerns on this PR? |
Hi @kahuang, Thanks for taking the time to add the tests for this. However the build is failing due to your changes, I believe you've forgotten some setup for your sharded cluster. Could you please have a look at how other testing clusters are done to see what's missing? Thanks, |
bedc976
to
147121f
Compare
Looks like I accidentally force-pushed a commit that didn't include the daemons. I've added those now, we'll see if the tests pass now |
Hi @kahuang, It looks like the build is still failing for mongo versions 3.0 and 3.2, any chance those issues are compatibility related? Thanks, |
Did a bit of looking, it seems that in <=3.2 mongo actually called the flag |
This is useful in the case where n shards are failing to return data, but partial results are acceptable to use