Junping Du commented on YARN-3411:

bq.  Regarding the public/private annotations, I often got beat it to the head 
that in principle the private annotation is opt-in; i.e. if there is no 
visibility annotation it's implicitly assumed to be up for use. I've gotten 
review comments that said we should mark them explicitly as private even if 
they are clearly YARN-internal classes. That's just my experience on this.
In my understanding, it depends on if this class is within api package that 
under hadoop-yarn-api or hadoop-yarn-common modules. If so, we may need to 
explicitly mark it as Private if we don't like to share it outside of hadoop 
projects. For other classes (like case here for TimelineWriterUtils which is in 
server side), we don't have to mark any annotation. [~vinodkv], can you confirm 

> [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-YARN-2928.001.patch, YARN-3411-YARN-2928.002.patch, 
> YARN-3411-YARN-2928.003.patch, YARN-3411-YARN-2928.004.patch, 
> YARN-3411-YARN-2928.005.patch, YARN-3411-YARN-2928.006.patch, 
> YARN-3411.poc.2.txt, YARN-3411.poc.3.txt, YARN-3411.poc.4.txt, 
> YARN-3411.poc.5.txt, YARN-3411.poc.6.txt, YARN-3411.poc.7.txt, 
> 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

Reply via email to