You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Nixon Rodrigues (JIRA)" <ji...@apache.org> on 2017/07/03 13:20:00 UTC
[jira] [Assigned] (ATLAS-1908) Updating old Kafka consumer api
properties to reflect change in new KafkaConsumer configs for Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nixon Rodrigues reassigned ATLAS-1908:
--------------------------------------
Assignee: Nixon Rodrigues
> 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.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)