[jira] [Commented] (BEAM-11102) Unable to use KafkaIO with SSL via Python API

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-11102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337855#comment-17337855 ] 

Beam JIRA Bot commented on BEAM-11102:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Unable to use KafkaIO with SSL via Python API
> ---------------------------------------------
>
>                 Key: BEAM-11102
>                 URL: https://issues.apache.org/jira/browse/BEAM-11102
>             Project: Beam
>          Issue Type: Improvement
>          Components: cross-language, io-py-kafka
>            Reporter: Michael Wizner
>            Priority: P2
>              Labels: stale-P2
>
> I've come across the same issue described in BEAM-9627 while trying to use KafkaIO with SSL via the Python API.
> While the solution in the Java API is to use withConsumerFactoryFn or withProducerFactoryFn and provide a custom function to download or generate key/trust stores before the consumer or producer gets created, there is no such functionality exposed via in the Python API since it's just a wrapper around the external transform.
> Is there currently any other way to work around this issue in Python or would it be possible to expose a similar functionality in the API? (I'm using the Dataflow runner, but hopefully it shouldn't matter.)
> As far as my understanding goes, alternatively one could write an external transform that's a thin wrapper around the Java's KafkaIO API that handles key/trust stores under the hood and make it available via an external expansion service, but that's definitely way less ideal than being able to achieve the same thing via the built-in API.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)