Hi! I am using Python SDK 4.3.0, I need to use transcation for my operations, but I am not sure how should I specify expiry and transcoder parameters for insert and replace operations. I need to store RawBinary documents and RawString documents. Without providing transcoder, how will CB tell if I am trying to store a json string or raw string? Non-transcational KV operations explicitly support options parameter, that allows to setup these values.
Hi @khan
We only very recently added support for binary documents in transactions, and it is currently only available in the C++ SDK. Currently only JSON documents are supported in transactions in the Python SDK - though you could use an approach like base64 encoding to store binary data inside that JSON of course.
I will notify the SDK PM that there is interest in this feature - thank you for reaching out.
1 Like
yeah unfortunately I can’t wait that long, we have a pretty urgent task for this 
can’t redesign to store as JSON with binary field either as this is a legacy system, a lot of clients depend on the format of stored data. if this feature is to be implemented, do you know how soon will it arrive? by the way, we are also interested in adding this feature to Java API as well if not yet
Hi @khan unfortunately I can’t speak to the roadmap, but I have raised this thread internally with our PM team. If you are an enterprise customer I’d encourage you to reach out to your representative there to discuss roadmap and escalation options.
Noted on the Java API request.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.