[ https://issues.apache.org/jira/browse/ATLAS-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sarath Subramanian updated ATLAS-2996: -------------------------------------- Fix Version/s: 2.0.0 1.2.0 > Message Processing: Conditionally Prevent Message Processing > ------------------------------------------------------------ > > Key: ATLAS-2996 > URL: https://issues.apache.org/jira/browse/ATLAS-2996 > Project: Atlas > Issue Type: Improvement > Components: atlas-core > Affects Versions: trunk > Reporter: Ashutosh Mestry > Assignee: Ashutosh Mestry > Priority: Major > Fix For: 1.2.0, 2.0.0, trunk > > Attachments: > ATLAS-2996-Conditionally-Prevent-Notification-Proces-HA-Mode.patch, > ATLAS-2996-Conditionally-Prevent-Notification-Proces.patch > > > *Background* > There is a need to start Atlas with its message processing ability shut off. > This is necessary when ingesting data via REST calls or using utility like > _import-hive.sh_. > Once message processing ability is shut off, it is possible to be certain > that no changes have been made during the manual import process. > *Approach Guidance* > * Introduce new property say, _atlas.notification.consumer.disabled_ > * Within _NotificationHookConsumer_, check the value of this property and > decide on starting the hook processing thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)