[
https://issues.apache.org/jira/browse/PHOENIX-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417921#comment-16417921
]
Lars Hofhansl edited comment on PHOENIX-4671 at 3/28/18 6:52 PM:
-----------------------------------------------------------------
Lemme file a separate issue for the test then.
I realize that it was in part me who gave that flack :) ... 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.
was (Author: lhofhansl):
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)
