[jira] [Commented] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests
[
https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508304#comment-14508304
]
Siddharth Wagle commented on YARN-3529:
---
Enlisted deps here :
{code}
org.apache.phoenix
phoenix-core
${phoenix.version}
org.apache.hadoop
hadoop-common
org.apache.hadoop
hadoop-annotations
org.apache.phoenix
phoenix-core
test-jar
${phoenix.version}
test
org.apache.hbase
hbase-it
${hbase.version}
test
tests
org.apache.hbase
hbase-testing-util
${hbase.version}
test
true
org.jruby
jruby-complete
{code}
> Add miniHBase cluster and Phoenix support to ATS v2 unit tests
> --
>
> Key: YARN-3529
> URL: https://issues.apache.org/jira/browse/YARN-3529
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
>Reporter: Li Lu
>Assignee: Li Lu
> Attachments: AbstractMiniHBaseClusterTest.java,
> output_minicluster2.txt
>
>
> After we have our HBase and Phoenix writer implementations, we may want to
> find a way to set up HBase and Phoenix in our unit tests. We need to do this
> integration before the branch got merged back to trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests
[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507801#comment-14507801 ] Siddharth Wagle commented on YARN-3529: --- Note: This will start in memory HBase cluster and provide a Phoenix connection to use for tests. > Add miniHBase cluster and Phoenix support to ATS v2 unit tests > -- > > Key: YARN-3529 > URL: https://issues.apache.org/jira/browse/YARN-3529 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Reporter: Li Lu >Assignee: Li Lu > Attachments: AbstractMiniHBaseClusterTest.java, > output_minicluster2.txt > > > After we have our HBase and Phoenix writer implementations, we may want to > find a way to set up HBase and Phoenix in our unit tests. We need to do this > integration before the branch got merged back to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests
[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated YARN-3529: -- Attachment: AbstractMiniHBaseClusterTest.java Attaching a Abstract base class from Ambari Metrics System, this directly extends the Phoenix test classes from the Phoenix compile time dep. All subclasses of this class use the Accessor functions to get to the Phoenix tables. > Add miniHBase cluster and Phoenix support to ATS v2 unit tests > -- > > Key: YARN-3529 > URL: https://issues.apache.org/jira/browse/YARN-3529 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Reporter: Li Lu >Assignee: Li Lu > Attachments: AbstractMiniHBaseClusterTest.java, > output_minicluster2.txt > > > After we have our HBase and Phoenix writer implementations, we may want to > find a way to set up HBase and Phoenix in our unit tests. We need to do this > integration before the branch got merged back to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend
[
https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349302#comment-14349302
]
Siddharth Wagle commented on YARN-3134:
---
Thanks [~vrushalic]
*Questions*:
- Do the responses to these API calls return any timeseries data?:
_GetFlowByAppId_ and _GetAppDetails_
- The set of access patterns do not cover query directly by a metricName. Is
there a use case for this? (Note: General use case for driving graphs)
- Do you use the hbase native timestamp for querying? This is an obvious
optimization for timeseries data, however how do you handle out of band data?
> [Storage implementation] Exploiting the option of using Phoenix to access
> HBase backend
> ---
>
> Key: YARN-3134
> URL: https://issues.apache.org/jira/browse/YARN-3134
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
>Reporter: Zhijie Shen
>Assignee: Zhijie Shen
>
> Quote the introduction on Phoenix web page:
> {code}
> Apache Phoenix is a relational database layer over HBase delivered as a
> client-embedded JDBC driver targeting low latency queries over HBase data.
> Apache Phoenix takes your SQL query, compiles it into a series of HBase
> scans, and orchestrates the running of those scans to produce regular JDBC
> result sets. The table metadata is stored in an HBase table and versioned,
> such that snapshot queries over prior versions will automatically use the
> correct schema. Direct use of the HBase API, along with coprocessors and
> custom filters, results in performance on the order of milliseconds for small
> queries, or seconds for tens of millions of rows.
> {code}
> It may simply our implementation read/write data from/to HBase, and can
> easily build index and compose complex query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
