[
https://issues.apache.org/jira/browse/BEAM-7029?focusedWorklogId=225055&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-225055
]
ASF GitHub Bot logged work on BEAM-7029:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Apr/19 15:37
Start Date: 09/Apr/19 15:37
Worklog Time Spent: 10m
Work Description: chamikaramj commented on issue #8251: [BEAM-7029] Add
KafkaIO.Read as external transform
URL: https://github.com/apache/beam/pull/8251#issuecomment-481304996
@lukecwik I summarized the current design (adapter from Max's original
design doc) in an email to dev list:
https://lists.apache.org/thread.html/b99ba8527422e31ec7bb7ad9dc3a6583551ea392ebdc5527b5fb4a67@%3Cdev.beam.apache.org%3E
The idea is to minimize the amount of work a transform author has to do to
make a given transform available to remote SDKs. With the current solution, the
transform authors simply have to provide a builder that can be used to build
the transform from a given config object (POJO). Framework will generate a
proto from this that defines the wire format. Remote SDKs can invoke arbitrary
transforms that are exposed through the expansion API (and has a builder
available) by using generic ExternalTransform. Also, transform authors may
define nicer wrappers (of ExternalTransform) if they choose to do so.
Of course this means that a cross-SDK interaction can only be done thorough
standard coders that are defined for both languages. These will be used for (1)
encoding parameters used to build the rewmote transform (2) encoding data
transferred between SDKs at runtime. A pipeline author has to be aware of this
and has to make sure that transforms at SDK boundaries use standard coders. We
hope the solution will become more generic once Beam SQL becomes available
(where we should be able to do a Row to Row conversion from SDK A to SDK B for
generic types).
----------------------------------------------------------------
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: 225055)
Time Spent: 3.5h (was: 3h 20m)
> Support KafkaIO to be configured externally for use with other SDKs
> -------------------------------------------------------------------
>
> Key: BEAM-7029
> URL: https://issues.apache.org/jira/browse/BEAM-7029
> Project: Beam
> Issue Type: New Feature
> Components: io-java-kafka, runner-flink, sdk-py-core
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> As of BEAM-6730, we can externally configure existing transforms from SDKs.
> We should add more useful transforms then just {{GenerateSequence}}.
> {{KafkaIO}} is a good candidate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
