[GitHub] [beam] kennknowles opened a new issue, #18150: DoFn per-key lifecycle (Setup/Teardown)

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #18150:
URL: https://github.com/apache/beam/issues/18150

   DoFn's that use state and timers are implicitly per-key. Setup/Teardown methods are usually used to establish expensive resources - long-standing connections and such.
   
   For per-key DoFn's, we'd often want to use these per-key, so it'd be good to have ability in the model to ask that there be 1 instance of the DoFn per key, reused between e.g. different timer or trigger firings for this key, but not used for other keys.
   
   E.g. this would be particularly useful for Splittable DoFn - for its ability to reuse expensive resources between checkpoints.
   
   Imported from Jira [BEAM-1314](https://issues.apache.org/jira/browse/BEAM-1314). Original Jira may contain additional context.
   Reported by: jkff.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org