[
https://issues.apache.org/jira/browse/PHOENIX-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026787#comment-16026787
]
Hudson commented on PHOENIX-3784:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-master #1627 (See
[https://builds.apache.org/job/Phoenix-master/1627/])
PHOENIX-3784 Chunk commit data using lower of byte-based and row-count (thomas:
rev e2ec76559b1d36fee7b696d7ee2989059e2bbe8c)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/JDBCUtil.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/execute/MutationState.java
* (edit)
phoenix-core/src/test/java/org/apache/phoenix/jdbc/PhoenixDriverTest.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/QueryMoreIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
> Chunk commit data using lower of byte-based and row-count limits
> ----------------------------------------------------------------
>
> Key: PHOENIX-3784
> URL: https://issues.apache.org/jira/browse/PHOENIX-3784
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Thomas D'Silva
> Fix For: 4.11.0
>
> Attachments: PHOENIX-3784-final.patch, PHOENIX-3784.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
