[ 
https://issues.apache.org/jira/browse/BEAM-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Burke reassigned BEAM-4424:
----------------------------------

    Assignee: Robert Burke

> Improvements to hooks module
> ----------------------------
>
>                 Key: BEAM-4424
>                 URL: https://issues.apache.org/jira/browse/BEAM-4424
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>    Affects Versions: Not applicable
>            Reporter: Bill Neubauer
>            Assignee: Robert Burke
>            Priority: P3
>
> Proposed improvements to the Go hooks API:
> Execution order of the hooks should be based on the order in which the hook 
> is enabled. This gives the runner precise control over ordering so 
> dependencies on hooked behavior can be well-managed.
> Provide an API to disable a hook. Disabling a hook removes it from the 
> ordered list. If the same hook is later re-Enabled, it has lost its previous 
> ordering and would be placed at the end of the ordered list.
> The invocation of setupRemoteLogging() in harness.Main() will be replaced by 
> a hook. This new hook will be called by the default translate code. The net 
> effect is the default behavior for runners remains unchanged. If a runner 
> wants a different logging behavior, it can disable the default logging hook 
> and enable its own hook.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to