RE: How to troubleshoot 'Could not find hash cache for joinId' which is failing always for some users and never for others

I ran the command along with ‘update statistics ’. However, the hash join error remains. The plan is to upgrade to Phoenix 4.8. However, that will take time. I still need to pursue other options. Given this an HBase table. I am wondering if recreating the view would help. Any suggestions are

RE: How to troubleshoot 'Could not find hash cache for joinId' which is failing always for some users and never for others

I was looking at the 4.2.2 source code. I could not find the “USE_SORT_MERGE_JOIN” anywhere. Thank you for clarifying. In the past, the stats were manually updated using the “UPDATE STATISTICS asset_metadata’ command. What is the side effect of deleting the guide posts? Will new stats get

Re: How to troubleshoot 'Could not find hash cache for joinId' which is failing always for some users and never for others

Hi Chabot, "USE_SORT_MERGE_JOIN" hint is supported from v4.3.0 onwards. As your version is 4.2.2 ,so it is not getting used in your query. It seems , your stats are corrupted because of region merge or split, resulting in some regionserver to not receive a hash join cache. Though stats

RE: How to troubleshoot 'Could not find hash cache for joinId' which is failing always for some users and never for others

I’ve captured the execution plan by running a standalone tool. [hpSDID@11 deviceId="-" reqId="-" threadId="1"] executing SQL select /*+ USE_SORT_MERGE_JOIN */T1.L,T1.C,T1.A,T1.R,T1.W,T1.P,T1.N,T1.E,T1.S,T1.M, T1.CW, T1 .T,T1.Y,T1.U FROM "asset_metadata" T1 WHERE R=(SELECT MAX(R) from

Re: How to troubleshoot 'Could not find hash cache for joinId' which is failing always for some users and never for others

It's quite possible you're hitting a bug that has been fixed as you're 5 or 6 releases behind on Phoenix and 14 patch releases behind on HBase. Thanks, James On Thu, May 5, 2016 at 8:14 AM, Kathiresan S wrote: > We had a similar problem while using explicit JOIN

Re: How to troubleshoot 'Could not find hash cache for joinId' which is failing always for some users and never for others

We had a similar problem while using explicit JOIN in the query (we didn't have sub-queries). We worked it around by switching to sort merge join from hash join (to get it run, though it'll be bit slower than hash join as per documentation) Try adding the hint */*+ USE_SORT_MERGE_JOIN*/ *in the