[
https://issues.apache.org/jira/browse/PHOENIX-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969456#comment-15969456
]
James Taylor commented on PHOENIX-3788:
---------------------------------------
Another, slightly more complex issue is when mutations are processed on the
server side. In this case, the client will still reflect the batch size as all
rows across the entire statement, even though the server will batch it up
according to {{phoenix.mutate.batchSize}}. We won't know definitely on the
client what this config parameter is set to on the server. We could assume it's
the same, or we could potentially pass the config value from the client to the
server and base the batching size on that.
> GLOBAL_MUTATION_BATCH_SIZE should reflect size of chunked batches
> -----------------------------------------------------------------
>
> Key: PHOENIX-3788
> URL: https://issues.apache.org/jira/browse/PHOENIX-3788
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.10.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
>
> As part of PHOENIX-541, we started chunking large MutationStates into
> multiple smaller batches transparently. However, the relevant metric,
> GLOBAL_MUTATION_BATCH_SIZE, still is updated with the total batch size, not
> the size of each chunk. This means you can't see the actual batch sizes which
> are being submitted to HBase.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
