Reuse StateNamespace.stringKey in Flink States
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
See BEAM-1587
StateNamespace.stringKey did two things: the base64 encoding of window , and then String.format. These two things consumption is not small. We can cache it in State and reuse.
Further more, we can cache the state.
Imported from Jira [BEAM-1588](https://issues.apache.org/jira/browse/BEAM-1588). Original Jira may contain additional context.
Reported by: lzljs3620320.
Contributor guide
Research direction
Start by tracing StateNamespace.stringKey and the related State implementation to understand where the window is base64-encoded and formatted. Review BEAM-1587 and the original BEAM-1588 Jira issue for missing context, then determine how cached keys and state reuse should preserve existing behavior and reduce repeated work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100