phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4671) Fix minor size accounting bug for MutationSize
Date Wed, 28 Mar 2018 18:52:00 GMT

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

Lars Hofhansl commented on PHOENIX-4671:
----------------------------------------

Lemme file a separate issue for the test then. A test is only good if it is actually useful,
a test for a test's sake is not necessarily useful.
I can write a unit test that merges two MutationStates then calls clear() and verifies that
the estimated size is back to 0 in less than 5 minutes - I'd call that a useless test, though.


> Fix minor size accounting bug for MutationSize
> ----------------------------------------------
>
>                 Key: PHOENIX-4671
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4671
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Priority: Minor
>         Attachments: 4671.txt
>
>
> Just ran into a bug where UPSERT INTO table ... SELECT ... FROM table would fail due
to "Error: ERROR 730 (LIM02): MutationState size is bigger than maximum allowed number of
bytes (state=LIM02,code=730)" even with auto commit on.
> Ran it through a debugger, just a simple accounting bug.



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

Mime
View raw message