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

Sidharth Kumar Mishra edited comment on ATLAS-4246 at 10/29/21, 10:38 PM:
--------------------------------------------------------------------------

[~aileeen] We have fixed our CI build. Started the PreCommit job - 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/942/

Once it will pass I will commit your patch.

cc: [~amestry], [~sarath]


was (Author: sidharthkmishra):
[~aileeen] We have fixed our CI build. Started the PreCommit job - 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/935/

Once it will pass I will commit your patch.

cc: [~amestry], [~sarath]

> Make Kafka Interface aware of Kafka Schema Registry
> ---------------------------------------------------
>
>                 Key: ATLAS-4246
>                 URL: https://issues.apache.org/jira/browse/ATLAS-4246
>             Project: Atlas
>          Issue Type: Improvement
>          Components: kafka-integration
>    Affects Versions: 2.1.0, 3.0.0
>            Reporter: Aileen Toleikis
>            Assignee: Viktor Somogyi-Vass
>            Priority: Major
>              Labels: Kafka
>             Fix For: 3.0.0, 2.3.0
>
>
> Kafka Community is using Schema Registry more and more heavily but as Atlas 
> is currently unaware of this, this extension helps Atlas make use of the 
> Schemas.
>  
> We have tested this extension and we have production environments where Atlas 
> will not be allowed without schema registry access. We have received feedback 
> that this extension would be sufficient to allow production use.



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

Reply via email to