Re: Continuing Trace UI work?

Thanks Jesse, For you ideas, Yes we can more focus in to zipkin On Thu, Mar 24, 2016 at 1:07 AM, Jesse Yates wrote: > I sent this to James the other day, didn't get a chance to post it on the > JIRA yet: > > *I was poking around htrace and zipkin and it looks like zipkin has

[jira] [Commented] (PHOENIX-2541) Support addBatch() and updateBatch() through QueryServer

[ https://issues.apache.org/jira/browse/PHOENIX-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209727#comment-15209727 ] Josh Elser commented on PHOENIX-2541: - This just landed in Avatica 1.8.0. Will likely get a release

[jira] [Commented] (PHOENIX-2714) Correct byte estimate in BaseResultIterators and expose as interface

[ https://issues.apache.org/jira/browse/PHOENIX-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209665#comment-15209665 ] Maryann Xue commented on PHOENIX-2714: -- Let's target it for next release. > Correct byte estimate

[jira] [Commented] (PHOENIX-2722) support mysql "limit,offset" clauses

[ https://issues.apache.org/jira/browse/PHOENIX-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209663#comment-15209663 ] ASF GitHub Bot commented on PHOENIX-2722: - Github user maryannxue commented on the pull request:

[GitHub] phoenix pull request: PHOENIX-2722 support mysql limit,offset clau...

Github user maryannxue commented on the pull request: https://github.com/apache/phoenix/pull/154#issuecomment-200637757 @ankitsinghal Thank you very much for the pull request! I am impressed by how many details you have taken into account in your commit. It took me quite a while to

Re: GSoC - 2016

Hi James. Thanks for the feedback. I will do necessary changes. Thanks *T. Pranavan* *BSc Eng Undergraduate| Department of Computer Science & Engineering ,University of Moratuwa* *Mobile| *0775136836 On 23 March 2016 at 21:19, James Taylor wrote: > Looks very good,

[jira] [Commented] (PHOENIX-2722) support mysql "limit,offset" clauses

[ https://issues.apache.org/jira/browse/PHOENIX-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209654#comment-15209654 ] ASF GitHub Bot commented on PHOENIX-2722: - Github user maryannxue commented on a diff in the

[GitHub] phoenix pull request: PHOENIX-2722 support mysql limit,offset clau...

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/154#discussion_r57269833 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java --- @@ -324,10 +328,13 @@ protected QueryPlan

[jira] [Commented] (PHOENIX-2722) support mysql "limit,offset" clauses

[ https://issues.apache.org/jira/browse/PHOENIX-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209645#comment-15209645 ] ASF GitHub Bot commented on PHOENIX-2722: - Github user maryannxue commented on a diff in the

[GitHub] phoenix pull request: PHOENIX-2722 support mysql limit,offset clau...

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/154#discussion_r57269271 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/compile/SubselectRewriter.java --- @@ -202,14 +204,30 @@ private SelectStatement

[jira] [Commented] (PHOENIX-2794) Flatten nested aggregate queries when possible

[ https://issues.apache.org/jira/browse/PHOENIX-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209545#comment-15209545 ] James Taylor commented on PHOENIX-2794: --- [~julianhyde] - does Calcite already do anything along

[jira] [Updated] (PHOENIX-2794) Flatten nested aggregate queries when possible

[ https://issues.apache.org/jira/browse/PHOENIX-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2794: -- Summary: Flatten nested aggregate queries when possible (was: Optimize aggregates of

[jira] [Created] (PHOENIX-2794) Optimize aggregates of aggregates when possible

James Taylor created PHOENIX-2794: - Summary: Optimize aggregates of aggregates when possible Key: PHOENIX-2794 URL: https://issues.apache.org/jira/browse/PHOENIX-2794 Project: Phoenix Issue

[jira] [Created] (PHOENIX-2793) Date-time functions on null dates return no data

Kevin Liew created PHOENIX-2793: --- Summary: Date-time functions on null dates return no data Key: PHOENIX-2793 URL: https://issues.apache.org/jira/browse/PHOENIX-2793 Project: Phoenix Issue

[jira] [Commented] (PHOENIX-2783) Creating secondary index with duplicated columns makes the catalog corrupted

[ https://issues.apache.org/jira/browse/PHOENIX-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209236#comment-15209236 ] Biju Nair commented on PHOENIX-2783: Thanks [~sergey.soldatov] for sharing the experiment results.

[jira] [Commented] (PHOENIX-2751) Wrong filtering for VARCHAR with null

[ https://issues.apache.org/jira/browse/PHOENIX-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209100#comment-15209100 ] Sergey Soldatov commented on PHOENIX-2751: -- Nick, could you please check whether this bug is

Re: Continuing Trace UI work?

I sent this to James the other day, didn't get a chance to post it on the JIRA yet: *I was poking around htrace and zipkin and it looks like zipkin has a jdbc storage plugin. Might be a nice little piece of work to integrate phoenix into that - would act as storage for the zipkin collector

Re: Would like to volunteer for 4.8 release

+1. Thanks, Rajeshbabu. Likely will be some perf improvements too that Samarth, Thomas, and I are working on. James On Wednesday, March 23, 2016, rajeshb...@apache.org < chrajeshbab...@gmail.com> wrote: > Hi Team, > > There is lot of working going on mainly local indexing new

Would like to volunteer for 4.8 release

Hi Team, There is lot of working going on mainly local indexing new implementation, namespace support, some work in tracing, stabilization of transactions as well some performance improvements like IndexTool improvements and so on. I think April 3rd or 4th week would be better time for 4.8

[jira] [Comment Edited] (PHOENIX-2783) Creating secondary index with duplicated columns makes the catalog corrupted

[ https://issues.apache.org/jira/browse/PHOENIX-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208939#comment-15208939 ] Sergey Soldatov edited comment on PHOENIX-2783 at 3/23/16 6:43 PM: ---

[jira] [Commented] (PHOENIX-2783) Creating secondary index with duplicated columns makes the catalog corrupted

[ https://issues.apache.org/jira/browse/PHOENIX-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208939#comment-15208939 ] Sergey Soldatov commented on PHOENIX-2783: -- Actually I was thinking about using HashSet, but I

[jira] [Updated] (PHOENIX-2792) Enable Kerberos auth over SPNEGO for QueryServer

[ https://issues.apache.org/jira/browse/PHOENIX-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-2792: Summary: Enable Kerberos auth over SPNEGO for QueryServer (was: Enable Kerberos auth over SPNEGO

[jira] [Updated] (PHOENIX-2792) Enable Kerberos auth over SPNEGO for QuerySErver

[ https://issues.apache.org/jira/browse/PHOENIX-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-2792: Attachment: PHOENIX-2792.patch Here's my test patch (won't build unless you get the avatica

[jira] [Created] (PHOENIX-2792) Enable Kerberos auth over SPNEGO for QuerySErver

Josh Elser created PHOENIX-2792: --- Summary: Enable Kerberos auth over SPNEGO for QuerySErver Key: PHOENIX-2792 URL: https://issues.apache.org/jira/browse/PHOENIX-2792 Project: Phoenix Issue

[jira] [Commented] (PHOENIX-2783) Creating secondary index with duplicated columns makes the catalog corrupted

[ https://issues.apache.org/jira/browse/PHOENIX-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208775#comment-15208775 ] Biju Nair commented on PHOENIX-2783: Hi [~sergey.soldatov], will it make the code better if we use

[jira] [Commented] (PHOENIX-1311) HBase namespaces surfaced in phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208633#comment-15208633 ] ASF GitHub Bot commented on PHOENIX-1311: - Github user JamesRTaylor commented on the pull

[GitHub] phoenix pull request: PHOENIX-1311 HBase namespaces surfaced in ph...

Github user JamesRTaylor commented on the pull request: https://github.com/apache/phoenix/pull/153#issuecomment-200406903 I just wonder how that'll work, @ankitsinghal. If it works, I suppose it's ok, but it muddies things a bit as views are all supposed to be contained in the same

[jira] [Updated] (PHOENIX-2751) Wrong filtering for VARCHAR with null

[ https://issues.apache.org/jira/browse/PHOENIX-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Hryhoriev updated PHOENIX-2751: Priority: Critical (was: Major) > Wrong filtering for VARCHAR with null >

[jira] [Commented] (PHOENIX-1311) HBase namespaces surfaced in phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208121#comment-15208121 ] ASF GitHub Bot commented on PHOENIX-1311: - Github user ankitsinghal commented on the pull

[GitHub] phoenix pull request: PHOENIX-1311 HBase namespaces surfaced in ph...

Github user ankitsinghal commented on the pull request: https://github.com/apache/phoenix/pull/153#issuecomment-200264320 Currently ,VIEW can be created in different schema name than it's base table name. are you recommending to use same schema? I checked MySQL and postgres