[
https://issues.apache.org/jira/browse/BEAM-7373?focusedWorklogId=245717&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-245717
]
ASF GitHub Bot logged work on BEAM-7373:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/May/19 03:16
Start Date: 21/May/19 03:16
Worklog Time Spent: 10m
Work Description: aaltay commented on pull request #8632: [BEAM-7373]
Migrating vet runner
URL: https://github.com/apache/beam/pull/8632
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 245717)
Time Spent: 0.5h (was: 20m)
> Migrate Google code for Go SDK "vet runner"
> -------------------------------------------
>
> Key: BEAM-7373
> URL: https://issues.apache.org/jira/browse/BEAM-7373
> Project: Beam
> Issue Type: New Feature
> Components: sdk-go
> Reporter: Daniel Oliveira
> Assignee: Daniel Oliveira
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The "vet runner" is a tool written by [~lostluck] internally for Google that
> is used to evaluate Beam pipelines to check if they are fulfilling the
> requirements needed to perform well. The following are some of the more
> straightforward things that the vet runner checks:
> * If types or functions need to be registered.
> * If shims have been generated for types/functions that need them.
> * Whether all identifiers in the pipeline were exported.
> * Based on the above, whether a pipeline is performant and, if not, what
> needs to be done to make it performant.
> I did not write the original tool but I will be migrating it to the Beam repo
> so that it can be integrated into the universal runner and direct runner,
> probably with a flag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
