Skip to content

[Feature Request]: Propagate drain mode up to reduceFn #36884

Closed

Description

@stankiewicz

What would you like to happen?

Continuation of #36534

Information about the fact that aggregation or timer was induced by drain event is stored in windmill internal data strutures.
Propagate it to TimerData and up to ReduceFn

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

Activity

  1. stankiewicz commented on Nov 24, 2025

    @stankiewicz
    ContributorAuthor

    .take_issue

  2. github-actions commented on Apr 24, 2026

    @github-actions
    Contributor

    This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

  3. self-assigned this
    on Apr 24, 2026
  4. added this to the 2.74.0 Release milestone on May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions