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]: Support Stateful Processing in Spark Runner (Without Timer Functionality) #33237

Closed
2 of 17 tasks
twosom opened this issue Nov 27, 2024 · 1 comment · Fixed by #33267
Closed
2 of 17 tasks

Comments

@twosom
Copy link
Contributor

twosom commented Nov 27, 2024

What would you like to happen?

I would like to add support for stateful processing in the Spark Runner, specifically:

  1. Implement state management functionality for streaming pipelines
  2. Add validation to reject pipelines that use timers (as timer support will be implemented later)
  3. Include proper error messaging when timer functionality is attempted

This implementation will follow the same approach that was successful with the Dataflow runner - implementing state management first, with timer support to follow in a future update.

mail context

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: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@twosom twosom changed the title [Feature Request]: A [Feature Request]: Support Stateful Processing in Spark Runner (Without Timer Functionality) Nov 27, 2024
@twosom
Copy link
Contributor Author

twosom commented Nov 27, 2024

.take-issue

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