Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-30 Thread Istvan Toth
. SUCCESS [07:03 > min] > [INFO] Phoenix Hbase 2.4.0 compatibility .. SUCCESS [ > 37.760 s] > [INFO] Phoenix Hbase 2.3.0 compatibility .. SUCCESS [01:40 > min] > [INFO] Phoenix Hbase 2.2.5 compatibility ...... SUCCESS [01:03 > min] > [INFO] Phoenix Hbase 2.1.6 compatibility .. SUCCESS [ > 39.114 s] > [INFO] Pho

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-29 Thread Simon Mottram
0 PM To: user@phoenix.apache.org Subject: Re: Urgent problem with Phoenix function LAST_VALUE and joins git clone https://github.com/apache/phoenix mvn clean package bin/phoenix_sandbox.py use the host and port displayed to start sqlline.py On Thu, Sep 30, 2021 at 4:21 AM Simon Mottram ma

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-29 Thread Istvan Toth
oenix dev > channel is the place to ask questions. > > Cheers > > Simon > -- > *From:* Istvan Toth > *Sent:* 29 September 2021 7:37 PM > *To:* user@phoenix.apache.org > *Subject:* Re: Urgent problem with Phoenix function LAST_VALUE and joi

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-29 Thread Simon Mottram
gt; Sent: 29 September 2021 11:32 AM To: Geoffrey Jacoby mailto:gjac...@salesforce.com>> Cc: user mailto:user@phoenix.apache.org>> Subject: Re: Urgent problem with Phoenix function LAST_VALUE and joins Geoffrey, Thank you for pointing out this. I mixed up release numbers. Yes, the pagin

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-29 Thread
9, 2021 at 12:36 AM Simon Mottram >> wrote: >> Ok, should I bug this in your JIRA? >> >> I will try and setup a more reproducible series of steps >> >> Cheers >> >> S >> From: Kadir Ozdemir >> Sent: 29 September 2021 11:32 AM >> To: Geof

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-28 Thread Istvan Toth
e don't have an hbase-site.xml (unless it's embedded in the > thin client jar. > > Cheers > > S > -- > *From:* Kadir Ozdemir > *Sent:* 28 September 2021 7:45 PM > *To:* user > *Subject:* Re: Urgent problem with Phoenix function LAST_

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-28 Thread Simon Mottram
Ok, should I bug this in your JIRA? I will try and setup a more reproducible series of steps Cheers S From: Kadir Ozdemir Sent: 29 September 2021 11:32 AM To: Geoffrey Jacoby Cc: user Subject: Re: Urgent problem with Phoenix function LAST_VALUE and joins

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-28 Thread Kadir Ozdemir
t;> >> S >> -------------- >> *From:* Kadir Ozdemir >> *Sent:* 28 September 2021 7:45 PM >> *To:* user >> *Subject:* Re: Urgent problem with Phoenix function LAST_VALUE and joins >> >> In Phoenix 5.0 we introduced a new server side p

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-28 Thread Geoffrey Jacoby
September 2021 7:45 PM > *To:* user > *Subject:* Re: Urgent problem with Phoenix function LAST_VALUE and joins > > In Phoenix 5.0 we introduced a new server side paging feature to eliminate > timeouts due long running server side computations such aggregation and > joins. I wonder

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-28 Thread Simon Mottram
jar. Cheers S From: Kadir Ozdemir Sent: 28 September 2021 7:45 PM To: user Subject: Re: Urgent problem with Phoenix function LAST_VALUE and joins In Phoenix 5.0 we introduced a new server side paging feature to eliminate timeouts due long running server side co

Re: Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-27 Thread Kadir Ozdemir
In Phoenix 5.0 we introduced a new server side paging feature to eliminate timeouts due long running server side computations such aggregation and joins. I wonder if this new feature caused your issue. If so, the work around is to disable it by setting phoenix.server.paging.enabled to false in hbas

Urgent problem with Phoenix function LAST_VALUE and joins

2021-09-27 Thread Simon Mottram
Hi Got my fingers crossed that there's a work around for this as this really is a big problem for us We are using: Amazon EMR Release label:emr-6.1.0 Hadoop distribution:Amazon Applications:Hbase 2.2.5, Hive 3.1.2, Phoenix 5.0.0, Pig 0.17.0 Thin Client version: phoenix-5.0.0-HBase-2.0-thin-cl