[jira] [Commented] (PHOENIX-57) ClientKeyValue doesn't work in debug mode

["Jesse Yates (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904476#comment-13904476 ] 

Jesse Yates commented on PHOENIX-57:
------------------------------------

Since this only occurs in debugging, we don't need to be too concerned with optimizing here. If we really wanted, we could go back to a KeyValueBuilder which knows how its KeyValue was created, and then pick the right algorithm. However, that seems far more convoluted than just catching an exception and falling back to the correct implementation.

Patch coming shortly.

> ClientKeyValue doesn't work in debug mode
> -----------------------------------------
>
>                 Key: PHOENIX-57
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-57
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Jesse Yates
>             Fix For: 3.0.0
>
>
> When debug logging is enabled, we run MutationState#logMutationSize. This then gets the buffer from the KeyValue. However, the clientKeyValue doesn't support a single backing buffer, causing an UnsupportedOperationException. We need to be able to support both.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)