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

Hudson commented on PHOENIX-5565:
---------------------------------

FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #3141 (See 
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/3141/])
PHOENIX-5565 Unify index update structures in IndexRegionObserver and (kadir: 
rev 234660ea0082815c59704a61dc9c33bb11d64381)
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/builder/IndexBuildManager.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/IndexRegionObserver.java


> 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 10m
>  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)

Reply via email to