Details
-
Improvement
-
Resolution: Fixed
-
Major
-
5.5.0
Description
We are shifting plan distribution responsibility from the SDKs to the query nodes.
As such we don't need to support the encoded_plan rest api parameter, nor prepareds supplied as query plan, rather than name.
Support for both will be retired in mad-hatter.
Object prepareds will generate an error (4050)
encoded_plans will be initially silently ignored for backwards compatibility with older SDKs.
Attachments
Issue Links
- relates to
-
MB-26290 [N1QL] Incorrect encoded plan gives incorrect error message.
- Closed