libserdes not registering schema to schema registry when the schema is used for multiple topics
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- distributed-systems, stream-processing
Research direction
Reproduce the report by using the same schema as the key for topicA and topicB with Schema Registry configured. Start by examining the local cache behavior keyed by the schema MD5; done means the topicB-key subject is registered even when the schema was already cached from topicA.
Written by the indexing model from the issue text.
Description
Looking to use the same schema as key for 2 Kafka topics, topicA and topicB. I'm using libserdes C++ client library to produce the records with Schema Registry setup.
When I produce for topicA for the first time, I observe that 2 new subjects are registered on Schema Registry as being topicA-key and topicB-value.
Using the same schema as key, after publishing an event onto topicB, topicB-key subject is nowhere to be found on Schema Registry, only topicB-value subject.
After some debug log printing, I see that libserdes checks in its local cache on the MD5 of a schema. If it is found in local cache, it will return the schema immediately and not register it with Schema Registry.
- Dominant language
- C
- Stars
- 12
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from confluentinc/libserdes
-
Difficulty 3/5 Half a day Newbie friendliness 22/100
confluentinc/libserdes#68 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
confluentinc/libserdes#66 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
confluentinc/libserdes#64 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
confluentinc/libserdes#63 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
confluentinc/libserdes#59 · 2 comments ·
All issues in confluentinc/libserdes
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
arduino/ArduinoCore-mbed#1126 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
security
Difficulty 1/5 Under an hour Newbie friendliness 93/100
btclib-org/btclib-secp256k1#1427 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esmuellert/codediff.nvim#594 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 67/100