phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jaanai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4900) Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message to recommend turning autocommit off for deletes
Date Wed, 06 Mar 2019 03:44:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785189#comment-16785189
] 

jaanai commented on PHOENIX-4900:
---------------------------------

{noformat}
+ MAX_MUTATION_SIZE_EXCEEDED(729, "LIM01", "MutationState size is bigger" +
+ " than maximum allowed number of rows, please turning autocommit on and try it again."),
+ MAX_MUTATION_SIZE_BYTES_EXCEEDED(730, "LIM02", "MutationState size is " +
+ "bigger than maximum allowed number of bytes, please turning autocommit on " +
+ "and try it again."),
{noformat}
Using Upsert and Upser Select also can trigger MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED
exception. Is there a reasonable approach to recommend to turn  autocommit on for Upsert and
Upser Select ?

> Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message
to recommend turning autocommit off for deletes
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4900
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4900
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Thomas D'Silva
>            Assignee: Xinyi Yan
>            Priority: Major
>         Attachments: PHOENIX-4900.patch
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message