Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Task]: [flink] reuse StateNamespace#stringKey in state access #33145

Closed
1 of 17 tasks
je-ik opened this issue Nov 18, 2024 · 0 comments · Fixed by #33146
Closed
1 of 17 tasks

[Task]: [flink] reuse StateNamespace#stringKey in state access #33145

je-ik opened this issue Nov 18, 2024 · 0 comments · Fixed by #33146
Assignees

Comments

@je-ik
Copy link
Contributor

je-ik commented Nov 18, 2024

What needs to happen?

StateNamespace#stringKey can be expensive due to serialization of the namespace. This should be cached in FlinkStateInternals.

Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@je-ik je-ik self-assigned this Nov 18, 2024
je-ik added a commit to je-ik/beam that referenced this issue Nov 18, 2024
je-ik added a commit to je-ik/beam that referenced this issue Nov 18, 2024
je-ik added a commit to je-ik/beam that referenced this issue Nov 18, 2024
je-ik pushed a commit to je-ik/beam that referenced this issue Nov 20, 2024
je-ik added a commit that referenced this issue Nov 20, 2024
@github-actions github-actions bot added this to the 2.62.0 Release milestone Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant