[
https://issues.apache.org/jira/browse/PHOENIX-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved PHOENIX-4829.
-
Resolution: Fixed
Thanks for the patch, Jimmy. I've added you as a contributor so you can
Github user asfgit closed the pull request at:
https://github.com/apache/phoenix/pull/318
---
[
https://issues.apache.org/jira/browse/PHOENIX-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated PHOENIX-4829:
Fix Version/s: 5.1.0
4.15.0
> Fixed Spelling
> --
>
>
[
https://issues.apache.org/jira/browse/PHOENIX-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser reassigned PHOENIX-4829:
---
Assignee: Jimmy Casey
> Fixed Spelling
> --
>
> Key:
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/315
Pulling this into `master`, it looks like there are some
commons-configuration issues that will need to be worked out for
GlobalPhoenixMetricsTestSink.java
---
Github user comnetwork closed the pull request at:
https://github.com/apache/phoenix/pull/319
---
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/315
> I think the only question pending in this PR is if we want JVMMetrics or
not, which are crucial from PQS POV, otherwise not really for a regular client.
Agreed. What about just making a
[
https://issues.apache.org/jira/browse/PHOENIX-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-4820:
--
Attachment: PHOENIX-4820-4.x-HBase-1.4.patch
> Optimize OrderBy for ClientAggregatePlan
>
[
https://issues.apache.org/jira/browse/PHOENIX-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-4820:
--
Attachment: (was: PHOENIX-4820-4.x-HBase-1.4.patch)
> Optimize OrderBy for ClientAggregatePlan
>
[
https://issues.apache.org/jira/browse/PHOENIX-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-4820:
--
Attachment: (was: PHOENIX-4820-4.x-HBase-1.4-v2.patch)
> Optimize OrderBy for
Ashutosh Parekh created PHOENIX-4832:
Summary: Add Canary Test Tool for Phoenix Query Server
Key: PHOENIX-4832
URL: https://issues.apache.org/jira/browse/PHOENIX-4832
Project: Phoenix
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r206968534
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r206971126
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed to
Sure I will file an INFRA ticket to change the behavior to send an email to
the issues list when an issue is commented on or issue comment is edited or
deleted.
Should we also redirect the ASF GitHub Bot emails to the issues list
instead of the dev list?
On Wed, Aug 1, 2018 at 10:20 AM, Josh
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207001759
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed
Github user karanmehta93 commented on the issue:
https://github.com/apache/phoenix/pull/315
Thanks @joshelser will update the PR soon. We have immediate requirements
for HBase-1.x versions here. That is why I mentioned that at the start of PR
Thomas -- we should be good on the mailing list being available.
Can we flip Jira over to use this new list?
On 2018/07/30 16:22:07, Josh Elser wrote: > Done.
I can't seem to find a way to figure out who the moderators of the >
currents lists are, so I put down myself, James (sorry ^.^), and
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r206974865
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed to
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/315
Just used JVisualVM to look at these metrics via the MBeans directly.
Worked just fine.
I think naming/convention when being collected from a distributed
environment needs to be thought
Given no further input, here's the draft board report. If no concerns,
I'll be sending this out sooner than later.
---
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics for
Apache Hadoop
## Issues:
- There are no issues requiring board attention at this
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r206973402
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed
Github user joshelser commented on the issue:
https://github.com/apache/phoenix/pull/315
> it looks like there are some commons-configuration issues that will need
to be worked out for GlobalPhoenixMetricsTestSink.java
Just needs to be switched to the
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207003788
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed to
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207051474
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed to
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207063036
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed
[
https://issues.apache.org/jira/browse/PHOENIX-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang updated PHOENIX-4476:
-
Comment: was deleted
(was: testing comment. (to test devlist notification fix requested by Thomas))
>
[
https://issues.apache.org/jira/browse/PHOENIX-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Sangudi updated PHOENIX-4751:
Attachment: 0001-PHOENIX-4751-Implement-client-side-hash-aggre.master.patch
> Support
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207049490
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed
Sounds reasonable to me.
On 8/1/18 1:59 PM, Thomas D'Silva wrote:
Sure I will file an INFRA ticket to change the behavior to send an email to
the issues list when an issue is commented on or issue comment is edited or
deleted.
Should we also redirect the ASF GitHub Bot emails to the issues list
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207054938
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207054877
--- Diff: phoenix-core/src/test/resources/hadoop-metrics2.properties ---
@@ -32,10 +32,9 @@
#[prefix].[source|sink].[instance].[options]
Github user xcangCRM commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207052688
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed to
Github user xcangCRM commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207053124
--- Diff: phoenix-core/src/test/resources/hadoop-metrics2.properties ---
@@ -32,10 +32,9 @@
#[prefix].[source|sink].[instance].[options]
#
Github user xcangCRM commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207053000
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed to
+1, it's alot of noise
On Wed, Aug 1, 2018, 6:29 PM Josh Elser wrote:
> Sounds reasonable to me.
>
> On 8/1/18 1:59 PM, Thomas D'Silva wrote:
> > Sure I will file an INFRA ticket to change the behavior to send an email
> to
> > the issues list when an issue is commented on or issue comment is
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207060201
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed
Github user karanmehta93 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/315#discussion_r207060270
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/monitoring/GlobalMetricRegistriesAdapter.java
---
@@ -0,0 +1,167 @@
+/*
+ * Licensed
I filed https://issues.apache.org/jira/browse/INFRA-16862 and
https://issues.apache.org/jira/browse/INFRA-16863.
On Wed, Aug 1, 2018 at 3:53 PM, Artem Ervits wrote:
> +1, it's alot of noise
>
> On Wed, Aug 1, 2018, 6:29 PM Josh Elser wrote:
>
> > Sounds reasonable to me.
> >
> > On 8/1/18
Github user twdsilva commented on the issue:
https://github.com/apache/phoenix/pull/313
Testing iss...@phoenix.apache.org.
---
+1
On Wed, Aug 1, 2018 at 10:16 AM Josh Elser wrote:
> Given no further input, here's the draft board report. If no concerns,
> I'll be sending this out sooner than later.
>
> ---
>
> ## Description:
> - Apache Phoenix enables SQL-based OLTP and operational analytics for
> Apache Hadoop
>
>
[
https://issues.apache.org/jira/browse/PHOENIX-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang updated PHOENIX-4476:
-
Attachment: (was: PHOENIX-4476-workInProgress.001.patch)
> Range scan used for point lookups if
Dinesh created PHOENIX-4833:
---
Summary: Function Undefined when using nested sub query
Key: PHOENIX-4833
URL: https://issues.apache.org/jira/browse/PHOENIX-4833
Project: Phoenix
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PHOENIX-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang updated PHOENIX-4476:
-
Attachment: PHOENIX-4476-4.x-HBase-1.3.002.patch
> Range scan used for point lookups if filter is not
Github user karanmehta93 commented on the issue:
https://github.com/apache/phoenix/pull/315
Thanks @xcangCRM and @joshelser for the review. I have addressed your
review comments and added tag support to differentiate between various types of
client when publishing metrics to JMX.
[
https://issues.apache.org/jira/browse/PHOENIX-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh updated PHOENIX-4833:
Description:
Function Undefined when using nested sub query
0:
[
https://issues.apache.org/jira/browse/PHOENIX-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang updated PHOENIX-4833:
-
Description:
Function Undefined when using nested sub query
0:
46 matches
Mail list logo
