phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5344) MapReduce Jobs Over Salted Snapshots Give Wrong Results
Date Thu, 13 Jun 2019 22:34:00 GMT

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

Geoffrey Jacoby commented on PHOENIX-5344:
------------------------------------------

[~akshita.malhotra], fyi.

> MapReduce Jobs Over Salted Snapshots Give Wrong Results
> -------------------------------------------------------
>
>                 Key: PHOENIX-5344
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5344
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Geoffrey Jacoby
>            Priority: Major
>
> I'm modifying an existing MapReduce job to use Phoenix's MapReduce / HBase snapshot integration.
When testing, I noticed that existing tests that had previously worked for this job when running
on salted Phoenix tables began to fail when running on a snapshot of those tables. They pass
when running identical logic against the live table. Unsalted tables give the same, correct
result whether running against a live table or a snapshot. 
> The symptom on the salted snapshots is that the row count is way too high (a factor of
about 7x), but the exact amount appears non-deterministic. 
> My working theory is that somewhere the snapshot MapReduce integration for Phoenix sets
up the scans improperly for salted tables.



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

Mime
View raw message