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

Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2023/04/05 07:26:00 UTC

[jira] [Updated] (PHOENIX-6821) Batching with auto-commit connections

     [ https://issues.apache.org/jira/browse/PHOENIX-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viraj Jasani updated PHOENIX-6821:
----------------------------------
    Fix Version/s: 5.2.0
                   5.1.4

> Batching with auto-commit connections
> -------------------------------------
>
>                 Key: PHOENIX-6821
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6821
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Kadir Ozdemir
>            Assignee: Hari Krishna Dara
>            Priority: Major
>             Fix For: 5.2.0, 5.1.4
>
>
> Phoenix commits the commands of a batch individually when executeBatch() is called if auto commit is enabled on the connection.  For example, if a batch of 100 upsert statements is created using addBatch() within an auto-commit mode connection then when executeBatch() is called, Phoenix creates 100 HBase batches each with a single mutation, i.e., one for each upsert. This defeats the purpose of batching. The correct behavior is to commit the entire batch of upsert statements using the minimum number of HBase batches. This means if the entire batch of upsert statements fits in a single HBase batch, then one HBase batch should be used.
> Please note for connections without auto-commit, Phoenix behaves correctly, that is, the entire batch of upsert commands is committed using the minimum number of HBase batches.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)