[
https://issues.apache.org/jira/browse/PHOENIX-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726278#comment-16726278
]
Thomas D'Silva commented on PHOENIX-5073:
-----------------------------------------
[~kiran.maturi] can you attach the full exception stack trace so we can see
where the error is thrown from the old client.
I spoke to [~vincentpoon] offline, we might have to modify the returned PTable
with the PIndexState that was used in 4.13 if we detect that the request was
from an old client.
{code}
public void getTable(RpcController controller, GetTableRequest request,
RpcCallback<MetaDataResponse> done)
...
// the PTable of views and indexes on views might get updated
because a column is added to one of
// their parents (this won't change the timestamp)
if (table.getType()!=PTableType.TABLE || table.getTimeStamp() !=
tableTimeStamp) {
builder.setTable(PTableImpl.toProto(table));
}
{code}
> Invalid PIndexState during rolling upgrade from 4.13 to 4.14
> ------------------------------------------------------------
>
> Key: PHOENIX-5073
> URL: https://issues.apache.org/jira/browse/PHOENIX-5073
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Reporter: Kiran Kumar Maturi
> Assignee: Kiran Kumar Maturi
> Priority: Major
>
> While doing a rolling upgrade from 4.13 to 4.14 we are seeing this exception.
> {code:java}
> java.util.concurrent.ExecutionException: java.sql.SQLException:
> java.lang.IllegalArgumentException: Unable to PIndexState enum for serialized
> value of 'w'{code}
> Steps to reproduce.
> # Start the server on 4.14
> # Start load with both 4.13 and 4.14 clients
> # 4.13 client will show the above error
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
