You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Szymon Orzechowski (Jira)" <ji...@apache.org> on 2023/08/09 20:04:00 UTC

[jira] [Commented] (RANGER-4349) AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES

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

Szymon Orzechowski commented on RANGER-4349:
--------------------------------------------

Review board: https://reviews.apache.org/r/74541/

> AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES
> --------------------------------------------------------------
>
>                 Key: RANGER-4349
>                 URL: https://issues.apache.org/jira/browse/RANGER-4349
>             Project: Ranger
>          Issue Type: Bug
>          Components: tagsync
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Szymon Orzechowski
>            Assignee: Szymon Orzechowski
>            Priority: Major
>         Attachments: RANGER-4349.patch
>
>
> AtlasTagSource.commitToKafka() is hard coded to commit offset to topic ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and received by Ranger Tagsync is determined by atlas.notification.entities.topic.name property in atlas-application.properties file. By default, it is ATLAS_ENTITIES but some might configure it to a different name in which case Tagsync would be committing offset to the wrong topic.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)