phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kadir OZDEMIR (Jira)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-5474) IndexTool should report the number of rows built
Date Sun, 15 Sep 2019 22:35:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kadir OZDEMIR updated PHOENIX-5474:
-----------------------------------
    Attachment: PHOENIX-5474.master.02.patch

> IndexTool should report the number of rows built
> ------------------------------------------------
>
>                 Key: PHOENIX-5474
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5474
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Kadir OZDEMIR
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0, 4.14.3
>
>         Attachments: PHOENIX-5474.master.01.patch, PHOENIX-5474.master.02.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In the old design, the IndexTool MR job mapper first scanned the data table rows one
by one using a Phoenix client code, then constructed the index rows and finally sent these
row mutations to region servers to update the rows on the index table regions. While doing
that, it emitted the counters at the row level. In the new design, this entire process is
done on the server side (within a coprocessor). So, the mapper just issues one RPC call to
instruct the coprocessor to build the entire table region. Thus, currently it does not report
the number of rows that have been built, instead it reports the number of table regions built.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message