You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2017/04/12 23:42:41 UTC

[jira] [Created] (PHOENIX-3782) MutationStates with too many rows should transparently split requests instead of throwing exception

Geoffrey Jacoby created PHOENIX-3782:
----------------------------------------

             Summary: 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)