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

[Feature Request]: Optimize [multi]map side inputs. #29691

Closed
16 tasks
robertwb opened this issue Dec 8, 2023 · 2 comments
Closed
16 tasks

[Feature Request]: Optimize [multi]map side inputs. #29691

robertwb opened this issue Dec 8, 2023 · 2 comments

Comments

@robertwb
Copy link
Contributor

robertwb commented Dec 8, 2023

What would you like to happen?

Currently the only way to read a map is key-by-key lookup. While this works great for too-large-to-fit-into-memory maps, for smaller maps (which are commonly used) this is very inefficient.

Issue Priority

Priority: 2 (default / most feature requests 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: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@jrmccluskey
Copy link
Contributor

@robertwb is work completed on this task?

@robertwb
Copy link
Contributor Author

The attached PRs should resolve the issue for the SDK and local runners.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants