[
https://issues.apache.org/jira/browse/BEAM-7029?focusedWorklogId=224897&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-224897
]
ASF GitHub Bot logged work on BEAM-7029:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Apr/19 10:27
Start Date: 09/Apr/19 10:27
Worklog Time Spent: 10m
Work Description: mxm commented on issue #8251: [BEAM-7029] Add
KafkaIO.Read as external transform
URL: https://github.com/apache/beam/pull/8251#issuecomment-481195343
Thanks for taking a look @lukecwik. The design document for this is
https://s.apache.org/beam-cross-language-io. Approach (2) in the design doc was
the original proposal for configuring cross-language transforms. It is very
close to what you are suggesting. The PR #7875 originally had this design, but
we changed it to match approach (1) after a discussion in the PR, on the
mailing list, and in a meeting which @chamikaramj summarized on the mailing
list.
It is not necessarily a contradiction to support both, an explicit Proto for
each transform, and a generic approach. However, the main objective for
cross-language transforms was that there should not be the need for users to
write Proto. So the generic approach was deemed more important.
>Also, how do you "choose" what the output type of the PCollection produced
by Kafka.Read is?
If someone passes in the
org.apache.kafka.common.serialization.LongDeserializer like in your example,
the returned PCollection may contain some Java SDK specific coder. Would it
make sense to have a mapping from beam coder URNs to kafka deserializers
instead?
Good point. I think it makes sense to define a mapping of supported coders
for Kafka deserializers, since we can only support standard SDK coders.
----------------------------------------------------------------
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: 224897)
Time Spent: 1h 20m (was: 1h 10m)
> 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: 1h 20m
> 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)
