[jira] [Updated] (ATLAS-2192) Split-Join Notification Messages Could Use Additional Logging

["Madhan Neethiraj (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ATLAS-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Madhan Neethiraj updated ATLAS-2192:
------------------------------------
    Affects Version/s:     (was: trunk)
        Fix Version/s: 0.8.3
                       1.0.0

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/35616050
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/6a18b5c6

> Split-Join Notification Messages Could Use Additional Logging
> -------------------------------------------------------------
>
>                 Key: ATLAS-2192
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2192
>             Project: Atlas
>          Issue Type: Improvement
>          Components: atlas-intg
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>            Priority: Minor
>             Fix For: 1.0.0, 0.8.3
>
>         Attachments: ATLAS-2192-2.patch, ATLAS-2192-Split-join-logging.patch
>
>
> *Background*
> The recent implementation of split-join messages allow for handling of notification messages posted on Kafka to be greater than the message threshold.
> The implementation could be improved with additional handling of error conditions and incidental logging.
> *Implementation*
> Items below could be used as implementation guidelines:
> - New class that encapsulates split buffer.
> - Rudimentary eviction logic within the _AtlasNotificationMessageDeserializer_ to maintain healthy state of _splitMsgBuffer_. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)