You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Li Lu (JIRA)" <ji...@apache.org> on 2015/07/10 20:45:04 UTC
[jira] [Updated] (YARN-3904) Adopt PhoenixTimelineWriter into
time-based aggregation storage
[ https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Li Lu updated YARN-3904:
------------------------
Attachment: YARN-3904-YARN-2928.001.patch
I moved the Phoenix writer to the time based aggregation package, and rebuilt it so that it can accommodate flow and user types of offline aggregations.
> Adopt PhoenixTimelineWriter into time-based aggregation storage
> ---------------------------------------------------------------
>
> 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
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)