h Elser [mailto:els...@apache.org]
Sent: Friday, July 21, 2017 7:58 PM
To: user@phoenix.apache.org
Subject: Re: Difference in response time for Join queries with a
hint.(ResultSet.next() takes a lot of time )
Are you giving equal amounts of Java heap to both applications?
On 7/21/17 5:04 AM, Siddhar
iday, July 21, 2017 7:58 PM
To: user@phoenix.apache.org
Subject: Re: Difference in response time for Join queries with a
hint.(ResultSet.next() takes a lot of time )
Are you giving equal amounts of Java heap to both applications?
On 7/21/17 5:04 AM, Siddharth Ubale wrote:
> Hi,
>
>
To: user@phoenix.apache.org
Subject: Re: Difference in response time for Join queries with a
hint.(ResultSet.next() takes a lot of time )
Are you giving equal amounts of Java heap to both applications?
On 7/21/17 5:04 AM, Siddharth Ubale wrote:
> Hi,
>
> Using phoenix 4.10 with
@phoenix.apache.org
*Subject:* RE: Difference in response time for Join queries with a
hint.(ResultSet.next() takes a lot of time )
Hi Sergey,
Yes Sergey. We are also on the same page with you hence we were
wondering about this behavior.
Please find my queries below :
*Query 1: *
select
Hi,
Using phoenix 4.10 with hbase0.98.
Thanks,
Siddharth
From: Siddharth Ubale [mailto:siddharth.ub...@syncoms.com]
Sent: Friday, July 21, 2017 12:24 PM
To: user@phoenix.apache.org
Subject: RE: Difference in response time for Join queries with a
hint.(ResultSet.next() takes a lot of time )
Hi
='MG
road190'
and terms.terms292FEC765F1C486F85A509D88096F098tenantid = 'c83'
and company.olapcompany1292FEC765F1C486F85A509D88096F098versionnum is not null
You can use the above 2 queries to reproduce the issue.
Thanks,
Siddharth Ubale
From: sergey.solda...@gmail.com [mailto:
Hi Siddharth,
That's sounds strange because sqlline tool is just an another db client
and it uses the same JDBC API. By any chance can you provide the DDLs and
queries, so we will be able to reproduce the problem?
Thanks,
Sergey
On Wed, Jul 19, 2017 at 11:16 PM, Siddharth Ubale <
siddharth.ub...
Hi ,
I am executing 2 join queries which give the same response.
Query 1: Nested join over 5 tables where . The query uses rowkey "like"
statement to narrow down to the filtered columns. This query in Phoenix sqlline
terminal takes 800millisecs to execute.
Query 2: Is a inner join over the same
