[
https://issues.apache.org/jira/browse/BEAM-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Burke updated BEAM-4017:
-------------------------------
Resolution: Won't Do
Status: Resolved (was: Open)
The Session Runner, while neat, isn't worth as much as improving the Direct
Runner, so this is unfortunately going into the won't do bucket.
> Go session runner should write multiple files
> ---------------------------------------------
>
> Key: BEAM-4017
> URL: https://issues.apache.org/jira/browse/BEAM-4017
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Reporter: Bill Neubauer
> Priority: P3
>
> The Go session runner allows a worker to "play back" a previous execution,
> which can be useful for debugging or profiling sessions. However, the
> recording facility produces one file for the entire lifetime of the worker.
> While this is useful for local debugging, it won't work well for workers at
> scale.
> Having the session capture facility make the output chunkable will help
> larger systems scale. I suggest that the interface for session writing be
> expanded from a io.WriteCloser to include a sequence number that systems can
> use to produce an ordered set of files for playback.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
