[
https://issues.apache.org/jira/browse/ATLAS-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049365#comment-17049365
]
ASF subversion and git services commented on ATLAS-3643:
--------------------------------------------------------
Commit ed2755dcce37318ffce21e5ecd7692416aa49a1d in atlas's branch
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ed2755d ]
ATLAS-3643: PC Fx: StatusReporter: Introduce Status Reporting to Be used With
PC Framework
> PC Framework: StatusReporter: Introduce Status Reporting to Be used With PC
> Framework
> --------------------------------------------------------------------------------------
>
> Key: ATLAS-3643
> URL: https://issues.apache.org/jira/browse/ATLAS-3643
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
> Attachments:
> ATLAS-3643-PC-Framework-Support-for-status-reporting.patch
>
>
> *Background*
> The Producer-Consumer (PC) framework helps in processing large amount of data.
> An utility class that helps correctly report the status of currently
> processed items will be helpful.
> *Solution*
> This class should be used in conjunction with the
> _WorkItemManager.getResults_. The users of the _StatusReporter_ should add
> their processed items to it.
> Once the results arrive, the _StatusReporter_ will compare them against the
> received results.
> The _StatusReporter_ should also account for timeout cases, where it should
> not wait too long for the processed items, that will cause reporting to be
> 'stuck'. The timeout case should be appropriately indicated.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
