Vrushali C commented on YARN-3706:

Hmm, yes, that would be a good thing to do. It would be a one way conversion 
though, which should be fine but we need to be aware of, while generating the 
We don't do that in hraven for metrics and config and I think similarly in the 
YARN-3411 patch, we are not doing that for config and metrics. 

> Generalize native HBase writer for additional tables
> ----------------------------------------------------
>                 Key: YARN-3706
>                 URL: https://issues.apache.org/jira/browse/YARN-3706
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Joep Rottinghuis
>            Assignee: Joep Rottinghuis
>            Priority: Minor
> When reviewing YARN-3411 we noticed that we could change the class hierarchy 
> a little in order to accommodate additional tables easily.
> In order to get ready for benchmark testing we left the original layout in 
> place, as performance would not be impacted by the code hierarchy.
> Here is a separate jira to address the hierarchy.

This message was sent by Atlassian JIRA

Reply via email to