Queries include query_context param against <7.0 server versions
Description
Doing a query with a 6.6 cluster fails and eventually times out, specifically due to including the query_context parameter:
This also affects the WaitUntilReady on the bucket and cluster due to the query checks.
I've included a set of logs that simply does a query with `SELECT 1;`
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Attachments
1
Activity
Show:
Jeffry Morris March 9, 2023 at 5:05 PM
- there are no other changes to be made as i've reviewed the code and determined the behavior is the same since Aug 2020: .
Will Broadbelt March 9, 2023 at 4:32 PM
- The patch fixes the issues I was seeing - still running all the tests. Let me know if you there are further changes you are making as you alluded to in your last comment.
Graham Pople March 9, 2023 at 10:22 AM
So, its just a bug.
Fair enough.
Do we need to send the query_context with regular queries (`scope.query(statment)`)? I added this (query_context) to those Scope level queries, but don't see any mention in CBD-5091's description, which outlines the scope of work to be completed.
Yea, query_context should be sent with scope.query(). It's not included in because that particular piece was completed earlier in .
Jeffry Morris March 9, 2023 at 5:19 AM
- you can test against the patch, but there still maybe be some work today.
Jeffry Morris March 9, 2023 at 4:53 AM
-
Do we need to send the query_context with regular queries (`scope.query(statment)`)? I added this (query_context) to those Scope level queries, but don't see any mention in CBD-5091's description, which outlines the scope of work to be completed.
Unresolved
Pinned fields
Click on the next to a field label to start pinning.
Doing a query with a 6.6 cluster fails and eventually times out, specifically due to including the query_context parameter:
This also affects the WaitUntilReady on the bucket and cluster due to the query checks.
I've included a set of logs that simply does a query with `SELECT 1;`