[
https://issues.apache.org/jira/browse/PHOENIX-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666301#comment-15666301
]
Samarth Jain commented on PHOENIX-3481:
---------------------------------------
bq. Actually, you're better off if you can track down and change it on the
server-side as otherwise we'll need to check-in a new Phoenix jar to core
(assuming this is potentially a real issue rather than a test only issue).
[~jamestaylor], I looked at the changes in HBase code between the versions
0.98.17 and 0.98.23 and I see that HBASE-15245 added new checks that were not
present before. Specifically this change in HRegionServer:
{code}
+ ByteString value = regionSpecifier.getValue();
+ RegionSpecifierType type = regionSpecifier.getType();
+ switch (type) {
+ case REGION_NAME:
+ byte[] regionName = value.toByteArray();
+ String encodedRegionName = HRegionInfo.encodeRegionName(regionName);
+ return getRegionByEncodedName(regionName, encodedRegionName);
+ case ENCODED_REGION_NAME:
+ return getRegionByEncodedName(value.toStringUtf8());
+ default:
+ throw new DoNotRetryIOException(
+ "Unsupported region specifier type: " + type);
+ }
{code}
The call
{code}
getRegionByEncodedName(regionName, encodedRegionName);
{code}
throws a NotServingRegionException. This exception is thrown before the Phoenix
coprocessor hook for doPostScannerOpen() could throw a
StaleRegionBoundaryCacheException for the phoenix client to retry. FWIW, this
change has also been made to HBase-1.3.0 as part of HBASE-15177.
> Phoenix initialization fails for HBase 0.98.21 and beyond
> ---------------------------------------------------------
>
> Key: PHOENIX-3481
> URL: https://issues.apache.org/jira/browse/PHOENIX-3481
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Fix For: 4.9.0
>
> Attachments: PHOENIX-3481.patch, PHOENIX-3481_master.patch,
> PHOENIX-3481_master_v2.patch, PHOENIX-3481_v3_0.98.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
