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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 4.10.0
• Assignee: Geoffrey Jacoby
• Reporter: Geoffrey Jacoby
• Created: 12/Apr/17 23:42
• Updated: 30/May/17 21:49
• Resolved: 30/May/17 21:49

Description

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.

Issue Links

• duplicates: PHOENIX-3784 Chunk commit data using lower of byte-based and row-count limits
• supercedes: PHOENIX-3513 Throw SQLException instead of IllegalStateException when max commit size exceeded