[
https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924470#comment-13924470
]
Mujtaba Chohan commented on PHOENIX-99:
---------------------------------------
After upgrade to 3.0 (with both 2.x and 3.0 jars on server), following
exception happens on querying metadata from SYSTEM.TABLE with 2.x client
(SYSTEM.TABLE has org.apache.phoenix.coprocessor.GroupedAggregateRegionObserver
and org.apache.phoenix.coprocessor.ServerCachingEndpointImpl CP)
ERROR org.apache.hadoop.hbase.regionserver.HRegionServer: Failed openScanner
org.apache.hadoop.hbase.DoNotRetryIOException:
SYSTEM.TABLE,,1394233259367.06566b0cc94752a151f63b1c90ec24f6.: 76
at
org.apache.phoenix.util.ServerUtil.throwIOException(ServerUtil.java:73)
at
org.apache.phoenix.coprocessor.BaseScannerRegionObserver.postScannerOpen(BaseScannerRegionObserver.java:51)
at
org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.postScannerOpen(RegionCoprocessorHost.java:1316)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.internalOpenScanner(HRegionServer.java:2566)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:2534)
at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:323)
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1426)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 76
at
org.apache.phoenix.expression.BaseCompoundExpression.readFields(BaseCompoundExpression.java:105)
at
org.apache.phoenix.expression.OrderByExpression.readFields(OrderByExpression.java:94)
at
org.apache.phoenix.coprocessor.ScanRegionObserver.deserializeFromScan(ScanRegionObserver.java:119)
at
org.apache.phoenix.coprocessor.ScanRegionObserver.doPostScannerOpen(ScanRegionObserver.java:190)
at
org.apache.phoenix.coprocessor.BaseScannerRegionObserver.postScannerOpen(BaseScannerRegionObserver.java:49)
> Automatic white list based upgrade from 2.2 to 3.0
> --------------------------------------------------
>
> Key: PHOENIX-99
> URL: https://issues.apache.org/jira/browse/PHOENIX-99
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 3.0.0
>
> Attachments: coproc-tweak.diff, patch-3.diff, patch.diff, patch.diff
>
>
> Auto upgrade tables from Phoenix 2.2.2/2.2.3 format to Phoenix 3.0 format.
> Note that upgrade is only attempted to be performed once, upon first
> connection to a cluster. A table is only upgraded if it is white listed based
> on the following new config property: phoenix.client.autoUpgradeWhiteList
> If this property is not present, no tables will be upgraded. The config
> property may have the following values:
> - * which means upgrade everything or
> - a comma separated list of fully qualified, case sensitive names (note that
> by default, Phoenix stores table names in uppercase unless put them in double
> quotes at DDL time)
> Examples:
> {code}
> <property>
> <name>phoenix.client.autoUpgradeWhiteList</name>
> <value>*</value> <!- will upgrade all tables ->
> </property>
> {code}
> {code}
> <property>
> <name>phoenix.client.autoUpgradeWhiteList</name>
> <value>MY_SCHEMA.MY_TABLE, OTHER_TABLE</value>
> </property>
> {code}
> The upgrade is only run once per connection to a cluster (when the
> SYSTEM.CATALOG is created). If you need to force it to run again after that,
> you can remove or set to "false" the UpgradeTo30 value that's stored in the
> metadata of the SYSTEM.CATALOG table.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
