Use a unified factory for storeKey conversion and KeyConvertingTransformer
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
Relates to changes discussed in the context of #970.
Replication needs to use the key converter to process metadata response, and the transformer to actually do the message transformation. These should be in sync with each other, so best to couple them together as part of the same factory.
Contributor guide
No contributing guide indexed for this repository
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 by reading the changes discussed in issue #970 and trace the replication path that processes metadata responses and transforms messages. Identify the existing storeKey converter and KeyConvertingTransformer, then define done as both being provided by one factory and kept in sync for replication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100