ydb-platform / ydb-platform/ydb-python-sdk
feature: send already encoded message
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 75
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Feature Request
Describe the Feature Request
Now the SDK always compress messages internally. It is bad when we have already encoded messages or want compress messages outside of SDK.
Describe Preferred Solution
Add parameter encoded for write method. As value of parameter will codec of message. The SDK will check about possible of use the codec (by topic settings) and save message in internal buffer as is, without internal encoding.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the SDK's write method and trace how topic settings determine the codec and how messages enter the internal buffer. The feature is complete when callers can provide an encoded value, the SDK validates codec compatibility with the topic settings, and compatible messages are stored without internal encoding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100