You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Kadir OZDEMIR (Jira)" <ji...@apache.org> on 2020/02/07 20:18:00 UTC
[jira] [Commented] (PHOENIX-5720) Multiple scans on the same table
region cause incorrect IndexTool counters
[ https://issues.apache.org/jira/browse/PHOENIX-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032636#comment-17032636 ]
Kadir OZDEMIR commented on PHOENIX-5720:
----------------------------------------
[~abhishek.chouhan], The attached short patch is implements the solution we have discussed today. Would you please review it? I tested and also debugged it. It works as we expected.
> Multiple scans on the same table region cause incorrect IndexTool counters
> --------------------------------------------------------------------------
>
> Key: PHOENIX-5720
> URL: https://issues.apache.org/jira/browse/PHOENIX-5720
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.0.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Attachments: PHOENIX-5720.mater.001.patch
>
>
> IndexTool records its counters on an HBase table and uses table region name as the row key. When there are multiple scans on the same table region (i.e., when there are multiple MR mappers working on the same table region), these rows get overwritten and this leads to incorrect total counts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)