atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nixon Rodrigues (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.
Date Sat, 15 Jul 2017 19:18:00 GMT

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

Nixon Rodrigues commented on ATLAS-1908:
----------------------------------------

Added NotificationConsumer with new interface to avoid Ranger compile time issue.
Please review [^ATLAS-1908.2.patch]

> Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs
for Atlas.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-1908
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1908
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Nixon Rodrigues
>            Assignee: Nixon Rodrigues
>         Attachments: ATLAS-1908-1.patch, ATLAS-1908.2.patch, ATLAS-1908.patch
>
>
> In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer api.
> Due to this update, there were changes in configs.
>  
> New property:
> atlas.kafka.session.timeout.ms=30000
>  
> Renamed property:
> atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false
>  
> New default value:
> atlas.kafka.auto.offset.reset=smallest to atlas.kafka.auto.offset.reset=earliest
> Need to handle old configs, so that Kafka consumer starts gracefully even if new configs
are not added explicitly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message