[
https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498366#comment-14498366
]
Vrushali C commented on YARN-3411:
----------------------------------
Thanks [~djp] !
bq. Just quickly go through the poc patch which is good but only have
EntityTable so far. Do we have plan to split other tables to other JIRAs?
yes, we can have jiras for other tables as we add in those functionalities.
Right now, the PoC is focussed only on entity writes, hence this patch has only
that table related stuff.
bq. Some quick comments on poc patch is we should reuse many operations here
like split() or join() in other classes, so better to create a utility class
with putting common methods to share.
Absolutely agreed, I am refining the patch. With hRaven we have a bunch of such
utility classes. I was trying to see how many I can put in, since it's not
confirmed that this would be the way to go. I did not want to mix up too much
code. But I will be uploading a refined patch + some more changes like Metric
writing soon.
> [Storage implementation] explore the native HBase write schema for storage
> --------------------------------------------------------------------------
>
> Key: YARN-3411
> URL: https://issues.apache.org/jira/browse/YARN-3411
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Vrushali C
> Priority: Critical
> Attachments: ATSv2BackendHBaseSchemaproposal.pdf, YARN-3411.poc.txt
>
>
> There is work that's in progress to implement the storage based on a Phoenix
> schema (YARN-3134).
> In parallel, we would like to explore an implementation based on a native
> HBase schema for the write path. Such a schema does not exclude using
> Phoenix, especially for reads and offline queries.
> Once we have basic implementations of both options, we could evaluate them in
> terms of performance, scalability, usability, etc. and make a call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
