[
https://issues.apache.org/jira/browse/ASTERIXDB-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184837#comment-16184837
]
ASF subversion and git services commented on ASTERIXDB-2104:
------------------------------------------------------------
Commit 56d972fa6dd89769d6ba1220d49e2d54d48657d3 in asterixdb's branch
refs/heads/master from [~luochen01]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=56d972f ]
[ASTERIXDB-2104][STO] Optimization for Correlated Policy
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Previously, we introduced an optimization to the prefix merge policy
by ensuring component size grows exponentially after merging. This patch
applies the same optimization to CorrelatedMergePolicy
- A little refactoring of PrefixMergePolicy and CorrelatedMergePolicy
for code reuse
Change-Id: Icd84c77f1e2c34c410508fbc9de70156224ce932
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2019
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: abdullah alamoudi <[email protected]>
> Avoid always merging old components in correlated policy
> --------------------------------------------------------
>
> Key: ASTERIXDB-2104
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2104
> Project: Apache AsterixDB
> Issue Type: Improvement
> Reporter: Chen Luo
> Assignee: Chen Luo
>
> Previously, we introduced an optimization to fix the write amplification
> problem of the prefix merge policy by ensuring the result disk component size
> grows exponentially (https://asterix-gerrit.ics.uci.edu/#/c/1818/). A similar
> optimization needs to be adopted for CorrelatedPrefixPolicy as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
