Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
We have a byte-based limit that determines how much data we send over at a time when a commit occurs (PHOENIX-541), but we should also have a row-count limit. We could check both the byte-based limit and the row-count limit and ensure the batch size meets both constraints. This would help prevent too many rows from being submitted to the server at one time and decrease the likelihood of conflicting rows amongst batches.
Attachments
Attachments
Issue Links
- is duplicated by
-
PHOENIX-3782 MutationStates with too many rows should transparently split requests instead of throwing exception
- Resolved