You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Jesse Yates (JIRA)" <ji...@apache.org> on 2014/02/27 01:13:19 UTC
[jira] [Created] (PHOENIX-78) MetaDataUtil must respect
ClientKeyValue usage
Jesse Yates created PHOENIX-78:
----------------------------------
Summary: MetaDataUtil must respect ClientKeyValue usage
Key: PHOENIX-78
URL: https://issues.apache.org/jira/browse/PHOENIX-78
Project: Phoenix
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 3.0.0
We can get into cases where the ClientKeyValue is being generated for metadata operations, but being operated on as a regular KeyValue, for instance:
{quote}
java.lang.UnsupportedOperationException: ClientKeyValue does not support a single backing buffer.
at org.apache.phoenix.client.ClientKeyValue.getBuffer(ClientKeyValue.java:500)
at org.apache.phoenix.util.MetaDataUtil.getMutationKeyValue(MetaDataUtil.java:202)
at org.apache.phoenix.util.MetaDataUtil.getMutationKVByteValue(MetaDataUtil.java:193)
at org.apache.phoenix.util.MetaDataUtil.isMultiTenant(MetaDataUtil.java:245)
at org.apache.phoenix.query.ConnectionQueryServicesImpl.createTable(ConnectionQueryServicesImpl.java:887)
at org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:1107)
at org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:409)
at org.apache.phoenix.compile.CreateTableCompiler$2.execute(CreateTableCompiler.java:174)
at org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:224)
at org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:185)
at org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(PhoenixPreparedStatement.java:137)
at org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(PhoenixPreparedStatement.java:142)
{quote}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)