[
https://issues.apache.org/jira/browse/BEAM-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854417#comment-16854417
]
Lukasz Gajowy commented on BEAM-4776:
-------------------------------------
I know that the ReferenceRunner's code [was
removed|https://github.com/apache/beam/pull/8380/files] but the PortableRunner
is still there in Java SDK, although in "reference" directory. To my current
understanding, only the ReferenceRunner was to be removed and there are no
plans (yet?) to remove the PortableRunner in Java sdk. The PortableRunner in
Java sdk still allows you to run portable Java jobs on different execution
engines (reference was only a "direct" runner). I was successfuly able to use
that runner to run portable jobs on Flink.
If my understanding is correct, should we move/rename the PortableRunner's
directory from "reference" to something less confusing?
Or this code (the Java's
[PortableRunner|https://github.com/apache/beam/blob/b953645ed6db837d24284d7fe1fe091e7309f821/runners/reference/java/src/main/java/org/apache/beam/runners/reference/PortableRunner.java])
should also be deleted and we should use Python's PortableRunner to run Java
jobs?
> Java PortableRunner should support metrics
> ------------------------------------------
>
> Key: BEAM-4776
> URL: https://issues.apache.org/jira/browse/BEAM-4776
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Eugene Kirpichov
> Assignee: Lukasz Gajowy
> Priority: Major
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> BEAM-4775 concerns adding metrics to the JobService API; the current issue is
> about making PortableRunner understand them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
