[ 
https://issues.apache.org/jira/browse/BEAM-4424?focusedWorklogId=664389&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-664389
 ]

ASF GitHub Bot logged work on BEAM-4424:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Oct/21 23:14
            Start Date: 12/Oct/21 23:14
    Worklog Time Spent: 10m 
      Work Description: lostluck commented on pull request #15713:
URL: https://github.com/apache/beam/pull/15713#issuecomment-941732695


   R: @riteshghorse @youngoli 
   cc: @jrmccluskey 


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 664389)
    Time Spent: 20m  (was: 10m)

> 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
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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