4paradigm / 4paradigm/OpenMLDB
Optimize trace info in Status
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
new trace impl from #435
construct trace object at runtime, only when trace setting is open.
try find inspiration from `absl::Status`
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
Look at the trace implementation from issue #435 and the absl::Status library for inspiration. The goal is to construct trace objects only when trace settings are enabled. Start by examining the current Status class and its trace handling, then design a lazy-initialization mechanism. Verify the changes by running existing tests related to Status and trace functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100