hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers
Date Fri, 24 Jul 2015 21:25:04 GMT

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

Li Lu updated YARN-3904:
------------------------
    Description: 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.
  (was: After we finished the design for time-based aggregation, we can adopt our existing
Phoenix storage into the storage of the aggregated data. This JIRA proposes to move the Phoenix
storage implementation from o.a.h.yarn.server.timelineservice.storage to o.a.h.yarn.server.timelineservice.aggregation.timebased,
and make it a fully devoted writer for time-based aggregation. )

> 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
>
>
> 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)

Mime
View raw message