[
https://issues.apache.org/jira/browse/PHOENIX-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966874#comment-15966874
]
Geoffrey Jacoby commented on PHOENIX-3782:
------------------------------------------
As it turns out, we already have this chunking logic because of PHOENIX-541,
which chunks if the max rows OR a max byte size is exceeded. All that should be
needed is to remove the throwIfTooBig check so that this logic can be reached
in the too-many-rows case.
> MutationStates with too many rows should transparently split requests instead
> of throwing exception
> ---------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-3782
> URL: https://issues.apache.org/jira/browse/PHOENIX-3782
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.10.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
>
> For a long time the Phoenix client has had a throwIfTooBig() check in
> MutationState that throws an exception if the MutationState has more rows
> than a config value. Since the correct solution is always "split up the rows
> into manageable chunks and submit to HBase one chunk at a time", we should do
> that rather than throwing back to the user.
> In addition, we should lower the default for the max rows, which right now is
> quite high at 500K rows.
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
