[ 
https://issues.apache.org/jira/browse/BEAM-7310?focusedWorklogId=382040&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382040
 ]

ASF GitHub Bot logged work on BEAM-7310:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 05/Feb/20 02:38
            Start Date: 05/Feb/20 02:38
    Worklog Time Spent: 10m 
      Work Description: udim commented on issue #10563: [BEAM-7310] Add support 
of Confluent Schema Registry for KafkaIO
URL: https://github.com/apache/beam/pull/10563#issuecomment-582213871
 
 
   Opened https://issues.apache.org/jira/browse/BEAM-9251 for breakage of 
updateOfflineRepository
 
----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 382040)
    Time Spent: 13h 10m  (was: 13h)

> Confluent Schema Registry support in KafkaIO
> --------------------------------------------
>
>                 Key: BEAM-7310
>                 URL: https://issues.apache.org/jira/browse/BEAM-7310
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-kafka
>    Affects Versions: 2.12.0
>            Reporter: Yohei Shimomae
>            Assignee: Alexey Romanenko
>            Priority: Minor
>             Fix For: 2.20.0
>
>          Time Spent: 13h 10m
>  Remaining Estimate: 0h
>
> Confluent Schema Registry is useful when we manage Avro Schema but  KafkaIO 
> does not support Confluent Schema Registry as discussed here.
> https://stackoverflow.com/questions/56035121/unable-to-connect-from-dataflow-job-to-schema-registry-when-schema-registry-requ
> https://lists.apache.org/thread.html/7695fccddebd08733b80ae1e43b79b636b63cd5fe583a2bdeecda6c4@%3Cuser.beam.apache.org%3E



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

Reply via email to