You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The query definition holds the memory stream passed in by the user. That stream is then read and disposed of to send the query over the wire. The issue is the query plan will be serialized multiple times for cross partition queries and for scenarios where the query plan can not be generated locally. Reserializing the query plan seems to be by design because the query plan can rewrite the query.
This API was specifically added for Encryption SDK, and will most likely be the biggest impact.
Solution:
Convert the stream to a byte[]. Then the byte array can be used to create new memory streams where necessary. This way the parameter values are always buffered can be serialized multiple times.
The text was updated successfully, but these errors were encountered:
The query definition holds the memory stream passed in by the user. That stream is then read and disposed of to send the query over the wire. The issue is the query plan will be serialized multiple times for cross partition queries and for scenarios where the query plan can not be generated locally. Reserializing the query plan seems to be by design because the query plan can rewrite the query.
This API was specifically added for Encryption SDK, and will most likely be the biggest impact.
Solution:
Convert the stream to a byte[]. Then the byte array can be used to create new memory streams where necessary. This way the parameter values are always buffered can be serialized multiple times.
The text was updated successfully, but these errors were encountered: