[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregation may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Summary: ClientAggregatePlan incorrectly using limit in aggregation may cause sql with limit clause

[jira] [Updated] (PHOENIX-2752) Update query server documentation for 4.7.0 release

[ https://issues.apache.org/jira/browse/PHOENIX-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-2752: Attachment: PHOENIX-2752.patch Some rough cleanup to the queryserver website page. > Update

[jira] [Commented] (PHOENIX-2199) Support DDL in Phoenix-Calcite integration

[ https://issues.apache.org/jira/browse/PHOENIX-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186340#comment-15186340 ] Maryann Xue commented on PHOENIX-2199: -- Should be "1.6.0", no "SNAPSHOT", the same as on master

[jira] [Commented] (PHOENIX-2752) Update query server documentation for 4.7.0 release

[ https://issues.apache.org/jira/browse/PHOENIX-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186441#comment-15186441 ] James Taylor commented on PHOENIX-2752: --- Thanks, [~elserj]. Do you know which release protobufs

[jira] [Commented] (PHOENIX-2752) Update query server documentation for 4.7.0 release

[ https://issues.apache.org/jira/browse/PHOENIX-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186462#comment-15186462 ] James Taylor commented on PHOENIX-2752: --- No worries - I'll just add that. Thanks for the updates!

[jira] [Commented] (PHOENIX-2752) Update query server documentation for 4.7.0 release

[ https://issues.apache.org/jira/browse/PHOENIX-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186448#comment-15186448 ] Josh Elser commented on PHOENIX-2752: - bq. Do you know which release protobufs were added and when

[jira] [Commented] (PHOENIX-2752) Update query server documentation for 4.7.0 release

[ https://issues.apache.org/jira/browse/PHOENIX-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186469#comment-15186469 ] Josh Elser commented on PHOENIX-2752: - Awesome, thanks. One other thing I just thought about is that

[jira] [Commented] (PHOENIX-2752) Update query server documentation for 4.7.0 release

[ https://issues.apache.org/jira/browse/PHOENIX-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186470#comment-15186470 ] James Taylor commented on PHOENIX-2752: --- One more question, and I think I'm just missing this, but

[jira] [Commented] (PHOENIX-2752) Update query server documentation for 4.7.0 release

[ https://issues.apache.org/jira/browse/PHOENIX-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15186471#comment-15186471 ] James Taylor commented on PHOENIX-2752: --- Wow, you read my mind! > Update query server

[RESULT][VOTE] Release of Apache Phoenix 4.7.0-HBase-1.1 RC6

The vote for the release of Apache Phoenix 4.7.0-HBase-1.1 RC6 is now closed and has passed with 6 binding +1s and no 0 or -1s: Thomas D'Silva* Rajeshbabu Chintaguntla* Ravi Kiran* Samarth Jain* Josh Mahonin* James Taylor* *=binding We'll push out the new release soon. Thanks to those who

[jira] [Commented] (PHOENIX-2734) Literal expressions for UNSIGNED_DATE/UNSIGNED_TIME/etc

[ https://issues.apache.org/jira/browse/PHOENIX-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185934#comment-15185934 ] Sergey Soldatov commented on PHOENIX-2734: -- [~jamestaylor] could you please take a look at it?

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185950#comment-15185950 ] Sergey Soldatov commented on PHOENIX-2535: -- Could someone take a look at it? > Create shaded

Re: [VOTE] Release of Apache Phoenix 4.7.0-HBase-1.1 RC6

+1 On Tue, Mar 8, 2016 at 7:07 AM, Josh Mahonin wrote: > +1 Ran some internal tests, and verified phoenix-spark integration > > On Sun, Mar 6, 2016 at 3:03 PM, Samarth Jain wrote: > > > +1 > > > > On Sun, Mar 6, 2016 at 12:03 PM, Ravi Kiran

Re: [VOTE] Release of Apache Phoenix 4.7.0-HBase-1.0 RC6

+1 On Tue, Mar 8, 2016 at 7:06 AM, Josh Mahonin wrote: > +1 Ran some internal tests, and verified phoenix-spark integration > > On Sun, Mar 6, 2016 at 3:04 PM, Samarth Jain wrote: > > > +1 > > > > On Sun, Mar 6, 2016 at 11:23 AM, rajeshb...@apache.org <

Re: [VOTE] Release of Apache Phoenix 4.7.0-HBase-0.98 RC6

+1 On Tue, Mar 8, 2016 at 7:06 AM, Josh Mahonin wrote: > +1 Ran some internal tests, and verified phoenix-spark integration > > On Mon, Mar 7, 2016 at 4:24 PM, Jan Fernando > wrote: > > > +1 Ran several internal Salesforce tests to validate the jar

[RESULT][VOTE] Release of Apache Phoenix 4.7.0-HBase-1.0 RC6

The vote for the release of Apache Phoenix 4.7.0-HBase-1.0 RC6 is now closed and has passed with 5 binding +1s and no 0 or -1s: Thomas D'Silva* Rajeshbabu Chintaguntla* Samarth Jain* Josh Mahonin* James Taylor* *=binding We'll push out the new release soon. Thanks to those who voted. James

[jira] [Commented] (PHOENIX-2742) Add new batchmutate APIs in HRegion without mvcc and region level locks

[ https://issues.apache.org/jira/browse/PHOENIX-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184722#comment-15184722 ] Anoop Sam John commented on PHOENIX-2742: - Index cells RK will be different.. Ya.. I did not

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Summary: ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Fix Version/s: (was: 4.7.0) > ClientAggregatePlan incorrectly uses limit in aggregation may cause

[jira] [Comment Edited] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185116#comment-15185116 ] chenglei edited comment on PHOENIX-2753 at 3/8/16 3:59 PM: --- Sorry,I found the

[jira] [Created] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

chenglei created PHOENIX-2753: - Summary: ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave Key: PHOENIX-2753 URL: https://issues.apache.org/jira/browse/PHOENIX-2753

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Commented] (PHOENIX-2752) Update query server documentation for 4.7.0 release

[ https://issues.apache.org/jira/browse/PHOENIX-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185071#comment-15185071 ] Josh Elser commented on PHOENIX-2752: - Thanks for the ping, [~jamestaylor]. Let me work on an update

Re: [VOTE] Release of Apache Phoenix 4.7.0-HBase-0.98 RC6

+1 Ran some internal tests, and verified phoenix-spark integration On Mon, Mar 7, 2016 at 4:24 PM, Jan Fernando wrote: > +1 Ran several internal Salesforce tests to validate the jar functionally. > > On Sun, Mar 6, 2016 at 8:07 PM, Mujtaba Chohan

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Fix Version/s: 4.7.0 > ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregation,Phoenix may compile the sql to get

Re: [VOTE] Release of Apache Phoenix 4.7.0-HBase-1.0 RC6

+1 Ran some internal tests, and verified phoenix-spark integration On Sun, Mar 6, 2016 at 3:04 PM, Samarth Jain wrote: > +1 > > On Sun, Mar 6, 2016 at 11:23 AM, rajeshb...@apache.org < > chrajeshbab...@gmail.com> wrote: > > > +1 Ran integration tests and all passed. > > > >

Re: [VOTE] Release of Apache Phoenix 4.7.0-HBase-1.1 RC6

+1 Ran some internal tests, and verified phoenix-spark integration On Sun, Mar 6, 2016 at 3:03 PM, Samarth Jain wrote: > +1 > > On Sun, Mar 6, 2016 at 12:03 PM, Ravi Kiran > wrote: > > > +1. Ran the tests . All look good. > > > > On Sun, Mar 6,

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Updated] (PHOENIX-2753) ClientAggregatePlan incorrectly using limit in aggregate may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-2753: -- Description: When we execute a sql with subquery and aggregate,Phoenix may compile the sql to a

[jira] [Resolved] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei resolved PHOENIX-2753. --- Resolution: Fixed sorry,I found the 2279 fixed this problem > ClientAggregatePlan incorrectly uses

[jira] [Comment Edited] (PHOENIX-2753) ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with limit clause to misbehave

[ https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185116#comment-15185116 ] chenglei edited comment on PHOENIX-2753 at 3/8/16 3:52 PM: --- sorry,I found the

[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=15185118#comment-15185118 ] James Taylor commented on PHOENIX-1311: --- I like the idea of having this just impact the physical

Problem with CDH 5.5 with enabling mutable index on table

I tried to enable secondry index on one of table but it fails with following exception. *0: jdbc:phoenix:v-in-sd-hack-03:2181> CREATE INDEX agent_id_idx ON transactions (AGENT_ID);* *Error: ERROR 1029 (42Y88): Mutable secondary indexes must have the hbase.regionserver.wal.codec property set to