You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Kadir OZDEMIR (Jira)" <ji...@apache.org> on 2019/11/14 11:39:00 UTC

[jira] [Updated] (PHOENIX-5565) Unify index update structures in IndexRegionObserver and IndexCommitter

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

Kadir OZDEMIR updated PHOENIX-5565:
-----------------------------------
    Attachment: PHOENIX-5565.master.002.patch

> Unify index update structures in IndexRegionObserver and IndexCommitter
> -----------------------------------------------------------------------
>
>                 Key: PHOENIX-5565
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5565
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 5.1.0
>            Reporter: Kadir OZDEMIR
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>         Attachments: PHOENIX-5565.master.001.patch, PHOENIX-5565.master.002.patch
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> The index updates are represented by a Collection<Pair<Mutation, byte[]>> where the byte[] member of the pair is the name of the index table. However, this map is then translated to a Multimap<HTableInterfaceReference, Mutation> when it is passed to an IndexCommitter. The code in IndexRegionObserver gets simplified and becomes more efficient in cpu utilization if IndexRegionObserver also uses a Multimap<HTableInterfaceReference, Mutation> structure to represent index updates. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)