[ 
https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532992#comment-14532992
 ] 

Junping Du commented on YARN-3411:
----------------------------------

Thanks [~vrushalic] for updating the patch. I will review and comment based on 
your updated patch in plan.
bq. Sure, I can change it to java but I think, as such there should not be any 
problem running ruby code with hbase, it does not add to dependencies. In fact, 
the HBase Shell, which is a command line interpreter for HBase is written in 
Ruby.
I see. Thanks for sharing this prospective. However, accepting code with a new 
language into hadoop community is not only mvn dependency issue but also a 
maintenance headache according to issues like: setting up new code convention 
for new language, etc. which could take more time to reach into a consensus. 
Given there is only very limited Ruby code in current patch, shouldn't be very 
painful to replace it with Java. Isn't it? 

> [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
>              Labels: BB2015-05-TBR
>         Attachments: ATSv2BackendHBaseSchemaproposal.pdf, 
> YARN-3411.poc.2.txt, YARN-3411.poc.3.txt, YARN-3411.poc.4.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
(v6.3.4#6332)

Reply via email to