[
https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643734#comment-14643734
]
Vrushali C commented on YARN-3904:
----------------------------------
bq. One thing pending discussion is about the aggregation method. I feel this
method is a little bit outdated. Could anyone remind me the assumed use case
for it? Will it fit for real-time aggregations only?
IIRC I think we had added it so that we could invoke/trigger aggregation
explicitly from the collector/caller in addition to the background aggregation
processing. This was provided so that aggregation is not just a
behind-the-scenes processing effort but can be triggered on demand. I am
thinking this would apply only to app-to-flow aggregation not the offline ones.
But yes, it is probably outdated and we should update it as we see fit.
> Refactor timelineservice.storage to add support to online and offline
> aggregation writers
> -----------------------------------------------------------------------------------------
>
> Key: YARN-3904
> URL: https://issues.apache.org/jira/browse/YARN-3904
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Li Lu
> Assignee: Li Lu
> Attachments: YARN-3904-YARN-2928.001.patch,
> YARN-3904-YARN-2928.002.patch, YARN-3904-YARN-2928.003.patch,
> YARN-3904-YARN-2928.004.patch
>
>
> After we finished the design for time-based aggregation, we can adopt our
> existing Phoenix storage into the storage of the aggregated data. In this
> JIRA, I'm proposing to refactor writers to add support to aggregation
> writers. Offline aggregation writers typically has less contextual
> information. We can distinguish these writers by special naming. We can also
> use CollectorContexts to model all contextual information and use it in our
> writer interfaces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
