Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Thu, 12 Nov 2015 03:44:10 +0000 (UTC)
From: "Don Brinn (JIRA)" <jira@apache.org>
To: dev@phoenix.incubator.apache.org
Message-ID: <JIRA.12910890.1446768597000.46978.1447299850955@Atlassian.JIRA>
In-Reply-To: <JIRA.12910890.1446768597000@Atlassian.JIRA>
References: <JIRA.12910890.1446768597000@Atlassian.JIRA>
 <JIRA.12910890.1446768597019@arcas>
Subject: [jira] [Commented] (PHOENIX-2381) Inner Join with any table or view
 with Multi_Tenant=true causes "could not find hash cache for joinId" error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/PHOENIX-2381?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
001652#comment-15001652 ]=20

Don Brinn commented on PHOENIX-2381:
------------------------------------

I'm glad that was helpful and it's good to see the problem has been identif=
ied.  Thank you for your work to investigate and analyze the problem, [~mar=
yannxue].

> Inner Join with any table or view with Multi_Tenant=3Dtrue causes "could =
not find hash cache for joinId" error
> -------------------------------------------------------------------------=
-----------------------------------
>
>                 Key: PHOENIX-2381
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2381
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.6.0
>         Environment: This is with Phoenix version 4.6.0 and HBase version=
 0.98.4.2.2.6.0-2800-hadoop2.
>            Reporter: Don Brinn
>            Assignee: Maryann Xue
>              Labels: join, joins, multi-tenant
>         Attachments: Inner_Join_Cache-Tables_and_Views_and_Data.zip, PHOE=
NIX-2381.patch, tmp-2381.patch
>
>
> I am seeing the following error when doing an INNER JOIN of a view with M=
ULTI_TENANT=3Dtrue with any other table or view:
> java.lang.RuntimeException: org.apache.phoenix.exception.PhoenixIOExcepti=
on: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbas=
e.DoNotRetryIOException: Could not find hash cache for joinId: Ys=EF=BF=BD0=
=EF=BF=BD=EF=BF=BD%=EF=BF=BD. The cache might have expired and have been re=
moved.
>         at org.apache.phoenix.coprocessor.HashJoinRegionScanner.<init>(Ha=
shJoinRegionScanner.java:95)
>         at org.apache.phoenix.coprocessor.ScanRegionObserver.doPostScanne=
rOpen(ScanRegionObserver.java:212)
>         at org.apache.phoenix.coprocessor.BaseScannerRegionObserver.postS=
cannerOpen(BaseScannerRegionObserver.java:178)
>         at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.pos=
tScannerOpen(RegionCoprocessorHost.java:1931)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegio=
nServer.java:3178)
>         at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$Client=
Service$2.callBlockingMethod(ClientProtos.java:29994)
>         at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078=
)
>         at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108=
)
>         at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecut=
or.java:114)
>         at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java=
:94)
>         at java.lang.Thread.run(Thread.java:745)
> =20
>         at sqlline.IncrementalRows.hasNext(IncrementalRows.java:73)
>         at sqlline.TableOutputFormat.print(TableOutputFormat.java:33)
>         at sqlline.SqlLine.print(SqlLine.java:1653)
>         at sqlline.Commands.execute(Commands.java:833)
>         at sqlline.Commands.sql(Commands.java:732)
>         at sqlline.SqlLine.dispatch(SqlLine.java:808)
>         at sqlline.SqlLine.begin(SqlLine.java:681)
>         at sqlline.SqlLine.start(SqlLine.java:398)
>         at sqlline.SqlLine.main(SqlLine.java:292)
> =20
> This is with Phoenix version 4.6.0 and HBase version 0.98.4.2.2.6.0-2800-=
hadoop2.
> =20
> This seems very strongly related to the MULTI_TENANT=3Dtrue property on a=
 view or table.  I see the error whenever the view has MULTI_TENANT=3Dtrue =
and I have a tenant-specific connection to Phoenix.  I do not see the probl=
em if the MULTI_TENANT=3Dtrue property is not set on the view or if I do no=
t have a tenant-specific connection to Phoenix.
> =20
> Here is an example SQL statement that has this error when the view INVENT=
ORY has the MULTI_TENANT=3Dtrue property and I have a tenant-specific conne=
ction, but that succeeds in other cases. (The view PRODUCT_IDS is not Multi=
-Tenant.)
> SELECT * FROM INVENTORY INNER JOIN PRODUCT_IDS ON (PRODUCT_ID =3D INVENTO=
RY.ID)
> =20
> Note:  "INNER JOIN" fails under these conditions, as does "LEFT OUTER JOI=
N".  However, "RIGHT OUTER JOIN" and "FULL OUTER JOIN" do work.  Also, if I=
 tell Phoenix to use a Sort Join for the Inner Join or Left Outer Join then=
 it does work, e.g.  SELECT /\*+ USE_SORT_MERGE_JOIN\*/ * FROM INVENTORY IN=
NER JOIN PRODUCT_IDS ON (PRODUCT_ID =3D INVENTORY.ID); works.
> =20
> This seems to be the same problem that was discussed previously in this m=
ailing list:  https://mail-archives.apache.org/mod_mbox/phoenix-user/201507=
.mbox/%3CCAOtKWX5XFbwkJF--0k-zj91TfdqWFq6RmuQW0R_LoJCNj1aMhg@mail.gmail.com=
%3E=20


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)