You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (Jira)" <ji...@apache.org> on 2021/03/30 10:15:00 UTC
[jira] [Updated] (FLINK-18340) Support directly providing bytes
instead of a Protobuf messages when writing to Kafka / Kinesis with the
Python SDK
[ https://issues.apache.org/jira/browse/FLINK-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tzu-Li (Gordon) Tai updated FLINK-18340:
----------------------------------------
Fix Version/s: (was: statefun-3.0.0)
statefun-3.1.0
> Support directly providing bytes instead of a Protobuf messages when writing to Kafka / Kinesis with the Python SDK
> -------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-18340
> URL: https://issues.apache.org/jira/browse/FLINK-18340
> Project: Flink
> Issue Type: New Feature
> Components: Stateful Functions
> Environment: State
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Major
> Fix For: statefun-3.1.0
>
>
> This was insight from this ML thread: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Any-python-example-with-json-data-from-Kafka-using-flink-statefun-td42520.html
> Currently, the {{kafka_egress_record}} and {{kinesis_egress_record}} methods in the Python SDK only support providing a Protobuf message to be written to Kafka / Kinesis.
> We should make this more flexible so that a user can directly supply bytes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)