You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/11/13 07:40:10 UTC
[jira] [Comment Edited] (PHOENIX-2412) Fix test failures due to use
of priority queue for merge sort
[ https://issues.apache.org/jira/browse/PHOENIX-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003438#comment-15003438 ]
James Taylor edited comment on PHOENIX-2412 at 11/13/15 6:39 AM:
-----------------------------------------------------------------
FYI, [~samarthjain]. Do you think the metrics would be different with the new implementation? There's an UPSERT SELECT being done over a salted table. Or do you think a bug was introduced?
was (Author: jamestaylor):
FYI, [~samarthjain].
> Fix test failures due to use of priority queue for merge sort
> -------------------------------------------------------------
>
> Key: PHOENIX-2412
> URL: https://issues.apache.org/jira/browse/PHOENIX-2412
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Ankit Singhal
>
> Looks like PHOENIX-2377 caused some test failures. Did you run all the unit tests (mvn verify) with your patch locally, [~ankit.singhal]?
> {code}
> Failed tests:
> PhoenixMetricsIT.testMetricsForUpsertSelectSameTable:615->assertMetricsAreSame:643->assertMetricsHaveSameValues:654 Unequal values for metric MUTATION_BYTES expected:<5600> but was:<16240>
> PhoenixMetricsIT.testMetricsForUpsertSelectWithAutoCommit:462->assertMetricsAreSame:643->assertMetricsHaveSameValues:654 Unequal values for metric MUTATION_BYTES expected:<5600> but was:<16240>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)