Details
-
Task
-
Resolution: Fixed
-
Major
-
2.2.0-dp2
-
None
-
Security Level: Public
-
None
Description
With named prepared statement support, we need to modify the prepared statement api.
[Current behavior]
Prepared a Statement => prepared statement is returned=> pass prepared statement into cbq for queries.
[New Behavior]
SHA1 hash query to be prepared to get name=> Prepare a statement using hash name from previous step=> prepared statement is returned=> pass in prepared statement name for cbq queries.
[Error Behavior]
On error, in fast fail mode the error will be immediately propagated back.
Best Effort retry will be covered in another jira issue.
[Future Considerations]
Until there is a reliable consistent storage of prepared statements between query nodes it doesn't make sense to try and utilize explicit prepared statement naming from the clients. Once this exists, using the explicit naming from the clients will be implemented.