Make sampled transaction info to use flat buffers
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
Sampled transaction info is stored in native serialization format. But this data is read from other languages (Java, Python) and also need to support backwards compatibility. hence it is tedious to maintain this whenever there is a schema change. Since flat buffer support has been added, it would be a better idea to represent the transaction info data using flat buffers. This will ease the maintenance of this feature to support backwards compatibility and cross platform serialization/deserialization.
Contributor guide
Research direction
Start by locating the sampled transaction info serialization and the existing flat buffer support in the FoundationDB codebase. Verify how Java and Python consume this data and define compatibility coverage; done means cross-language serialization and deserialization remain backward compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100